Choose an entrypoint
Choose between the Web console, CLI, HTTP API, and MCP tools.
Use the Web console for first-time setup, status inspection, field-level help, and guided tasks.
Use the CLI for local development, SSH server bootstrap, CI scripts, and interactive confirmation.
The default BYOS GitHub Action shape also enters through the CLI surface: Pure SSH Action uses
control-plane-mode: none, installs/runs the CLI in the Action, deploys over SSH, and stores state
in ssh-pglite on the target server.
Use the HTTP API for automation. API descriptions should link to the same public docs anchors instead of redefining separate input semantics.
Self-hosted Server Action uses the HTTP API surface: control-plane-url explicitly selects the
Appaloft instance, and appaloft-token supplies deploy-token authentication. The Action does not
run the CLI, open SSH, or scan target machines to discover a control plane.
When an agent host configures Appaloft MCP, use appaloft mcp stdio to expose the same operation
catalog. MCP tools reuse the same topic ids, input explanations, and recovery guidance. See
Appaloft MCP server.