Skip to content

Pre-launch. RepoStaff isn't for sale yet. This page says what it will do.

repostaff

/pricing

Flat per org. Your models.

Seats punish you for adding people, and they make no sense when the staff you're paying for isn't people.

Untested hypotheses

Every price and limit on this page is planned, untested with buyers, and may change. RepoStaff isn't for sale yet. No billing provider has been selected, and no payment is collected here.

Planned offers

At most 5 teams

Design partner

$149

planned hypothesis, per org, per month, for 12 months

Half the self-run list price, or $349 on RepoStaff-hosted compute once that exists. Billing begins after the first completed agent run on your repo.

Become a design partner
Planned first

Self-run

$299

planned hypothesis, per org, per month

Hosted Management UI, your compute. Marshall, ephemeral agents, and the brain repo included. Compute and model usage are separate.

Become a design partner
Later. Waitlisted. No date

RepoStaff-hosted compute

$699

planned hypothesis, per org, per month

Hosted Management UI, my AWS. 100 VM-hours included, then $0.60 per VM-hour up to your overage cap. Model usage is separate.

Hosted compute waitlist details
After launch, if support allows

Self-hoster rate

$49

planned hypothesis, per org, per month

Up to three members on their own hardware. No sooner than 90 days after the paid launch. Not full management self-hosting.

Self-hoster rate details

Hosted management is not hosted compute. RepoStaff plans to host the Management UI first, on every plan. Worker compute rolls out separately: your Linux/KVM hardware, then your AWS, then RepoStaff-hosted AWS after the paid self-run launch.

How the bill works.

  1. 1 of 4

    A flat subscription

    Per org, not per seat. It will pay for the hosted Management UI, Marshall, ephemeral agents, and the workflow around the brain repo.

  2. 2 of 4

    Ongoing overhead

    Persistent Marshall and shared infrastructure will keep running between tasks, so those costs continue whether or not a ticket is moving.

  3. 3 of 4

    Included hosted usage

    RepoStaff-hosted compute is planned to include one Marshall host and 100 VM-hours a month. Self-run has no allowance, because the compute is yours.

  4. 4 of 4

    Then metered usage

    Hosted VM-hours beyond the allowance will be metered at a rate that includes a hosted-service margin. That margin is on compute. It isn't model-token resale. The exact markup isn't final.

A quiet month

An inactive period shouldn't generate task-usage charges for compute you don't consume. The subscription or included plan still continues, and so do persistent Marshall and shared infrastructure costs. Don't count on a refund or rollover of unused included hours: neither is promised.

What you pay someone else.

Your model provider

Model usage will go straight to Anthropic or OpenAI on your own API key, as a separate invoice. No subscription logins. I don't resell tokens or mark them up. RepoStaff will hold your keys in an encrypted vault and broker requests by default, so they won't stay only on your machines, and bringing your own key isn't a no-retention promise. All planned and unbuilt. [LINK TO SECURITY PAGE WHEN IT EXISTS]

Your compute

Self-run compute will go to whoever you already pay: your electric bill or your AWS bill.

Your AWS account

Connecting customer AWS will start persistent costs before any task runs, and they will keep accruing without task activity: about $118 a month at us-east-1 list prices for network, proxy, and Marshall. That's a hypothesis and an estimate, not a quote. The setup is untested as of 2026-11-08.

What the protections don't cover

RepoStaff's planned caps and budgets apply to RepoStaff's bill or stop runs based on estimates. They do not cap your model provider's invoice or your infrastructure invoices, and stopping runs doesn't stop always-on AWS charges. Spending controls are unbuilt and unproven.

Planned limits, side by side.

Planned limits by compute option. Every value is an untested hypothesis.
Planned termSelf-runRepoStaff-hosted compute
Price$299 per org, per month$699 per org, per month
Agents run onYour Linux/KVM hardware first, your AWS account nextRepoStaff's AWS, after the paid self-run launch
Management UIHosted by RepoStaffHosted by RepoStaff
Included computeNone. The compute is yoursOne Marshall host and 100 VM-hours a month. One VM-hour is one 4 vCPU, 16 GiB worker for one hour
After the allowanceNot applicable$0.60 per VM-hour, up to your overage cap
Marshall and the brain repoOne org, one Marshall, includedOne org, one Marshall, included
Members and reposNo limit on eitherNo limit on either
WorkersLimited by your hardware or AWS accountOne 4 vCPU, 16 GiB VM per task, up to 4 at once, 120 minutes and 5 GB of network per run
Fair use1,500 runs a month. Two months above that starts a conversation, not a billGoverned by your overage cap
Overage capNot applicable. Self-run has no overageRequired before your first run. $0 to $500 a month, default $100, at most $100 in your first 30 days. Covers overage on your RepoStaff bill only. Reaching it stops new and active runs
Org safety budgetOn by default, amount set by you. Reaching it stops new and active runsRequired, amount set by you. Reaching it stops new and active runs
Per-ticket budgetSet by you. Reaching it stops that run and hands the ticket to a personSet by you. Reaching it stops that run and hands the ticket to a person
Model keysYours, Anthropic or OpenAIYours, Anthropic or OpenAI
BillingMonthly. No annual plan at launch. Provider not selectedMonthly. No annual plan at launch. Provider not selected
Free trial14 days, one per org, card required, not charged before day 15None on hosted compute
SupportEmail, no response-time guaranteeEmail, no response-time guarantee. Hosted questions are handled first

On hosted compute, the planned most you can owe RepoStaff in a month is $699 plus your overage cap. Your model provider's invoice sits outside that figure.

What the whole bill might look like.

Model spend is usually the largest line, so RepoStaff's price alone is the wrong number to compare. These are modeled, not measured. Nothing has run yet.

Modeled hypothesis, not measured

Modeled monthly totals in US dollars, including the planned RepoStaff price. These are hypotheses, not quotes.
Usage per monthModel spendSelf-run, your hardwareSelf-run, your AWSRepoStaff-hosted compute
Light: 40 runs$243$542$668$942
Typical: 120 runs$729$1,028$1,179$1,428
Heavy: 400 runs$2,390$2,689$2,963$3,269

Model assumptions: list prices from 2026-11-08, workers on Claude Sonnet 5.5 and Marshall on Claude Opus 5.5. Token volumes are unmeasured. Your own hardware adds electricity. The heavy hosted figure includes $180 of overage. Seat-based tools usually include some model usage, so compare totals and not list prices.

Two things I won't sell you.

A free hosted trial

A free VM with a browser attracts exactly who you'd expect, and hosted compute costs real money from minute one. It will need a card on file and an overage cap.

An enterprise plan

There isn't one: no SOC 2, no procurement portal, no "contact sales" hiding the price. If you need those, buy from someone who has them.

Want a say in how this gets priced?

If the Management UI says it isn't worth it, cancel. The knowledge committed to your brain repo stays with you. Application history, session archives, credentials, and live services need separate export or migration.