Skip to main content
Three tiers. The levers are projects and retention — not seats, and not runs. Prices and limits are read from one config on our side and rendered on the pricing page, the product page and your billing tab — so they cannot disagree with what you are charged.

What is not metered

Runs. Evals are bursty and CI-shaped, and metering them would show you a frightening number on the exact day you are evaluating us. Reporting is never rate-limited and no tier restricts it — see Reporting. Seats. Unlimited from the first paid tier. Per-seat pricing punishes the agency with six developers and one client project, which is precisely the shape of team this is for.

Retention deletes less than you think

This is the part most worth reading carefully, because the natural assumption is wrong. Only per-sample detail ages out. Runs, their per-row scores, and baselines are kept forever, on every tier including free. “Is this worse than it was three months ago” is the entire value of the product — deleting the run would delete the answer. What ages out is the verbatim model input and output hanging off it, which is both the bulk of the storage and the whole of the compliance surface.
In practice: on the free tier your trend line still goes back to your first run a year later. What you lose after 14 days is the ability to open a row from back then and read what the model actually said.

Projects

The project limit is enforced when you create one — you will be told which plan you are on and what it includes, rather than the form silently failing. Existing projects are never removed if you downgrade.

Changing plan

Settings → Billing. Only the team owner can change a plan; members see why they cannot rather than a button that fails. Billing runs through Stripe, and the customer portal handles cards, invoices and cancellation.