self-hosted · one binary
Self-hosted. Each app runs in its own sandbox, with an identity, grants and network policy. IT holds the keys.
Linux, or macOS in a Lima VM · MIT / Apache-2.0 · try it free for an hour: ssh [email protected]
A backend, a git history, a sandbox. mv renames it, cp -r forks it.
Open its terminal in the browser. Edit it live, or hand it to an agent.
Another app, the network, a GPU: reached only after the owner approves.
Code and live state run in separate sandboxes; state answers only to the app's API.
$ bx new apps/dashboard --runtime go $ bx term apps/dashboard ~/apps/dashboard $ claude "add a p95 latency card" $ bx grant apps/dashboard res:apps/db reader ✓ live · sandboxed · versioned · backed up
Users and orgs. Invite-only accounts. SSO: Google, Okta, Entra, Keycloak, authentik, GitHub. Viewer, developer, admin.
Default-deny between apps. Network sets per org. Publishing is an explicit bind, behind your TLS.
Rootless namespaces, seccomp, landlock, a read-only base image, resource limits per app.
An encrypted vault per app. Scheduled backups to any S3. Every approval in the audit log.
One binary on any Linux box. The installer prints its plan and asks first. On macOS it sets up a Lima VM.