Pay for what's asked
Billing tracks the questions answered across your widgets and API, not a flat per-seat fee. Quiet months cost less; growth months scale with the value your users are getting.
Hard caps, soft alerts, or pay-as-you-go — choose your model per tier. Set spend ceilings at any level so an AI bill never surprises you.
Set a hard cap, a soft alert, or pay-as-you-go on every dimension. The figures below are illustrative examples, not list prices.
tableArth.ai is priced on usage, not seats. You pay for the AI analytics your customers actually use — so cost scales with adoption, never with how many users you provision.
Billing tracks the questions answered across your widgets and API, not a flat per-seat fee. Quiet months cost less; growth months scale with the value your users are getting.
Tiers map to your rollout — a starter footprint for a single dataset or pilot, a growth tier as more customers turn it on, and an enterprise tier adding SSO/SCIM, audit logging, bring-your-own-LLM, and on-prem privacy modes. Every tier ships the same engine and four privacy modes.
Three levers: how many questions get asked, which privacy mode you run (Local template makes no external AI calls, so it carries no model cost), and whether you bring your own LLM key. Spend caps at every level keep all three predictable.
There's no public price list because the right number depends on your customer base and query volume. Talk to sales and we'll build a cost model with you — most teams start with one dataset on a single plan tier and expand from there.
Match your seat count, query volume, and privacy posture. Adjust the options below to see live pricing.
Across every customer and user — surfaced in a built-in dashboard and piped to your data warehouse on request.
Pricing is usage-based and tailored to your customer base and query volume, so there's no flat list price. Most teams start with one dataset on a single plan tier and expand as adoption grows. Talk to sales and we'll build a cost model with you.
Usage-based. You pay for the AI analytics your customers actually use — measured by questions answered — not a flat fee per user. Cost scales with adoption, not with how many seats you provision.
Yes — that's the core of how cost control works. You set spend ceilings per widget, per API endpoint, per customer, or per user, so the bill can't run away even if usage spikes.
A hard cap stops usage when the ceiling is reached. A soft alert notifies you but lets usage continue. Pay-as-you-go bills for what's used with no ceiling. You choose the model per tier and per dimension.
They can. Local template mode makes no external AI calls, so it carries no model cost, and Hybrid mode sends only column statistics rather than full rows. Running stricter modes for some customers or tables is one of the levers you can use to manage spend.
Yes. Most rollouts begin as a scoped pilot on a single dataset so you can see answer quality and adoption before expanding. Book a demo to scope one.
Tell us about your plan tiers and customer base. We’ll walk through the pricing that fits.