Backed byYCombinator

Run Claude Codein the cloud

Fleets of coding agents with the flexibility of local development and the governance of enterprise infrastructure. Get started with $100 free credit, then pay for tokens plus 20%.

Install on GitHub
Talk to salesDocumentation
from ellipsis import Ellipsis client = Ellipsis(api_key="ellipsis_key_...") session = client.sessions.run(prompt="Fix the flaky test in ci/")
Claude logoClaudeCodex logoCodexGemini logoGemini
Works with the agents your team already uses
0+
engineering teams
0.0M
agent sessions
Ellipsis, #4 Product of the Day on Product Hunt
Mosaic logoTrack logoRoo logoTribe AI logo
01The CLI

A fleet of cloud agents, managed like infrastructure

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
Graphic: Terminal streaming a fleet of parallel agent sessions

Run parallel sessions from your terminal

02Harnesses

You choose the harness, we handle the infrastructure

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
Graphic: Side-by-side claude/codex YAML files: same agent, one field changed

Swap the harness with one config field

03Agents as code

Agents are defined as code

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
Graphic: Agent YAML file revealing field by field, live on merge

Define the agent in YAML, live on merge

04Code review

Code review with your prompts and your models

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
Graphic: code_review.yaml with multiple reviewers and a gatekeeper filter

Add reviewers and gate what lands

05Sandboxes

Agents spawn in seconds, with your toolchain installed

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
Graphic: Sandbox provisioning timeline: warm image, repos cloned, tests running

Warm images make repeat sessions instant

06Governance

Scoped credentials, hard budgets, full audit trail

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
Graphic: Governance panel: per-session token scopes, budget bar, audit trail

Permissions minted per session, spend attributed

07The API

Spawning agents is as simple as POST /v1/sessions

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
Graphic: POST /v1/sessions curl request and the 201 response body

One POST starts a session, typed output back

08Self-hosted

No data ever leaves your VPC

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
Graphic: Your-VPC diagram: platform, sandboxes, and model calls inside the customer account

The whole platform inside your AWS account

Frequently asked questions

Claude Code and Codex today, each with the model, tools, and spend cap you declare. GitHub Copilot and Gemini are coming soon.

Sessions run on cloud machines, so dozens work in parallel while your laptop is closed. Each one gets credentials scoped below any developer, a hard spend cap, and a transcript your whole team can read afterwards.

Install the GitHub app, commit one YAML file under agents/ in your repository, and the version on your default branch is the live agent. There are no runners to host and no tokens to mint.

One YAML file in your repository carries the prompt, model, trigger, repositories, permissions, and spend caps. Commit it to deploy, open a pull request to change it, revert to roll it back.

A config declares one trigger: a cron schedule, an event on a GitHub pull request, push, or issue, a Linear issue, a Sentry alert, or a new Slack channel, or an @ellipsis mention. Any agent also starts from the REST API and the CLI.

On its own cloud machine, one per session, with your repositories cloned in and credentials scoped to the job at hand. The sandbox is torn down when the session ends.

Every turn, tool call, and diff is recorded and searchable, with the cost of each step. Transcripts keep indefinitely by default; an organization admin can set retention between 7 and 365 days.

Zero source code retention: your code exists only inside a session's sandbox and is deleted when that sandbox is torn down.

Every agent session runs in its own sandbox, and you pay for exactly what that session consumes: CPU and memory metered by the second, tokens passed through at the model provider's rates with no markup, and a platform fee of 20% of the session's token and compute cost. There are no per-seat fees, and nothing runs idle, so nothing bills idle.

Yes, at four levels: your whole account, one agent, one session, and one developer, over rolling 1-, 7-, and 28-day windows. A session that would breach a limit never starts, and a running session that reaches its budget stops immediately.

Yes. Agents are defined as YAML in your repositories, so they are portable by construction: the same configs, skills, and triggers run in either deployment, at the same prices. Talk to sales and we will help you plan the move.