Encrypted in transit
The public site, API, and terminal connection use HTTPS or secure WebSockets. Session cookies are HTTP-only, secure in production, and same-site.
▍ Security · current production model
Know what you are trusting.
Terminalbox runs code and coding-agent credentials on hosted infrastructure. That is different from a local relay, so the useful security question is not “is it secure?” but what is isolated, what Terminalbox can access, and which risks remain yours.
This page describes the live architecture as of . It avoids certifications and guarantees Terminalbox does not currently have.
The short version
Three boundaries matter.
Unprivileged containers
Each terminal runs in an unprivileged Incus container with nesting disabled and CPU, memory, and process limits. Each account receives quota-bounded persistent storage.
Not end-to-end encrypted
Terminalbox operators administer the host and can access workspaces and operational logs when needed. Do not use Terminalbox for data an infrastructure operator must never be able to inspect.
What happens to your data
The practical model.
Files and processes
Your pane is isolated; your home follows you.
A pane gets its own container runtime. The account’s home directory is shared only across that account’s panes so repositories, tool configuration, and shell history persist when you switch templates. Storage quotas cover the container and persistent home data together.
Agent credentials
Provider sign-in happens inside the workspace.
Claude Code, Codex, Gemini CLI, and other providers remain separate services. Their credentials and configuration live in the hosted environment after you sign in. Terminalbox does not include model usage and cannot make a hosted provider credential invisible to the host operator.
GitHub and billing
Use scoped processors for narrow jobs.
The optional GitHub App uses short-lived installation access when cloning a selected repository instead of copying a long-lived personal token into the pane. Card entry is hosted by Stripe; Terminalbox stores the subscription and billing state needed to enforce the selected plan.
Logs and support
Operations are observable.
Terminalbox records account and session activity and may record commands or terminal traffic needed to operate, debug, secure, and audit the service. Access is restricted to operators who need it, but this is an operational control—not zero-knowledge encryption.
Current limits
What Terminalbox does not promise yet.
No end-to-end workspace encryption
The production operator is inside the trust boundary.
No published uptime SLA
Terminalbox is an early service running in one production region.
No customer restore guarantee
Keep repositories in version control and important data backed up elsewhere.
No provider-security substitute
Your agent provider’s authentication, permissions, and usage rules still apply.
Safer first session
Start with a bounded project.
A hosted terminal is easiest to evaluate when the first task is useful but recoverable.
- 01Push the repository to source control before moving it.
- 02Use provider and repository access scoped to the task.
- 03Avoid production credentials until the workflow earns your trust.
- 04Keep the hosted workspace out of your backup strategy’s critical path.
Try the real boundary
One hosted terminal. One bounded task.
Base is €6/month for one pane with 2 vCPU, 4 GB RAM, and 50 GB of persistent quota-bounded storage. Cancel when the hosted workflow is not useful.