Massed Compute desk
GitHub Open the app
  • Open source
  • MIT
  • Cloudflare Workers

Run it on your own Cloudflare account.

You, the Massed Compute account holder, deploy it. Your members join with just their email and rent GPUs on your account, inside a budget, a GPU list, and a machine cap.

Deploy to Cloudflare Open the app View on GitHub

Fleet

Example
  • Lab member 1× A6000 · running in budget $12.40 of $20
  • Coding agent 1× L40S · running in budget $3.10 of $8
  • Started on Massed Outside the desk unattributed no budget

How it works

Deploy once. Hand out budgets.

  1. 1

    Deploy

    Sign in with Cloudflare and the button sets up the Worker, database and backup bucket in your account. You become the admin.

  2. 2

    Connect Massed

    Approve on Massed’s own page. Your password stays there. Revoke it under Settings → Connected Apps.

  3. 3

    Invite

    Email a budget, a GPU list, and a machine cap. Members join with just their email. No Massed account.

  4. 4

    Members launch GPUs

    At $0 that person’s VMs stop, after a final backup of their workspace. Admins are not stopped. Massed still bills you.

The desk

What Massed does not keep.

  • Spend by person, agent, and GPU. Burn from the samples.
  • History after the VM stops. Massed only lists what is running.
  • Unattributed if it was started on Massed, outside this desk.
  • Agents — Claude Code, Codex, Cursor. Approve gpu-proxy login. 30-day token. Same caps.
  • Match a job to the cheapest live GPU on that person’s allowlist.
  • Backups of each workspace to your R2 bucket, with restore onto a new VM. A budget-safe final backup runs before a $0 stop.

Limits

These numbers are not a bill.

  • EstimateSampled every 5 minutes. An estimate, not an invoice.
  • No walletThe API has no balance, transactions, or receipts.
  • GapsA VM that starts and stops between samples can be missed.
  • $0Stops that person’s VMs. Admins keep running. Massed still bills the lab.

Run it yourself

Your Cloudflare account, your data.

The Deploy button or npm run setup logs in with Cloudflare OAuth and provisions D1 and R2. Admin sign-in and member invites are the desk’s own. MOCK_MASSED=1 locally. "0" in production. Don’t commit .dev.vars or the Massed key.

On your machine

# from the README
git clone https://github.com/vasanthsreeram/mass-compute-management-ui.git
cd mass-compute-management-ui
cp .dev.vars.example .dev.vars
npm install
npx wrangler d1 migrations apply gpu-proxy --local
npm run dev

On your Cloudflare account

# opens the Cloudflare login in your browser
npm install
npm run setup -- --dry-run
npm run setup
# prints your URL and a one-time admin claim,
# then: Connect Massed Compute, invite members