log inget access →

pricing

Pricing.

The price has two parts: a platform fee for the product, and a prepaid balance for the work Perfloop runs on your code. Everything is in dollars, and nothing is charged automatically. These are early access tiers and prices.

Evaluation

$0

seven days · by invite

  • an included use allowance

The full product on your repositories. When the seven days end, you pick a plan or we close the workspace. There is no invoice if you stop.

get access →

Pro

$5,000/month

month-to-month · most teams start here

  • $3,000 platform
  • $2,000 included use

The platform fee covers the product, its controls and reporting, and support. Single sign-on is included; an Admin sets it up in Setup. Included use pays for the work Perfloop runs, and every case shows what it cost. If you need more within a month, you approve one prepaid invoice.

get access →

Enterprise

from $15,000/month

annual

  • $10,000 platform
  • $5,000 included use to start

An annual agreement on our standard enterprise terms, with committed usage, invoiced to your purchase order. Same product as Pro.

get access →

How the balance works.

  • Included use. The balance your plan starts with. It pays for mapping your code, deciding what to do, running cases, and research.
  • Cost. Every case shows what it cost.
  • Spend caps. A cap bounds each case; raising it is your decision.
  • Top-ups. When the balance runs out, work pauses. You approve one prepaid invoice to add more.
  • No unit fees. There is no charge per seat or per repository. A case costs what its work costs, nothing more.

Everything, in every tier.

  • Repositories. Connect GitHub and choose exactly which repositories are in scope.
  • The model. A living map of your system and how it performs, kept current as your code changes.
  • The frontier. A ranked list of cases: places in your code where a known performance pattern may apply, ordered by the strength of the evidence behind them.
  • Cases. Each one states a hypothesis, makes the change, measures the result, and verifies it.
  • Pull requests. A proven change arrives as a pull request. Perfloop can never approve or merge its own work.
  • Automatic work. Four switches per repository decide what runs on its own, from keeping the model current to opening pull requests.
  • Initiatives. Research toward a goal you set; accepted hypotheses become cases.
  • MCP server. The whole work loop as tools for your coding agents: read the model and the cases, submit ideas, start work and research, check the balance. Agents act with your permissions, and Perfloop runs the work.
  • Slack. What needs your decision, in your channel, linked straight to the case.
  • Usage. Your balance, the cost of every case, and the spend caps, all in dollars.

Enterprise adds.

  • An annual agreement. On our standard enterprise terms, signed through your procurement process and invoiced against your purchase order.
  • More use. Higher included use than Pro.

Get access.