Keep the control plane fast under load
Console polls receive only the parts of the state that changed, and Hosts reconcile at a pace that follows their load. Core also writes a complete copy of its database every day.
Benchmarks are in-process timings on a copy of a loaded Core database, not production latency guarantees. The adaptive Host pace, state deltas, a live restore and a 24-hour backup cycle are not yet proven live. The systemd backup path does not truncate the WAL, and a standalone restore does not restore the Run signing key.
How it works
Poll less, send less
The CLI daemon and terminal console get 304 Not Modified for an unchanged snapshot and otherwise only the changed sections: about 270 KB instead of 1.6 MB per poll in the benchmark. Browsers and MCP clients keep full snapshots.
Reconcile Hosts at the right pace
The Host agent takes one-shot Docker stats samples, caches sidecar accounting and reruns policy passes only when their inputs change. The pause between passes grows from 5 to 30 seconds as the host gets busy; commands are still picked up every 3 seconds.
Isolate the control plane
New workspace containers run with a lower CPU weight, and optional systemd slices separate Core and web from workloads. Background session-search indexing is capped at a fifth of the Host’s cores.
Back up Core every day
Core writes a complete database copy with a version and SHA-256 manifest every day and keeps 7 copies within 10 GiB. Keep the master key file in its own protected backup; restore refuses a copy from another product or schema version unless forced.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.