Run your team's Claude and Codex sessions in the cloud with isolated sandboxes, scoped permissions, hard budget caps, spend attribution, audit logs, and full observability.
What are we shipping today?
Each agent runs in its own sandbox with scoped credentials and a hard budget. Developers get parallelism, the platform team gets the audit trail.
Learn more→Run parallel sessions from your terminal
Ellipsis is the infrastructure under whichever agent wins: sandboxes, credentials, budgets, and logs stay the same while the harness and model are config fields.
Learn more→Swap the harness with one config field
An agent is a YAML file in your repo: the prompt, the model, the sandbox, the permissions, the budget. Like infrastructure-as-code, for your agents.
Learn more→Define the agent in YAML, live on merge
Choose the models and prompts, add multiple reviewers, and gate what lands with a filter you write. Too noisy? Write a stricter prompt.
Learn more→Add reviewers and gate what lands
Each agent spawns the full stack and runs the tests in its own sandbox, so ten agents on one repo never clobber each other.
Learn more→Warm images make repeat sessions instant
Agents stop running on developers’ own credentials. Permissions are minted per session, spend is capped and attributed, and the transcript outlives the sandbox.
Learn more→Permissions minted per session, spend attributed
Put an LLM decision-maker anywhere in your SDLC with no infra to manage. Spawn a session from any workflow and get typed, structured output back.
Learn more→One POST starts a session, typed output back
Self-host in your AWS account and nothing leaves your VPC. Model calls can route through your own gateway for compliance and logging.
Learn more→The whole platform inside your AWS account