Introduction
sfp server is the server-side control plane for sfp-based DevOps automation. It provides a REST API used by the sfp CLI and other clients to run operations that would otherwise be bound to a single CI/CD job.
If you’re familiar with Salesforce DevHub, a useful mental model is “DevHub++”: the same control-plane pattern, extended from org/auth primitives into DevOps execution (queueing work, running it in isolated workers, tracking state, and exposing results through a consistent API). This term is just a shorthand for the concept; throughout the docs we simply refer to the system as sfp server. A single deployment can host multiple isolated tenants. Each tenant has its own configuration and operational state, and workload execution is handled by worker services.
Architecture (High Level)
The runtime is composed of an API service (the control plane), worker pools (the execution plane), and a small set of supporting services. The API accepts requests, validates identity/authorization, persists and streams state, and schedules work. Workers pick up tasks based on queue priority (critical/normal/batch), execute them in an ephemeral environment, and report progress and results back to the state store.
Capabilities
From a technical perspective, the system provides authentication flows (interactive and application tokens), task submission and lifecycle management (immediate/scheduled/recurring), document and key/value storage primitives used by higher-level features, and operation-scoped logging.
Server Management
sfp server provides comprehensive CLI commands for server lifecycle management:
Core Commands
sfp server init- Initialize a new server instancesfp server start- Start tenant servicessfp server stop- Stop tenant servicessfp server status- Check service statussfp server update- Update to latest version
Monitoring & Operations
sfp server health- Health checks and diagnosticssfp server logs- View and monitor logssfp server scale- Scale worker services
For a complete list of server management commands, see the CLI Reference.
Last updated