Managed Cloud forCoding Agents

Spawn coding agents with one API call.Spawn coding agents with one API call. Observability, permissions, and budgets included. Start with $100 credit, then pay for tokens + 10%.

Install on GitHub

Talk to salesDocumentation

+ 9 models

ellipsis:
  name: Flaky test fixer

claude:
  model: claude-opus-5
  system: Fix the flaky test in ci/.

trigger:
  type: cron
  schedule: "0 9 * * 1"

environment:
  repositories:
    - name: acme/api
  image:
    dockerfile_append: |
      RUN npm install -g pnpm

from ellipsis import Ellipsis

client = Ellipsis(api_key="ellipsis_key_...")

handle = client.sessions.run(
    prompt="Fix the flaky test in ci/",
    repository="acme/api",
)

import { Ellipsis } from '@ellipsis-dev/sdk';

const client = new Ellipsis({ apiKey: 'ellipsis_key_...' });

const handle = await client.sessions.run({
  prompt: 'Fix the flaky test in ci/',
  repository: 'acme/api',
});

handle.send("Now open a pull request")

session = handle.wait(timeout=900)
print(session.status)

for record in handle.records(limit=50):
    print(record.type)

await handle.send('Now open a pull request');

const session = await handle.wait({
  timeoutMs: 900_000,
});
console.log(session.status);

await handle.stop();

Deploy a fleet of agents
Without the infrastructure

Ship more in parallel

Hundreds of sessions at once, each on its own isolated machine built from your image. Agents start themselves on GitHub events, Slack and Linear mentions, Sentry alerts, or a schedule. Nothing waits on a laptop staying awake.

Trust what comes out

Every turn, tool call, and thinking block is recorded, and every session is attributed to a person, an API key, or the parent agent. "Which session produced PR #123?" is a query, months later.

your-org / agents

standup-automator.yaml

ellipsis:

name: Standup automator

description: Posts a daily standup digest to Slack

triggers:

- type: cron

schedule: "30 8 * * 1-5"

budget:

session: 2

claude:

model: claude-opus-4-8

system: |

Each weekday, summarize yesterday's merged PRs, the

reviews still waiting, and any failing CI, then post

the digest to #engineering and @ the right owners.

Set the limits once

Permissions are scoped before an agent spawns, on tokens that expire with the session. Spend is hard-capped per session, per developer, per agent. It is all YAML in your repository, reviewed like any other change.

Agents are moving to the cloud.
Make it a cloud you can verify.

The blocker is not capability. It is credentials, retention, and who can prove what an agent did.

More about security

SOC 2Type ICertified

SOC 2Type IIIn progress

Scoped credentials

Minted per session, narrowed to the repos and permissions you allowed, revoked when the sandbox is torn down.

Zero source retention

Your code lives only inside the session sandbox and is deleted with it. The transcript outlives the sandbox; the code does not.

Deploy inside your infrastructure

Run on Ellipsis Cloud, or self-host in your own AWS account so credentials, code, and model calls never leave your VPC.