Usage & billing

The Usage page is where you see, in detail, what your organization’s credits went toward this cycle — “from the source that triggered the work down to the model and compute behind it.” Open it from the admin sidebar under Usage & Control. (A note on names: the sidebar label is Usage and the page title is Usage & billing — buying credits lives on a separate Billing page, covered at the end.)

Everything on this page is measured in credits, and always as billed figures — the numbers that actually count against your organization. There are no raw vendor costs, margins, or multipliers anywhere here; a flagged admin sees exactly the same figures.

The two KPI tiles

The header shows two tiles side by side:

Usage this cycle — the total credits used so far this cycle, with a meter splitting AI usage from the rest and a delta reading “% vs last cycle · day N of M”. This is spend; it is not a limit.
Credits remaining — your organization’s wallet balance. When the wallet is funded, this shows a number with a colored meter and, if a refill is scheduled, a “+N on date” chip. If credit enforcement is off for your organization, it reads Not activated with “Exempt from credit enforcement” instead. A depleted wallet shows red.

The subtitle sums up the page: “What’s driving your usage this cycle, end-to-end — from the source that triggered the work down to the model and compute behind it. Metered in credits.”

Stepping through cycles

Ronja bills over your organization’s own anniversary period, not the calendar month. Use the ‹ › cycle stepper next to the header to move to earlier billing cycles; the label and date range come from Ronja. You can’t step into the future.

Cost flow — where credits go

The Cost flow card is the heart of the page. Its hint reads “Every credit, from the source that triggered it to the model & compute behind it,” and it has two views you switch between with a Flow | Trend toggle:

Flow is a Sankey diagram: credits flow from sources on the left to types on the right.
Trend is a stacked daily area chart of the same families over the cycle.

The Cost flow card in Flow view, tracing sources to cost types Cost flow, Flow view: each source on the left feeds into AI usage, Processing, or Billed hours on the right.

Sources — what kicked off the work:

Analyst — asking Ronja questions and exploring data in chat (the Standard and Deep analysis modes).
Builder — Build mode work: creating and editing workflows, notes, and data apps.
Automations — scheduled and triggered runs.
Data apps — interactive apps your team opens.
Data platform — the data-processing layer itself (queries, table builds).
System — background work Ronja does on its own.

Types — the work behind each credit:

AI usage — the model calls behind conversations and agent work.
Processing — queries, pipelines, and table builds.
Billed hours — hands-on time billed by the Ronja team for professional services.

If a cycle has no measurable usage, the card shows “No measurable usage this cycle” — usage appears as your team runs explorations, automations, and data jobs.

The cost glossary

Every source and type has a plain-language definition. Click the ? on the Cost flow card to open the glossary popover — for example, Analyst is “Asking Ronja questions and exploring your data in chat,” and Billed hours is “Hands-on time billed by the Ronja team for professional services.” Reach for it whenever a label isn’t self-explanatory.

The Cost explorer

Below Cost flow, the Cost explorer breaks the same credits into a sortable table. Change the grouping to answer different questions:

Source — which lane (Analyst, Builder, Automations, …) is driving spend, with a composition breakdown.
User — spend per person, with their session count and a “% builder” sub-figure so you can see who’s doing the credit-intensive build work. (This is the default grouping.)
Model — spend by model and vendor.
Mode — Analyst mode (Standard + Deep analysis) vs Builder mode (Build), with session counts.
Recent explorations — the latest sessions, each with owner, when, and its mix.
Billed hours — professional-services entries: date, consultant, hours, and note.

Sort by the Usage column to find the biggest line. All figures are billed credits, shown to two decimals.

Buying credits (Super Admin)

Topping up the wallet happens on the separate Billing page (sidebar → Usage & Control → Billing), which only the Super Admin can open. Credit purchases are invoiced, not charged to a card.

Open Billing. The Total available credits card shows the wallet balance, with “N added · N used” beneath it. (If your organization has never been funded and enforcement is off, it reads “Not enrolled.”)
In Buy credits, enter a Credit amount. A live Cost preview and a per-credit rate appear as you type.
Click Buy credits, then Confirm in the Confirm credit purchase modal — it restates the dollar amount and credit count.

Credits top up the wallet immediately (allow up to about 20 seconds to take effect); “the cost is added as a line on your next invoice — your card is not charged.” The Credit extensions table records your wallet top-ups, not only purchases: card and invoice purchases, your monthly subscription refills, and trial credits. Each row shows the date, credits, cost, a Method column that distinguishes them (Card, Invoice, Subscription refill, or Trial credits), and — for purchases — who bought them.