From task to merged PR, with nothing left to chance.
Kestrel is the runtime between your agents and your repo. It decides where they run, what they remember, which model does each step and what has to pass before anyone reviews the work.
The life of a run
Five stops, every time
01Queue
A task arrives from the CLI, an issue label or the API and waits its turn.
02Sandbox
A fresh, sealed copy of the repo spins up with the network off.
03Agent
The agent plans, reads and edits, routed step by step to the right model.
04Evals
Your tests and our evals run on the diff. Failures go back to the agent.
05Pull request
Only a passing diff leaves, as a pull request with its full trace attached.
Sandboxes
Walls around every task
Each task gets a throwaway machine with a copy of your repo and nothing else. The agent can install, build and break things freely, because nothing it does survives the task.
0.8scold start for a sandbox
0outbound calls unless you allow them
1task per sandbox, never shared
Memory
Learns your repo, keeps it
Build commands, flaky tests, the module nobody touches: what one run works out is written to memory your whole team shares, and every later run starts from it.
38%fewer steps on a repo's tenth run
Per repomemory, never mixed across repos
Editableby your team at any time
Evals
A reviewer that never gets tired
Before a pull request opens, the diff runs your test suite and Kestrel's evals for scope, style and risk. A failing diff goes back to the agent with the failure attached.
48checks on a typical run
93%of pull requests merged unchanged
Customevals in plain YAML
Model routing
Pay for reasoning only where it counts
Kestrel scores each step before it runs. Lookups and renames go to a small model, and only the hard steps reach a large one. You set the thresholds.
72%of steps run on a small model
3.1xcheaper than one large model for everything
Anyprovider, or your own
And the rest
Everything a run needs
Traces
Every file read, tool call and test of every run, kept for search and replay.
Rate limits
Cap how fast each repo may spend, turned away at the edge before it costs.
Queues
A thousand tasks during a release drain in order. Nothing is dropped.
Webhooks
Run started, evals failed, pull request opened: post each to your own tools.
CLI and API
Start runs from a terminal, a script, CI or an issue label.
Long context
One million tokens of working context, compacted instead of cut off.
Security
Built for the repo you can't leak
Code never leaves the sandbox it was cloned into, and the sandbox is gone when the task ends. On Enterprise, so is the question of whose cloud it ran in.
SSO and SCIM
Sign in with Okta or Google, or any SAML provider, and provision seats from your directory.
Audit log
Every run, setting change and approval, exportable to your SIEM.
Your VPC
Enterprise runs Kestrel's workers inside your own cloud account.