Runs in your Cloud account, with your keys

We work through your tickets while you sleep.

No more kicking off long chains of agents on your laptop and waiting hours for them to finish. Label your GitHub issues and log off: BacklogBeast works through them around the clock in your own cloud account, and leaves draft pull requests waiting for your review. It never merges and never deploys.

Bring your own cloud account and AI model provider key. Your code never leaves them, and we never mark up your model bill.

acme/webappOverviewExample workspace
Spend this month$41.20
of $300 budget
Draft PRs waiting2limit 2 · next run paused
Sent back as unclear1told what's missing
TicketTitleOutcomeCost
#412Settings page returns 500 on saveDraft PR$6.91
#420Retry the invoice webhook on a 502Running · 18m·
#415Make exports betterNeeds detail$0.00
#409Tidy the onboarding copyBlocked$3.40

#415 was sent back before any run: no checkable done state · no location in the product

How it works

From label to draft PR, with every step narrated on the ticket.

  1. 01

    Label a ticket

    Add the BacklogBeast label to any issue in a connected repo. Newest tickets are picked up first.

  2. 02

    It checks the ticket first

    Before anything starts, it checks for a clear outcome, a clear place in the product, no open decision, and one PR's worth of work. Unclear tickets are sent back with what's missing, and cost you nothing.

  3. 03

    It works in your account

    A short-lived machine in an isolated network in your own cloud account runs the coding agent from your AI model provider, on your key, with a hard time and spend cap on every run.

  4. 04

    You get a draft PR

    The change is inspected before it's pushed, then opened as a draft, with cost and outcome on the ticket. You review, run your tests, and land it your way.

Safety

Built so nothing ships without you.

Nobody has to watch it while it works, so these safeguards are built into BacklogBeast itself. They aren't instructions the AI could ignore: it can't switch them off, whatever a ticket says.

  • Draft PRs only

    GitHub won't merge a draft. It never pushes to your main branch, never deploys, and never closes a ticket for you.

  • Protected paths, enforced

    If a change touches CI config or your guard tests, or weakens an existing assertion, the branch is thrown away, not pushed.

  • Capped time and spend

    Every run has a dollar cap and a shutdown timer. If the budget can't be read, nothing launches. Stuck machines are shut down and you're alerted.

  • The model can't reach your keys

    The code it writes runs as a locked-down user with no GitHub token and no cloud credentials. Pushing and labelling happen only after inspection.

Your account, your keys

We run the dashboard. Everything that touches your code runs with you.

Many hosted coding agents run your code on their servers and bill model usage themselves. BacklogBeast works the other way round: the work happens in your account, on your key, and our price covers only the service.

In your cloud account

  • The machines that run each ticket, in their own network
  • Your AI model provider's API key
  • Your code, clones and full run logs
  • Your cloud and AI model bills: you pay your providers directly

Connect with one click, which creates a single access role. Delete the role and we're out.

With BacklogBeast

  • Sign-in, your team and their roles
  • Run history: outcomes, cost and time, never code
  • Ticket readiness checks, on us
  • Scheduling, and the GitHub app you install on your repos

Readiness checks read a ticket's title, body and recent comments, and keep only the verdict.

Pricing

Start free. Upgrade when it's earning its keep.

Plans cover the service. You pay your cloud and AI model providers directly for the machines and model usage in your own account, so we never mark either up. Prices will be announced at launch.

Free

Try it on a repo, with ticket readiness checks included.

Pro

For a product that ships every week: more runs, more repos, longer history.

Team

For a product team, including the people who write the tickets.

Anyone who can open a GitHub issue can hand work over. People who only write tickets never need a seat.

Early access

Be first to hand your backlog to the beast.

BacklogBeast is in private testing. Leave your email and we'll tell you when you can connect your first repo. One email at launch, no newsletter.

We only use your email to tell you about launch. Privacy