Platform settings: limits

Platform Settings holds the DataMind staff settings for the platform itself. The Limits tab sets the platform-wide limit defaults and the per-company overrides that every company's requests are measured against. Use it to change a default for all companies, or to give one company its own rate, concurrency or spend values. Limits is the tab Platform Settings opens on by default, and only DataMind staff accounts can open the area; the client's own settings live in Settings.

Edit the global defaults

The tab shows three tiles.

Traffic sets the default request rate per company for chat and tool requests, and the default number of requests a company can have in flight at once. Spend defaults are the money defaults, denominated in the Currency you pick (GEL or USD) and converted to each company's plan currency. Key limit (optional) is a credit limit in USD provisioned onto the platform's OpenRouter keys; leave it empty for unlimited.

The platform starts with these defaults:

1. Change one or more values.
2. Click Save defaults. The button stays disabled until you change something.

A save is refused when a value fails its check: Rate limit must be a positive integer, Max concurrent must be a positive integer, Spend cap and hard ceiling defaults must be decimal amounts, or OpenRouter key limit must be a decimal USD amount or empty. The platform also refuses a Spend cap default above the Hard ceiling default.

Set a company override

A company can hold its own values. Open them from the Companies list.

1. Open Companies.
2. On the company's row, open the Company actions menu and choose Limits.
3. Fill in Rate limit / minute, Max concurrent, Spend cap (CCY) and Hard ceiling (CCY).
4. Click Save overrides. It stays disabled until you change something.

The dialog is titled Company limits · {companyName}. Its note reads: "Per-company overrides. Saving pins these values (they no longer follow global defaults live). Money fields use the plan currency (CCY)."

• Each value stands on its own. Saving pins the values you set and leaves the rest as they are.
• Clearing a value returns it to the global default; from then on the company follows later changes to that default.
• The dialog shows Enforced today with the amount the platform applies, min(cap, ceiling), the subscription state, and the Premium and Standard allowance lines with their overage rates per 1M tokens.

The override fields are checked the same way; their messages read Rate limit must be a positive integer, Max concurrent must be a positive integer and Spend cap and hard ceiling must be decimal amounts (max 2 places), plus Spend cap cannot exceed the hard ceiling. Closing the dialog with unsaved edits raises Unsaved Changes, with Discard & Close and Keep Editing.

Saving an override shows Company limits updated; saving the defaults shows Limit settings updated.

What the limits do

• The amount enforced is the lower of the two money values: min(cap, ceiling). A cap saved above a later-lowered ceiling stays saved, but is never enforced above the ceiling.
• The cap gates billable extras only: Premium overage, Standard overage and pay-as-you-go. Tokens included in the plan serve first and are not refused by the cap.
• Once billable extras reach the enforced cap, further billable requests are refused until the next billing window opens or the cap is raised. For the refusal statuses and retry rules, see Limits and the spend cap.
• On a plan that prices no Standard overage, raising the cap does not help: Standard requests stop at the allowance, and the company sees Standard requests are being refused.
• A company's own Administrator can set the cap up to the ceiling on the Spend cap card in Settings. A value above the ceiling is refused with Cannot exceed the ceiling of {amount}. Contact support to raise it. Saving there shows Spend cap updated.

Saved changes apply to new requests; nothing needs a restart.

Usage alerts

The meters on this tab feed the usage alerts. There are eight kinds. Six watch the meters: a 70% alert and a 100% alert for the Premium token allowance, the Standard token allowance and the spend cap. Two are plan-change suggestions, sent on day 24 of the window and on its second-to-last day, and only when another plan would save at least 5% of the current price. A suggestion can point to a larger or a smaller plan, and each kind goes out at most once for a company in a billing window. For how the billing window works, see Billing.

Questions, answered

Which companies follow the global defaults?

Every company without an override. It follows each change to the defaults live. A company that has pinned a value keeps that value until someone clears it.

Do saved overrides follow later changes to the defaults?

No. Saving pins them, as the dialog says: "they no longer follow global defaults live". Clear a value to hand that field back to the defaults.

How do I make a company follow the global defaults again?

Open its Company limits dialog from Companies, clear the values you no longer want pinned, and save. The cleared fields follow the defaults again, including later changes.

What is the enforced spend cap?

The lower of the company's spend cap and its hard ceiling: min(cap, ceiling). The dialog shows it as Enforced today, and it is the number the platform applies.

Why can't I set a spend cap above the ceiling?

The ceiling is the highest cap a company may hold, so a cap above it is refused. The dialog shows Spend cap cannot exceed the hard ceiling, and the company's own attempt on its Spend cap card is refused with Cannot exceed the ceiling of {amount}. Contact support to raise it. Raise the Hard ceiling first if the company needs a higher cap.

Does the spend cap stop a company's plan tokens?

No. The tokens included in the plan serve first. The cap gates only billable extras: Premium overage, Standard overage and pay-as-you-go. When the extras reach the enforced cap, billable requests are refused until the next billing window or a raised cap.

What does leaving Key limit (optional) empty do?

It leaves the platform's OpenRouter keys without a credit limit; the field's note reads "Leave empty for unlimited." Enter a value to provision a credit limit in USD.

What does Remaining credits show?

The platform's own OpenRouter balance, as {used} used of {total} purchased. The tile warns below 10% of the purchased balance and turns to an error at zero. It is a readout only: a low balance never changes the defaults above.

What values do the limit fields accept?

A positive whole number for the traffic fields, a decimal with at most 2 places for the money fields, and a decimal USD amount or nothing for the key limit. A spend cap cannot be above its hard ceiling.