Orbi Cloud: file an Issue, get a release

WHAT ORBI CLOUD IS

A hosted runner — GitHub stays the source of truth

Orbi Cloud runs the same GitHub-native delivery line as self-hosted Orbi — Issue in, worktree, tests, independent review and repair, exact-head merge — on infrastructure we operate. Nothing about your workflow moves: the Issues, pull requests, and release evidence stay in your repositories.

• THE LOOP
  GitHub Issue in, tagged release out

  Independent review that repairs code and reruns tests, the exact-head merge, then the frozen SHA, the tag, the GitHub Release, and the closed milestone — the loop your repository already speaks, with no second workspace to adopt.

• MODELS
  Model usage included, cost in the open

  Solo includes 400M tokens a month and Pro includes 1.2B; when the applicable allowance runs out, new deliveries pause — there is no per-token overage billing. The measured cost of a delivery is published below.

• OPERATIONS
  Recovery, merge gates, independent review

  The operational layers of the delivery line, run for you.

• RELEASES
  You start the release, Orbi runs it

  Releases are never automatic. You open the release Issue and apply the ai-release label — a label only humans set. The release's test acceptance is your repository's CI result — the GitHub Actions check runs on the release commit — so what you put in CI decides what Orbi guarantees: put unit tests there and it guarantees your code logic; put a business-flow e2e there and it guarantees the loop closes. No CI is a choice too: with no check runs, both gates pass and the release still ships — minus its only test-acceptance gate. Orbi then freezes the SHA, cuts the tag, publishes the GitHub Release, and closes the milestone.

COST, MEASURED

We don't take a margin on your tokens

Pro's 1.2B tokens cover about 240–630 merged deliveries for typical tickets in a small repository, or about 96 in a large codebase like Orbi's own engine (measured September 2026). That cost structure assumes the provider supports prompt caching. Sample, quantiles, limits, and competitor citations are on the cost page.

AFTER YOU CLICK

From sign-in to a delivered Issue in four steps

No new password, no workspace to migrate. The whole path is GitHub-native:

1. 01 Sign in with GitHub

   One OAuth click. Your repositories, your account — no separate Orbi credential.

2. 02 Install the Orbi GitHub App

   Choose which repositories the runner may work in; revoke at any time from GitHub.

3. 03 Connect a repository

   Connect the first repository and we provision your runner. Try 3 merged deliveries on your own repository — no credit card, no subscription.

4. 04 Label one Issue ai-ready

   Open <repo>/issues/new?labels=ai-ready, write what should change, and add the label. Orbi claims it within 5 minutes and comments on the Issue as it works. Only merged deliveries count toward the lifetime allowance; a delivery that fails or ends without a merge refunds its grant.