Self-hosting and operator deployment
Self-hosting a development machine is separate from operating a control plane or a relay. Most developers can start with direct SSH and no hosted service.
Distribution origin
The website serves documentation, the laptop client installer and content-addressed client downloads from the same HTTPS origin. Configure FIVE08_REMOTE_INSTALL_ORIGIN at build time for your deployment, and set the matching public API origin at runtime.
docker build -f Dockerfile.control-plane \
--build-arg FIVE08_REMOTE_INSTALL_ORIGIN=https://devbox.example.com \
-t remote-control-plane .The example sets a public origin, not credentials. TLS, OIDC, database configuration and approved release signing are operator responsibilities. There is no production-ready one-command multi-tenant cloud bootstrap.
Control plane
The control plane owns identity, durable authorization and observations. Keep daemon identities distinct from human CLI sessions. Scope enrollment approvals and revoke relationships independently.
The owner test at devbox.508.dev has tasks and browser preview ingress disabled. Existing implementations behind feature gates are not an invitation to enable them without their acceptance and operational prerequisites.
Signed daemon channel
Build and sign host artifacts in a protected release environment. Distribute only the public verifier key to users and machines, and deliver it independently from the release it verifies. Preserve artifact size/digest, manifest expiry, channel and monotonic sequence checks.
The laptop client's HTTPS bootstrap is not a substitute for this signed host boundary. The public test distribution does not create a daemon signing authority automatically.
Relay
Deploy the standalone relay separately with independent connector/client authorities, TLS, effective memory/CPU/PID limits and narrowly scoped credentials. A connector dials the local machine's SSH endpoint; it is not arbitrary LAN proxying.
Multiple routes can improve reachability while preserving one host identity. Credential reload/revocation, bounded sessions and restart recovery need operational validation. Do not repurpose vendor agent credentials as relay credentials.
Backups and recovery
Back up the database, signing trust configuration and durable host files through approved mechanisms. Test restores into an isolated target. A local dump does not protect against losing the host's disk.
The owner test has verified local PostgreSQL restore, but offsite backup remains pending. Do not broaden the pilot or promise durability based solely on a successful local dump.