Skip to content

Current Scope

Jump to bottom
Nick Hamze edited this page Aug 31, 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.
  • Connections use WordPress Core Application Password approval.
  • Connected sites are stored per hub user.
  • Application Passwords are encrypted at rest.
  • Fleet detects missing, inactive, active, and network-active OpenStation installs.
  • Fleet installs or activates OpenStation through the Core Plugins REST API.
  • Status checks happen on demand, one site at a time.
  • Disconnect revokes the exact remote Application Password.
  • Pretty and plain WordPress REST URLs are supported.
  • Path-based multisite siblings can be connected without letting the hub connect to itself.

Not included yet

  • Bulk actions
  • OpenStation or plugin updates
  • Theme management
  • WordPress core updates
  • Backups or restores
  • Uptime monitoring
  • Security scanning
  • Site Health aggregation
  • Client reports
  • Team-shared credentials or site lists
  • Background jobs, schedules, or alerts
  • Interactive sign-in to a managed site's wp-admin
  • Private-network or localhost targets
  • A hosted control plane
  • A target-site Fleet agent

Why the preview is this small

WordPress Core already provides authorization, capabilities, HTTP requests, plugin installation, and credential revocation. The preview composes those features instead of building replacements.

The one-site-at-a-time workflow is enough to test the product loop:

  1. An agency installs OpenStation and Fleet on a hub.
  2. The agency connects a client site.
  3. Fleet detects that OpenStation is missing.
  4. The agency installs it with one button.
  5. OpenStation gains another active installation.

The next feature should be chosen from observed agency pain, not from a speculative maintenance-platform checklist.

Graduation into OpenStation core

The intended long-term split is:

  • The Fleet user experience and site-management workflow move into OpenStation core after validation.
  • WordPress Core remains responsible for authentication, permissions, HTTP, and plugin operations.
  • The feature plugin remains the test boundary until that workflow is stable enough to graduate.

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

Clone this wiki locally