CLANKER DUTYSign in

Claude Code in the cloud

Agent orchestration for building software.

Clanker Duty runs Claude Code in the cloud, triggered by your stack: production errors, payments, analytics, GitHub, schedules and requests from your team. Agents build the change, test it and review it, and you decide how much ships without a person.

Sign in to Clanker DutyHow it works
Clanker Duty's Approvals page: a reviewed change waiting for a person, with checks and reviewer verdicts.

How it works

  1. 1

    Triggered by your stack

    Sentry, Stripe, PostHog, GitHub, any webhook, a schedule, or a request from someone on your team starts a workflow.

  2. 2

    Built by Claude Code

    Each run gets a fresh cloud sandbox with your repo, the tools and secrets you allow, and a budget. Nothing it does touches your machines.

  3. 3

    Reviewed by agents

    Your checks run, then code, QA, design, compliance and security reviewers read the diff in parallel. Findings go back to the builder until it passes.

  4. 4

    Shipped your way

    Changes that clear your guardrails merge on their own. Anything else waits for a one-click approval, or goes back to the builder with a note.

Orchestration, not a chat window

Workflows chain a builder, checks, reviewer agents and fix rounds into one pipeline, with every run, transcript, verdict and dollar on record.

Autonomy you set per project

Run hands-off, review everything, or anything in between. Clanker Duty tracks which changes would have merged on their own, so you know when a project is ready for more autonomy.

The whole company can ask

Product, support and ops send requests from an inbox, email or Slack. An intake agent drafts the spec, an engineer checks it, and the requester follows it to the merge in plain words.

Context every agent shares

Team knowledge and past decisions go into every prompt, and agents add what they learn from each run, so Clanker Duty gets better at your codebase over time.

Guardrails built in

Sandboxes never hold a write token, builders work from an engineer's spec rather than a customer's words, and budgets, protected paths and a kill switch keep runs in bounds.

Your cloud, your keys

Self-hosted on Railway with Postgres and Redis, with your Anthropic key. Workflows are built in the dashboard, versioned on every save and exportable as YAML.