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

Your remote development workspace

Keep your repositories, development tools and coding agents on a Linux machine you control. Connect from your laptop, open the right worktree, and view your app through a private tunnel.

Private pilot: start with your own host. Managed compute, hosted task execution and browser preview ingress are not enabled on the test deployment.

Choose your starting point

What lives where

LocationResponsibility
Your laptopCLI, editor, SSH keys and local tunnel endpoints
Your Linux hostRepositories, running agents, vendor sign-ins and dev servers
Optional hosted control planeIdentity, authorization, observed machine/workspace/session metadata
Optional relayTransport for encrypted SSH; not an agent conversation protocol

Two ways to connect

Direct SSH works without hosted enrollment. Add an existing trusted SSH alias, prepare your repo, and open it. Use a VPN alias when your host is reachable through your own network.

Hosted enrollment adds machine observations and an optional outbound relay for machines without publicly reachable SSH. An independently hosted relay is also supported. Compare connection methods.

Know the boundaries

A persistent filesystem survives disconnection and normal host reboots when its disk survives. Running tmux sessions survive a laptop disconnect, but do not survive a host reboot. Worktrees under one Unix user are not security sandboxes.

Devboxes are for development and temporary services, not production hosting. You own the host, its operating system, backups and vendor subscriptions.

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