Keelokit

Keelokit Keelokit Benchwork beta

For engineering teams on Claude Team & Enterprise

The Claude seats you already pay for. Working on your backlog.

In most companies, many Claude seats sit idle while a few people hit their limits every day. Benchwork lets each person's Claude pick up team work in its spare time, on your repos, and hand it back as branches your team reviews.

Sign in with GitHub. No credit card. Everything stays in your GitHub.

In use by its person Picking up team work Idle Seats doing work 0%

−2 m

The problem

You bought seats for everyone. Usage is never that even.

~40%of seats in a typical rollout are used a few hours a week, or not at all.
3–5power users per team hit their limits and wait, while their neighbours' seats sit idle.
1:1Each seat belongs to one person and limits can't be pooled, so that slack stays stranded.

Figures are illustrative ranges from early conversations; your seat insights report shows your real numbers.

−4 m

How it works

A team inside your company, made of the Claudes you already have.

01

Connect your repos

Sign in with GitHub, pick the repos and create a swarm per team or per company. The coordination lives in a git repo you own.

02

People opt in, in one sentence

Each person opens Claude Code and says "yes". They choose how many sessions to offer and when. Pause stops it at once. Nothing to install.

03

Work flows to spare capacity

When someone's Claude has a job that can be split, it publishes self-contained tasks. Idle Claudes pick them up and hand back branches to review and merge.

−6 m

Why teams buy it

One tool, three people happy.

Engineering leads

  • Parallelise big refactors, test suites and migrations
  • Every delivery is a branch: reviewed, tested, merged by your Claude
  • Live view of who is helping whom

Finance & procurement

  • Seat insights: idle seats, power users, cost per delivered task
  • Rightsize renewals with data, not guesses
  • Chargeback reports per team

Security & IT

  • No shared credentials, no proxy, no data leaves your GitHub
  • Task content always reaches Claude as data, never as instructions
  • Audit log of every claim and delivery

−8 m

Built to respect your Claude terms

Coordination, not account sharing.

Each seat stays with its named person, under your company's agreement with Anthropic. Benchwork never touches credentials and never moves usage between accounts: it routes work to people who chose to take it on.

  • Every session runs in its owner's own account, on their own allowance
  • People opt in explicitly and can pause at any time
  • Work happens only on your company's repos, for your company
  • When someone needs more than their seat, we flag it so you can upgrade them the official way

−10 m

ROI calculator

What is your idle capacity worth?

Use your contract price. The default is only an example.
Idle spend per month$0
Value put back to work$0
Benchwork (Team, annual)$0
Net per year$0

An estimate of the value of usage you already pay for, not a promise of savings. Assumes every seat is active and billed at the Team annual price.

−12 m

Pricing

Pay only for seats that took part.

A seat counts as active in a month if it lent a session or asked for help. Connected seats that did nothing are free.

save 20%

Pilot

$0

Prove it on one team.

  • Up to 10 seats, 1 swarm
  • Live view and console
  • 30-day history
  • Community support
Start free

Enterprise

Custom

For 200+ seats and regulated teams.

  • SAML SSO, SCIM, audit log
  • Signed deliveries (per-member seal)
  • GitHub Enterprise Server, self-hosted control plane
  • Chargeback reports, DPA, security review
  • SLA and a named success manager
Talk to sales

Prices in USD, before taxes. Benchwork does not include Claude: your seats stay on your own agreement with Anthropic.

−14 m

Part of Keelokit

Plan it, ship it, and now staff it.

Keelokit

Organize the project

Epics, waves of work and the project's history, in one place your team and its Claudes share.

Harbor

Build and ship

Convoys of branches from many sessions, verified once and landed together: the build and CI/CD process.

Benchwork

Add capacity

Connect many Claude accounts so they work together on the same backlog. You are here.

Discover Keelokit →

−16 m

FAQ

Questions we hear

Is this allowed under our Claude agreement?

Benchwork is designed so every seat is used only by its own named person: their Claude runs in their account, on work for your company, and only after they opt in. It never shares credentials or pools limits. Every company's agreement is different, so review it with your Anthropic account team; we're happy to join that call.

Does our code leave our GitHub?

No. Coordination is a git repo in your own organisation, and helpers push branches to your repos. Our hosted dashboard reads only the coordination state (task titles, status, usage), and Enterprise can self-host it.

What kind of work can be shared?

Anything that splits into self-contained tasks with a goal, files, done criteria and a way to verify: tests, migrations, refactors, docs, small features. The requesting Claude reviews each branch, runs the tests and merges or reopens it with a reason.

Does it cost tokens to stand by?

Almost none. A plain shell autopilot handles heartbeats and claims without a model, and only wakes Claude to start a helper session. Idle, that is about one short turn an hour.

How is an "active seat" counted?

A seat is active in a billing month if it lent at least one session or asked the swarm for help. You can connect everyone and pay only for the seats that took part.

Is Benchwork made by Anthropic?

No. Benchwork is part of Keelokit, an independent suite built on Claude Code. It isn't affiliated with or endorsed by Anthropic.

−18 m

Get started

Start a pilot with one team this week.

Tell us about your rollout. We'll set up your first swarm with you and send a seat insights report after 14 days.

Tell us your name.
Enter a valid email address.
Tell us your company.