Now in private beta

Your backlog, on autopilot.

Connect Linear and GitHub. Orbital picks up issues, implements the code, tests, fixes, and merges PRs — autonomously. Your 4-person startup ships like a team of 20.

orbital
$ orbital tail
Claimed ENG-42: Add rate limiting to /api/v1
Workspace created orbital/ENG-42
Running playbook install → implement → test → review
Tests failed (2 of 89 assertions)
Fixing... reading failure output, patching
Tests passed (14 suites, 89 tests)
Review passed
PR merged to main
ENG-42 → done · 4m 22s
$

We use Orbital to build Orbital. Every feature in this product was implemented, tested, and merged by an agent.

Connect Linear. Connect GitHub. Ship.

1

Connect

Link your Linear workspace and GitHub repo. Add a playbook.toml that defines your agent workflow.

2

Write issues

Create issues in Linear. Describe what you want built. Mark as ready. Orbital picks them up and starts working.

3

Review the PR

The agent implements in a branch, runs your test suite, fixes failures, opens a PR on GitHub, and merges when ready.

It doesn't give up.

Tests fail. The agent reads the output, patches the code, tries again. Review rejects. Back through the fix loop. No limit on iterations. Each pass builds on the last — context accumulates, the code improves.

The system keeps going until the issue is resolved. You check in on a PR, not a process.

retries until resolved
~4m avg issue completion
implement
test
fix
review

How it actually works.

Crash recovery

Something goes wrong mid-run? The agent picks up where it left off. No orphaned branches, no lost work, no manual cleanup.

Parallel agents

Multiple issues run simultaneously, each in its own isolated workspace. No conflicts. They all merge cleanly.

Self-healing

Tests fail? The agent reads the output, understands what broke, fixes it, and tries again. No human needed in the loop.

Customisable workflows

Define exactly how your agent works in a simple config file. What it implements, what it tests, how it reviews. Your process, automated.

Your test suite, your rules

Orbital runs your actual tests. bun test, pytest, cargo test — whatever you use. No separate validation layer.

Your backlog shrinks overnight

Triage issues before you leave. Come back to merged PRs. Your team focuses on architecture and product — the agents handle the tickets.

Your workflow,
in 20 lines of TOML.

Playbooks define what the agent does for each issue. Chain agent steps, shell scripts, and decision gates. Branch on success or failure. Issue context is injected automatically via variables.

This is the actual playbook we use to build Orbital.

playbook.toml
[[steps]]
id = "implement"
type = "agent"
prompt = """
Implement ticket $TICKET_ID: $TICKET_TITLE
$TICKET_BODY
"""

[[steps]]
id = "test"
type = "script"
command = "bun run test"
on_success = "review"
on_failure = "fix"

[[steps]]
id = "fix"
type = "agent"
prompt = "Fix the failing tests..."
next = "test"

[[steps]]
id = "review"
type = "agent"
prompt = "Review the implementation..."
on_failure = "fix"

Pay for what you use.

Bring your own API key, or let us handle the tokens. No per-run limits.

Solo
$19/mo
For individual developers
  • 1 user
  • 5 repositories
  • Bring your own API key
  • 100 agent runs / month
Get started
For teams
Startup
$199/mo
+ $29 per additional user
  • Unlimited repositories
  • $25 / 1M tokens, or bring your own key
  • Unlimited agent runs
Get early access
Enterprise
Custom
For teams running agents at scale
  • Everything in Startup
  • Volume token pricing
  • Dedicated infrastructure
  • SLA & onboarding
Talk to us

Ship while you sleep.

Write issues in Linear. Wake up to merged PRs. We're onboarding startups now.

Request access

No credit card required · Free tier available · Cancel anytime