Billing

Your organization's subscription, seats, invoices, and payment method — in the admin area at /admin/billing.

Viewing the page requires canViewUsage (the owner-reserved "View usage & billing" permission). Changing anything — plan, payment method, cancellation — happens in the secure billing portal, which additionally requires canManageBilling (also owner-reserved, and granted separately). A delegate who can see spend cannot silently change how the organization pays.

Plans and seats

Strata is priced per seat, billed monthly. The per-seat rate falls as your organization grows, and the plan name follows your seat band:

• Billed monthly. Sales-led plans are sold on an annual contract but invoiced every month — the contract term governs cancellation, not the billing frequency.
• How you pay. Starter and Business can be purchased online with a card. Enterprise and Global are sales-led and invoiced Net 30 (ACH, card, or wire) through your account team.
• Your band is the larger of your onboarded members and the seats you contracted for. A 25-seat Business contract stays Business even while only 12 people are onboarded, and carries Business's free-licence allowance.
• Because AI inference runs on your own Azure AI Foundry, the seat price is not a token pass-through — model tokens bill to your Azure subscription, not to Strata. See Bring your own Azure AI Foundry.

Note

Model inference is never a line on your Strata invoice. Your Strata bill is seats plus any metered compute credits; the tokens themselves land on your own Azure AI Foundry bill.

Compute credits

Alongside seats, Strata meters compute credits — its unit for finished work (generated documents, Analysis runs, scheduled agent runs, exports, dashboards). Credits are priced at a flat $0.50 per credit on every plan. On most plans today, credits accrue for reconciliation and are invoiced per your agreement rather than charged automatically; the Usage page shows the running balance and how each credit was earned. Searching, reading, and ordinary chat draw no credits — you are metered for output, not effort. See Usage → Compute credits for the full weighting.

Free trial

Organizations that sign up online start on a 14-day free trial. A card is required up front — Stripe holds it and converts the trial to a paid Starter subscription when the 14 days end — but nothing is charged during the trial, and canceling before it ends takes effect immediately with no charge.

A trial is deliberately bounded so a team can evaluate Strata without it becoming free production capacity:

Note

The trial's 150 credits meter deliverables — documents, Analysis runs, agent runs, exports — over the trial window, since that is the work that runs on Strata's own compute. Ordinary chat is not credit-metered, and its model tokens bill to your own Foundry. When the 150 credits are spent, credit-drawing work pauses for the rest of the trial; chat keeps working.

The billing page

The page reads like a statement, top to bottom:

• The figure that matters now, with a line under it: the amount due on an open invoice, this period's estimate, the last invoice, or, on a free trial, what will be charged and when. Beside it, Manage billing for an admin with that permission, and Start a subscription while no subscription is live.
• Notices, most urgent first: a payment past due or waiting for confirmation, a subscription that was canceled, is waiting for its payment or is starting, more members than seats, a rate that does not match your seat band, a paused seat sync, a subscription that ends, no payment method on file, a trial.
• Account: plan, seats in use (with pending invitations and free licenses), free licenses, contract, rate, billing period, collection (automatic, or invoiced with its terms), payment method, compute credits on a free trial, the subscription with Cancel subscription or Keep my subscription, credits, and the response fee. Your plan name is Starter, Business, Enterprise, or Global; see Plans and seats.
• Invoices: number, status, amount, due date and a link to each one, the 24 most recent.
• At the foot, how to change your plan or payment details for your kind of account.

The page is in the language you chose in Settings, with money, counts and dates written your language's way; a plan keeps its name and an invoice the number Stripe gave it.

When members have asked for more usage, an admin with Manage billing also sees their requests on this page, above the account details: the same queue as the top of the Usage page, with Approve and Decline. It is here because Manage billing, the permission that answers a request, does not by itself open the Usage page. The panel is absent when nobody is waiting.

Canceling an online subscription

If your organization signed up online (rather than under an Order Form), an administrator with billing permission can cancel from this same Organization → Billing page (/admin/billing) without contacting anyone. The control sits in the Account ledger and reads Cancel subscription; once cancellation is scheduled the same row offers Keep my subscription to reverse it. It appears only for administrators who hold canManageBilling.

• Cancellation takes effect at the end of the monthly period you have already paid for — your workspace stays fully available until then, and no further charge is made.
• You can reverse it at any point before it takes effect; the subscription simply continues.
• Canceling during the 14-day free trial takes effect immediately and no charge is made.
• The amount already charged for the current period is not refunded or prorated.

Organizations billed against an Order Form do not see this control — non-renewal for those subscriptions is handled through your account team, per the notice period in your agreement. In its place, an administrator with canManageBilling sees a note that the term is set by your agreement, with a Contact support button that opens Organization settings › Support — or, for an administrator without Manage org settings, an Email support@kronisys.com link.

If seats in use exceed seats purchased, the Seats card flags it and a banner explains the next step. Strata's enforcement is deliberately soft — going over plan never suspends your organization or blocks sign-ins; it surfaces the overage so you can true up with your account team.

Below the cards, the Invoices table lists your recent invoices (number, period, amount, status, due date) with links to the hosted invoice and PDF for each.

The billing portal

Manage billing opens a secure, Stripe-hosted portal where every payment mutation happens — updating the payment method, viewing invoices, changing the plan, or canceling. Strata never sees or stores card or bank numbers; the portal session is created server-side and the button appears only when your organization has a billing account and your role grants canManageBilling.

Opening the portal is itself recorded in the audit log as billing.portal_opened (on the Compliance tier and above).

Monthly AI spend ceiling

A monthly AI spend ceiling is a dollar cap on your organization's total AI spend in a calendar month — an organization-wide backstop, not a per-user or per-agent limit.

When the ceiling is reached, Strata pauses AI generation across every surface — chat, scheduled agents, the Teams bot, the public API, and voice — cutting a response off mid-turn if one is already in flight. A Monthly AI spend ceiling reached notice is posted to admins' inbox, and the ceiling resets automatically at the start of the next calendar month.

No ceiling is set by default. A new organization runs uncapped until an administrator sets one — the cap protects your own Azure bill rather than Kronisys's, so it is yours to choose. Leave the field blank to run uncapped. Setting or clearing the ceiling requires canManageBilling. This is now the only place it can be set. Organization → Member defaults → Rate limits states its current value read-only on a Monthly spend ceiling row, with a Set it in Billing link beside it (See it in Billing for an admin who can view billing but not manage it), so an admin reading the rate limits can see the money ceiling without there being two screens that write it.

The ceiling is enforced in real time and checked during a response, not only at the start. Requests already in flight when the line is crossed can carry a little past it, so treat it as a firm backstop rather than an absolute cut-off.

The ceiling counts Strata's estimate of model cost, not your Microsoft invoice: each request's input and output priced at that model's rates in the Model Catalog. Prompt-cache reads are priced at the model's Cached input rate where the catalog lists one, and at the full input rate where it doesn't; Anthropic prompt-cache writes are priced at 1.25 times the input rate. Each figure is priced once, when the usage is recorded, and is not recalculated later. The per-run and monthly agent spend caps under Agent quotas are estimated the same way.

Default limit per person

Under Manage billing → Default limit per person, Monthly limit per member sets what each member is capped at when neither they nor any of their groups has a limit of its own. It is per person, not shared, and it counts the estimated model usage of the member's own work, the estimate the ceiling above adds up for everyone, plus usage charges where you are invoiced for them; API keys, the support assistant and Recap do not count toward it. Leave it blank for no default; $0 stops every member who inherits it, and Billing asks before it saves one, naming how many members it would stop. Weekly pace, beside it, sets the most of their monthly limit any member may use in one week (Monday 00:00 UTC to Monday); see Spend limits for members. API service accounts and connection bots never inherit it. A member who reaches their limit can ask for more from chat or from Settings → Usage: the request waits on the Usage and Billing pages for an admin who can manage billing, and the member is emailed the answer. See Spend limits for members.

Permissions

Both are owner-reserved capabilities: they can only be granted from an owner-tier role. See Roles and permissions.

How provisioning works

Subscriptions are provisioned only when payment lands — an invoice being sent changes nothing in your workspace; the plan, seat count, and renewal date on the billing page update when the invoice is paid. The page itself renders from Strata's local billing mirror (kept fresh by payment-provider webhooks), so it loads instantly and never blocks on an external API.

What can go wrong

Related

• Usage
• Bring your own Azure AI Foundry
• Roles and permissions
• Audit log
• Organization