Skip to content
d_devboxby 508.dev/ DocumentationDashboard ↗
Browse documentation
DOCUMENTATION / Security boundaries

Security and trust boundaries

The goal is a recoverable development machine with explicit trust and authorization, not invisible credential forwarding.

Machine identity

Initial SSH trust comes from OpenSSH and an independently checked fingerprint. Saved routes bind the same machine ID, development user and negotiated Ed25519 host key. A changed identity is a hard error.

Never remove known-host entries simply to silence a mismatch. Verify whether the machine was rebuilt or you are reaching the wrong endpoint, then update trust deliberately.

Release boundaries

The laptop installer trusts its HTTPS distribution origin and checks embedded content digests. It installs only into the current user's directories.

The host daemon has a separate signed-release verifier: pinned public key, exact artifact size/digest, expiry, channel and monotonic sequence. The privileged updater activates verified releases and rolls back unhealthy activation. No client convenience script removes that boundary.

Relay boundary

SSH authenticates and encrypts through the platform or self-hosted relay. Relay authorization is scoped and expiring. The relay is transport, not a vendor-agent plugin protocol or permission bypass.

Workload boundary

An ordinary worktree is not a sandbox. Processes under your development user can access that user's resources. Resource limits and admission protect availability; they do not turn mutually untrusted projects into isolated tenants.

Managed hosts have aggregate workload limits and protected control/recovery headroom. A BYO administrator remains responsible for suitable cgroup policy, OS updates, SSH access and tested backups.

Development-only services

Keep development listeners private and expose only the service you intend to preview. No production uptime or production data durability promise is made for a devbox.

What the hosted pilot stores

Authorization, commands and bounded observed metadata belong in the hosted control plane. Prompts and transcripts are not sent in heartbeat inventory. Live Paseo pairing is a separate full-control connection that the user explicitly approves.

Development machines. Your code. Your control.
Private pilot · Feature availability is called out in each guide.