Billing and quota enforcement
Just want to do it in the dashboard? See the guide: See what the org uses and spends or Choose which models the orgs can use, and their price.
This page explains how OpenTremor gates analysis, records billed usage, and limits monthly LLM spend. It is for platform operators and org administrators.
Deployment mode controls entitlement
Section titled “Deployment mode controls entitlement”config.deployment.mode (self_hosted or cloud) describes the deployment. It is file or environment configured and cannot be edited through the admin API. See Platform settings.
On a self_hosted deployment, every org is entitled, regardless of its plan tier or trial usage. On cloud, an org is entitled if its tier is paid or enterprise, or if it has trial analyses remaining.
The platform checks entitlement against a meter, a named unit of usage declared by a product. OpenTremor-core declares these meters:
| Meter | Unit | Purpose |
|---|---|---|
analysis | analysis | A lifetime trial of 100 successful analysis calls per org on the cloud free plan |
resource_analyzed | resource | The billed meter, priced by monthly quantity |
The trial count is stored in trial_usage.analysis. A successful analysis call consumes one trial unit if it analyzed at least one resource. Calls that analyze nothing consume no trial unit. The count uses an atomic increment, so concurrent calls each count.
Cloud requests that check entitlement can return 402 when the org has no trial allowance remaining and is not on a paying tier. The dashboard also reflects entitlement when it checks product access.
Plans determine entitlement and billing
Section titled “Plans determine entitlement and billing”| Tier | Entitlement | Billed usage |
|---|---|---|
free | Analysis is available within the lifetime trial on cloud. Self-hosted deployments are always entitled. | No metered cost is calculated. |
paid | Unlimited analysis. | The full monthly billed-meter quantity, using the configured degressive pricing tiers. |
enterprise | Unlimited analysis. | Only usage above the committed monthly allowance, at the lowest configured per-unit price. |
An enterprise org can have an OrgContract with included_units_per_month, committed_amount_usd, expires_at, and reference. A superadmin records the contract terms.
Usage events for the billed meter are recorded regardless of plan. The usage summary calculates a metered cost only for paying tiers. A commitment sets the billing basis; it does not stop usage recording.
Exceeding an enterprise commitment reports overage and a cost. It does not return 402 or stop work. An expired contract is reported for follow-up; expiry does not revoke access.
An enterprise contract without included_units_per_month has no usage ceiling. The contract is preserved if the org changes tiers, but it applies only while the org is on enterprise.
Monthly spend caps limit recorded LLM costs
Section titled “Monthly spend caps limit recorded LLM costs”An org can have an optional monthly spend cap: organizations.quota.monthly_budget_usd. The default is unlimited. Budget checks run before supported cost-incurring operations. If the org has already reached its cap, the operation is refused with 402 before it starts.
During analysis, the remaining budget is reduced by the actual cost of each unit. If the budget runs out mid-analysis, the run stops early and returns a partial result with quota_exceeded: true.
The usage total includes the cost of all usage events recorded for the current UTC calendar month. Usage summaries reset at the start of each month; there is no rollover.
View usage and configure pricing
Section titled “View usage and configure pricing”In the dashboard: Organization → Usage & Audit → Usage. The usage page shows this month’s spend, budget, billed-meter quantity, trial progress, and enterprise commitment details.
In the dashboard: Platform Admin → Billing → Pricing. A superadmin can configure the degressive price tiers. GET /v1/pricing returns the current public tiers, and PATCH /v1/admin/pricing replaces them. The defaults apply until a platform admin changes them.