Billing and plans
Judgment's plans, what uses Judgment Units, and how limits and usage alerts work.
Judgment bills for two things: Judgment Units (JU) for the work Judgment’s agents and judges do on your data, and gigabytes of trace ingestion. Everything is per organization. Open Settings, then Billing & Usage, to see your plan, what you’ve used this cycle, and the limits that apply.
Plans
| Developer | Pro | Enterprise | |
|---|---|---|---|
| Price | $0/month | $249/month | Custom |
| Judgment Units | 200 JU allowance per month | 1,000 prepaid JU per month, then $0.25 per JU pay as you go | Custom JU rates |
| Trace ingestion | First 50 GB free, then $0.50/GB | First 50 GB free, then $0.50/GB | Contact us |
| Projects, datasets, seats | Unlimited | Unlimited | Unlimited |
| Also included | Team training, integration help, a dedicated success manager |
Pro is the only plan you can buy in the app. On the Developer plan, the billing page shows every plan: select Select Plan on Pro to check out, or Contact Us on Enterprise. On a paid plan, the page shows only your current plan; select Compare plans to see the others. Only Admins and Owners can change the plan; everyone else sees Admin Only.
Enterprise can also run Judgment in your own cloud (BYOC). contact support for details.
What uses JUs
The billing page splits usage into two workloads.
| Workload | What counts |
|---|---|
| Evaluations/platform agent | Judges evaluating your traces and sessions, online and in test runs (Agent judges and Code judges). The Judgment Agent’s work: chats in the app, the Slack Agent, Scheduled Tasks, and Issues detection, which all run the same agent. |
| Traces | Trace ingestion after the free 50 GB. |
A JU is not a request count. To see where your JUs went, use Raw usage per workload and the project breakdown, or View Detailed Usage and Cost Breakdown.
What happens at the limit
On Developer, usage stops at the allowance. On Pro and Enterprise with pay as you go, usage continues past the included or prepaid JUs up to the PAYGO JU cap, which is 1,000 JU unless you change it.
When an organization reaches its limit, trace ingestion returns 402 with {"error": "Usage limit exceeded"}. New judge evaluations, test runs, Scheduled Task runs (including Issues detection) and the analyses that start during project setup are blocked too, until the next cycle or until you raise the limit. Rate limits are separate; see Rate limits.
You can set three kinds of limits:
| Limit | Where | What it does |
|---|---|---|
| JU limit | Each workload tab under Raw usage per workload | Caps one workload. 0 allows nothing beyond any free trace allowance. A blank field means no workload cap. |
| PAYGO JU cap | Pro and Enterprise with pay as you go | Fixed (a positive whole number) or Unlimited. The default is a fixed cap of 1,000 JU. |
| Prepaid JU cap | Some contracts | Stops usage at the prepaid amount instead of continuing into pay as you go. |
Work stops when it hits any one of these. Raising one doesn’t lift the others.
Usage alerts
Usage alerts email chosen roles when usage passes a percentage of a limit. They’re available on Developer, Pro, and Enterprise.
- On the billing page, open Usage Alerts.
- Turn on Alerts enabled.
- In Alert thresholds (%), enter whole numbers from 1 to 100, up to 10 per field. Leave a field empty to use the defaults: 90 and 100 for the included or prepaid allowance, and 50, 90, 95, and 100 for pay as you go and workload limits.
- Pick Notify roles. The default is Admin and Owner.
- Select Save.
Workload alerts only fire for a workload that has an explicit JU limit. Alerts only notify. They don’t change any limit.
Invoices and payment
Invoice History lists each invoice’s date, period, amount, and status. Select View to open one. Admins can update the card on file with Manage Payment.