Skip to content
Docsturbobase.io

Billing and usage

Shipped

The console gives you usage tracking for each instance today, with self-service billing on its way for each organization. Billing is scoped to your active org: switch orgs in the nav to see another org’s billing.

Usage

Section titled “Usage”

Usage is live today. It’s tracked per instance and rolled up per billing period; each instance has a Usage view (/instances/<slug>/usage, linked from the instance’s row on the instances list) showing:

  • Current period — usage so far in the open billing period.
  • Recent periods — a history of prior periods.
  • Lifetime — cumulative totals.

The metrics Turbobase meters are:

  • Sync events — the volume of records mirrored from your connected sources.
  • AI tokens (in / out) — input and output tokens consumed by Pilot, your AI assistant, and the other AI agents in your app. Inside the app the same usage is broken down by tier (Frontier, Chat, Fast and Other); what’s reported is token counts, not a dollar figure or the underlying AI provider.
  • CPU hours, egress (GB), and peak database size (GB) — the infrastructure footprint of your instance.

These roll up from the agents running inside each instance, so what you see reflects real consumption — not an estimate.

Billing — coming soon

Section titled “Billing — coming soon”

The Billing tree (/billing) is in the console but sits behind a “coming soon” cover while the pricing model is finalized — you won’t be charged anything you haven’t seen in writing. If you need to talk pricing now, reach out to your Turbobase contact.

When billing activates, the pages already under the cover open up:

  • Billing details (/billing/details) — your customer record (billing email and contact info).
  • Payment methods (/billing/payment-methods) — the cards on file; add or update a card.
  • Invoices (/billing/invoices) — your invoice history, with per-invoice detail and downloadable copies (and a CSV export of the list). Paid invoices also get a downloadable PDF receipt.
  • Add-ons (/billing/addons) — optional capabilities you can layer on top of your plan. Each add-on is priced as a flat monthly charge, metered on usage, or included up to a limit in your plan; it applies per instance or org-wide depending on the add-on, and some require Turbobase staff approval before they activate.

Who can see billing

Section titled “Who can see billing”

Billing is an org-level surface, gated by your console (customer-realm) membership of the org. It governs your subscription only; it never exposes the business data inside an instance, which is gated separately by the app’s own users. See Console overview for the realm split.

Section titled “Related”