Skip to content

Current Scope

Jump to bottom
Nick Hamze edited this page Sep 1, 2026 · 6 revisions

Current scope

Fleet for OpenStation is an early feature-plugin preview. Its first job is to prove a useful agency workflow that also puts OpenStation on more WordPress sites.

Included now

  • One WordPress install acts as the Fleet hub.
  • Managed sites connect through WordPress Core's native Application Password approval.
  • Fleet never asks for a normal WordPress password and encrypts each integration credential on the hub.
  • Approval returns to a visible setup screen that installs or activates OpenStation automatically.
  • Reconnecting an existing site does not create a duplicate credential.
  • Fleet detects missing, inactive, active, and network-active OpenStation installs.
  • Every selected site opens in its own stable, bounded OpenStation window, allowing multiple remote sites to stay open together.
  • Fleet Inbox combines pending comments, drafts, posts awaiting review, scheduled posts, connection problems, and Core Site Health findings from connected sites.
  • Live fleet search finds content, media, comments, and users across as many as 25 matching sites at once, with optional client scoping for larger fleets.
  • Client workspaces open every site assigned to a client as a persistent set of OpenStation windows.
  • Capability-aware views manage posts, pages, comments, media, plugins, users, and common site settings.
  • Media uploads and WordPress.org plugin installation are supported.
  • The live Explorer catalogs every advertised Core and plugin REST route and can use any method allowed to the approving account.
  • Agency metadata includes client, tags, plan status, private notes, and favorites, with search and filters.
  • An attention queue combines connection problems, OpenStation status, Core Site Health, and available WordPress version information.
  • Safe bulk actions check selected sites or install and activate OpenStation on them.
  • A private activity history records connection and management actions.
  • Core cron refreshes sites every 15 minutes while spacing heavier Site Health checks.
  • Pretty and plain WordPress REST URLs and path-based multisite siblings are supported.

Fleet-wide reads use the existing WordPress Core collection routes. When the managed site advertises Core's /batch/v1 controller, Fleet combines those reads into one authenticated request; otherwise, it calls the same Core routes individually. Neither path requires a Fleet endpoint on the managed site.

Deliberately outside Fleet

  • Backups and restores
  • Uptime monitoring
  • Malware or vulnerability scanning
  • A shared credential vault
  • Interactive sign-in to another site's wp-admin
  • Private-network or localhost production targets
  • A hosted control plane
  • A target-site Fleet agent
  • Management for features that expose no REST API

The installation loop

  1. An agency installs OpenStation and Fleet on one hub.
  2. The agency enters a client site's URL.
  3. WordPress shows its native approval screen.
  4. Fleet installs and activates OpenStation automatically.
  5. The client site opens immediately as a named, manageable OpenStation window beside the hub.

The connection itself stays useful even if the host blocks automatic plugin installation. Fleet preserves it and offers a retry without another approval.

Graduation into OpenStation core

The feature plugin remains the test boundary while the workflow changes quickly. Its user experience may later graduate into OpenStation core, but Fleet does not require changes, branches, or pull requests in OpenStation to work today. WordPress Core remains responsible for users, capabilities, safe HTTP, credentials, REST routes, and plugin operations.

No compatibility promise has been made for the preview's internal storage shape or private PHP identifiers.

Clone this wiki locally