Skip to content
Ronja Docs

Credits and AI spend

Everything Ronja does on your behalf — answering questions, running automations, building tables — consumes credits, the single metering unit across the whole product. This page explains where credits go, where to see them, and what your team experiences when they run low.

The wallet and the billing cycle

Section titled “The wallet and the billing cycle”

Your organization has a credit wallet: credits added minus credits used. Additions include automatic refills and credit purchases. Usage is measured per billing cycle — your organization’s own anniversary period, not the calendar month.

Two admin pages show the money side, and their names matter (the full name-vs-route disambiguation is on What’s the difference?):

  • Usage (in the admin sidebar) — the “Usage & billing” breakdown: Usage this cycle, Credits remaining, a cost-flow view of what drove spend, and a cost explorer you can group by user, model, or mode. Visible to admins in organizations where billing access has been enabled.
  • Billing (in the admin sidebar) — the wallet itself: Total available credits, Buy credits, and Credit extensions (your top-up history — purchases, monthly subscription refills, and trial credits, each tagged in a Method column). Super Admin only.

The Billing page with the Total available credits card and the Buy credits form The Billing page: the wallet balance, credit purchases, and the extension history.

What consumes credits

Section titled “What consumes credits”

The Usage page traces every credit “from the source that triggered the work down to the model and compute behind it”. Sources include your team’s conversations with Ronja (the Analyst and Builder lanes — Analyst covers the Standard and Deep analysis modes, Builder covers Build mode), Automations, Data apps, and the Data platform itself; behind them sit three cost types — AI usage, Processing, and Billed hours (hands-on time from the Ronja team). Build-mode work — creating and editing workflows, notes, and data apps — is the most credit-intensive.

Buying credits

Section titled “Buying credits”

When the wallet runs low, the Super Admin tops it up from the Billing page — and the cost “is added as a line on your next invoice — your card is not charged.” For the step-by-step buy-credits flow, see Usage & billing.

Running low: what your team sees

Section titled “Running low: what your team sees”

Credit enforcement is optional per organization — if yours shows “Not activated” and “Exempt from credit enforcement” on the Credits remaining tile, none of the below applies. Where it’s on, Ronja degrades gracefully rather than failing abruptly:

  1. Warnings. If your admins have set usage thresholds, crossing a user warning threshold shows every user a grey banner in chat — “Your organization is approaching its monthly credit limit.” — and a separate org warning threshold emails your admins a heads-up. Nothing is blocked.
  2. Reduced models. Past a configured downshift threshold, Ronja switches to your organization’s Reduced models set to protect the remaining pool. The chat banner reads “Running model instead of model due to company policy”. Everything resets when the cycle resets.
  3. Low balance. At the organization’s low-balance limit, chat is cost-floored to the Sonnet model — the banner reads “Running Sonnet instead of model — your organization is out of credits.” (Super Admins also see an Add credits link) — and admins receive the “Credit balance low” email. Still nothing is blocked.

Keeping spend under control

Section titled “Keeping spend under control”

Admins can shape spend long before any of this triggers: per-user monthly allocations (Limited, Unlimited, or Blocked), the warning and downshift thresholds above, and the model and effort defaults — all managed in the Control Center. See Govern AI spend.

See also

Section titled “See also”