Autonomous coding agents, without the ops or the blind trust.
Every agent session runs in its own microVM. Egress is closed by default — a session reaches only the destinations its own configuration needs.
- Egress: closed by default
- microVM isolation
- No runtime ceiling on your plan
- Region: EU
- Guardrails, not surveillance
- BYOT: your token, your provider
Ship code. Skip the agent-sitting.
Point an agent at your repo, cap its budget, close the laptop. It runs in its own microVM — not in a tmux you babysit.
Connect a repo
A git remote and a scoped token. Nothing to install, no runners to keep alive.
repo: git remote · scoped tokenBring your model
BYOT: your token, your provider. Keys are stored encrypted and never displayed again after saving.
model: byot · stored encrypted · never displayed againSet the cap. Walk away.
No runtime ceiling on your plan — a run may take a weekend. The caps are yours: a runtime-minute cap per account and a lifetime cap per session, both with auto-stop, both optional.
runtime: no ceiling on your plan · caps optional · auto-stop
Full control. Zero ops. Not a trade-off.
Managed here means less ops — not less control over what the agent can reach.
Give your agent a sandbox, not the keys to the building.
- No lock-in · BYOT
- Standard git flow
- Zero ops
The boundary is the default.
microVM isolation
Every session gets its own Firecracker microVM with its own guest kernel — no shared kernel namespace.
isolation: firecracker microvm · 1 session = 1 vmExecution and storage in the EU
Sessions run on bare metal at an EU provider. Whether the whole route stays in the EU also depends on the model you choose.
region: eu · bare metal · model route: declaredGuardrails, not surveillance
We operate the platform with guardrails, not with surveillance of what your agent is working on.
operating policy: guardrails instead of content monitoringA live event feed per session
A running session streams an event feed you can watch, boundary decisions included. The events are persisted as OCSF records. Ageing out runs on a schedule, but the window is shared across accounts rather than set per customer. Export and tamper-evident anchoring are on the roadmap.
audit: live session feed · persisted as OCSF records · export & tamper-evidence: roadmap
Become a design partner
We are building this with a small number of teams, not for an anonymous market. Tell us what you need to run agents on your code — you get early access, we get the requirement.
Become a design partner