Monthly budget
An organization that Ronja bills by invoice can have a monthly budget: a limit on how much the whole organization uses in each billing period. When it is used up, new chats and runs stop for everyone, admins included, until the next billing period starts, or until an admin raises the budget. If your organization has one, the Control Center’s Rules tab shows a Monthly budget section.
How it works
Section titled “How it works”- One billing period at a time. The budget follows your organization’s billing period, which starts on your billing date rather than on the 1st of the month. Each period starts at zero, and what you don’t use doesn’t carry over.
- Counted as on your invoice. All usage in the organization counts, automations included, the way your invoice charges for it. The platform fee is not included, and neither are hours of work billed by the Ronja team (Billed hours on the Usage page).
- Shared by the whole organization. It isn’t a per-person amount: everyone’s usage counts toward the one budget.
- A heads-up first. From 80%, your admins are emailed and everyone sees a note in the sidebar: “Your organization has used most of its monthly budget.”
What you see when it is used up
Section titled “What you see when it is used up”A note in the sidebar says “Your organization has used its monthly budget.” Its ⓘ explains when work resumes, for example “New chats and runs resume when the next billing period starts on 3 Nov, or as soon as an admin raises the budget in Control Center › Rules. Work already running finishes.” Admins see a Change the budget link; everyone else reads “Contact your administrator if you need more.”
While the budget is used up:
- A message you send is refused with the explanation: “Your organization has used its monthly budget. New chats and runs resume when the next billing period starts on 3 November 2026, or as soon as an admin raises the budget in Control Center › Rules.” What you typed stays in the chat box.
- Approve on a step, Skip for now on a form and submitting a form are refused the same way, and the step or form keeps waiting. Reject still works.
- An app’s chat panel shows Monthly budget reached with the same explanation, and no Try again.
- An answer to a question an Agent or automation asked you by email, Slack or Teams isn’t taken yet: Ronja writes back “Thanks, but I can’t carry on right now:” followed by the explanation, ending “Reply again once it is raised or the new period starts.” The question keeps waiting.
What stops and what keeps running
Section titled “What stops and what keeps running”New paid work stops for everyone: new chats with Ronja, chats in apps, Saved Agent runs, automations and workflow runs, however they are started. An automation that fires while the budget is used up runs nothing: its run history records a skipped run labelled Paused — monthly budget used, in neutral grey, with the explanation as its summary. It isn’t a failure: it doesn’t count towards a run of failures, sends no failure alert (your admins get the budget’s own emails instead) and is not run again later. The automation’s next trigger runs as usual once the budget is raised or the new billing period starts.
Work already running finishes. Queries in apps, table builds and connection syncs keep running, and so do conversations with Ronja in Slack and Microsoft Teams. All of it still counts toward the budget, so usage can end a little above 100%. A running workflow that starts another workflow is refused at that step, like any new run, and fails if it doesn’t handle the refusal.
A run that is waiting on a person, an approval or a set time keeps waiting. Ronja tries it again every minute, so it carries on within about a minute of an admin raising the budget or the new billing period starting. A run whose time to answer ran out meanwhile then carries on as it does when nobody answers.
Over the API
Section titled “Over the API”A request that starts paid work, such as sending a prompt, starting a Saved Agent run or running a workflow, answers 400 with the code monthly_budget_reached and the same explanation, naming the date the next billing period starts. Don’t retry before then unless an admin has raised the budget. See the API reference.
For admins
Section titled “For admins”Every Admin sees the budget and can change it, with or without billing access.
See how much is used
Section titled “See how much is used”- On the Rules tab, the Monthly budget section shows Your organization’s budget for each billing period, for example “1,000 credits”, and under it “This billing period: 62% used · resets 3 Nov”. The What each limit does table has a Monthly budget column.
- On the People tab, a line under the dates says, for example, “This billing period: 62% of the monthly budget · resets 3 Nov”. Once the budget is used up, a grey strip at the top says so and when work resumes, and everyone’s status reads Monthly budget used up.
- On the Usage page, the Monthly budget tile shows the budget and how much of it is used, for example “62% used · resets 3 Nov”, or No monthly budget. The Super Admin’s Billing page shows the Monthly budget in place of the balance and the purchase history: credits aren’t bought separately.
Raise or lower it
Section titled “Raise or lower it”- Open the Control Center (admin sidebar → Billing & Control → Control Center) and click Rules.
- Under Monthly budget, click Edit. If Ronja has set no budget for your organization, the section reads “No monthly budget. Nothing stops when usage grows.” and the button is Set budget.
- Enter Credits per billing period: a whole number of credits, at most 1,000,000.
- Click Save.
The change applies within about 20 seconds, so raising the budget lifts the stop without waiting for the next billing period. There is no Remove: only Ronja can take the budget away. Changing it is browser-only: an API token, the CLI and automations can’t.
Get told before and when it happens
Section titled “Get told before and when it happens”Your admins get an email at 80% and again when the budget is used up, each with a link to Rules, and Ronja is told when it is used up too. Each is sent once per billing period, and again if the budget changes: raising it while usage is still at 80% or more of the new amount sends a new heads-up. These emails are on by default; to send them somewhere else or turn them off, use the Monthly budget row in the Billing & credits section of Notification routing (admin sidebar → Governance).
If your organization has spend steps on the Spend response tab, they act at percentages of the budget: an Email a warning step at 70% fires at 70% of it, and Warn members in chat reads “Your organization is approaching its monthly budget for this billing period.”
When other limits apply too
Section titled “When other limits apply too”A used-up monthly budget comes first. Otherwise the daily AI safety limit, a separate safeguard that pauses AI until 00:00 UTC, comes before a person’s own weekly AI budget or billing-period allocation. Those per-person limits stop only that person’s chats; the monthly budget stops everyone’s work. See What each limit does.
See also
Section titled “See also”- Control Center: where the budget is set and its use is shown.
- Credits and AI spend: what credits are and what consumes them.
- Usage & billing: where the usage went.