Sandboxes in your own cloud Enterprise runs now execute inside your account, and no code leaves it.
By Ravi Menon and Nadia Karim
Abstract
Enterprise runs can now execute in a sandbox inside the customer's own AWS or Google Cloud account, with the model served from the customer's own endpoint. Source code, secrets and test output never leave that account. This note describes the split, the runner and the trade-offs we accepted.
1Why
The first question in almost every security review we sat through was where the code goes. For most teams, an isolated sandbox in our cloud, deleted after each run, was enough. For banks, health companies and anyone with customer data in their test fixtures, it was not. Their code could not leave.
2The split
We divided Orrin in two. The control plane, which we run, handles everything that is not your code: the queue, who may approve, the Slack thread, the audit log. The runner, which you run, handles everything that is: it clones the repository, calls the model through your endpoint, runs commands and edits files. The runner keeps one outbound connection to the control plane, so you open no inbound ports.
| Orrin's cloud | Your account | |
|---|---|---|
| Source code | Never | Cloned per run |
| Secrets | Never | Your secret manager |
| Test output and logs | Pass and fail counts | In full |
| Run history | Steps and approvals | Mirrored to your bucket |
| Model calls | None | Your Bedrock or Vertex endpoint |
3The runner
The runner is one container image, rebuilt and signed every week. It starts a Firecracker microVM per run, gives it the repository and only the secrets the project allows, and destroys it when the run ends. A run never shares a machine with another run, even on the same repository.
orrin-runner.yaml
control_plane: wss://runners.orrin.dev
model:
provider: bedrock
region: eu-central-1
sandbox:
max_concurrent_runs: 8
network: registry-only
secrets:
source: aws-secrets-manager
allow: [DATABASE_URL_TEST, STRIPE_TEST_KEY]
history:
bucket: s3://quarry-orrin-history4What it costs
Running in your account is slower to start. A run's first step takes a median of 21 seconds on a cold runner against 6 in our cloud, mostly pulling the image; a warm pool closes most of the gap. It also moves the compute bill to you, which some teams prefer and some do not.
- Orrin's cloud6s
- Your account, warm pool8s
- Your account, cold21s
5Available now
Runners in your own account are part of Enterprise, on AWS and Google Cloud, with Azure planned for early 2027. Our security page lists the certifications and subprocessors behind the control plane.