Pricing

Pricing for the frontier AI ecosystem.

Standard Perception console questions are included - not NTU-metered. NTUs cover analyze, tools, and runs. Start on Free, then upgrade when you need a paid plan.

Annual billing selected. Prices shown per month, billed annually.

Free

For teams getting started

$0

Request Access

Key Features:

  • No card required
  • Up to 5 users
  • 100 lifetime NTUs/user (pooled)
  • 1 workspace
  • Agents in Conflux, chats & syncs
  • Connectors, wikis and vaults
  • Governance by design

Scale

For larger organisations

$120 /user/month

Request Access

Everything in Team, plus:

  • 2,000 NTUs per user/month (pooled)
  • Unlimited workspaces
  • SSO (SAML)
  • 24/7 support

Enterprise

For large organizations

Custom

Contact us

Everything in Scale, plus:

  • Custom NTU allowance
  • Unlimited seats (contract)
  • VPC / dedicated deployment
  • SAML + SCIM
  • Dedicated customer success
Tokenminning

Maximum outcome per token - not maximum spend.

Matching model size, context window, and modality to the actual task. Faster answers, lower NTU spend, and the same or better quality.

  • Efficient NTUs
  • Wasted NTUs
  • NTU spend
Illustrative weekly view: as Nimbus learns your workloads, efficient NTUs grow and spend falls.
Why NTUs compound

Spend less over time, not more.

Context that compounds

Past runs inform the next. Your teams stop paying to re-explain what the platform already knows.

Smarter model routing

Routine steps use efficient models. Frontier reasoning only where the work actually demands it.

NTUs that trend down

The same deliverable costs fewer NTUs over time - more ROI from every month on the platform.

Quotes before high-commitment work

Reports, Confirm & run, external writes, and large index jobs show an NTU estimate upfront with a hard ceiling - no silent overruns on governed actions.

Failed runs cost nothing

NTUs book on successful runs only. A bad attempt does not tax your allowance - retry without paying twice.

One pooled allowance

Org-wide NTU budget with shared visibility - finance gets one ceiling to manage, not per-seat AI sprawl.

Same deliverable, lower cost

Context accumulates, routing improves, and the next governed run quotes fewer NTUs.

Run 1Q3 forecast pack
Quote840 NTU
Ceiling1260 NTU

Fresh wiki + first connector pull

Run 6Q3 forecast pack
Quote520 NTU
Ceiling780 NTU

Prior runs + updated ledger context

Run 12Q3 forecast pack
Quote390 NTU
Ceiling585 NTU

Full lifecycle graph + routed models

FAQ

Pricing questions.

What exactly is an NTU?

An NTU (Nimbus Token Unit) is a work credit for completed AI activity - analyze turns, tool calls, reports, governed runs, writes, and index jobs. It is not a raw LLM token count. High-commitment work shows a quote and ceiling before you confirm; everyday Analyze usage is metered silently and visible on your Usage dashboard.

Are Perception console questions billed?

No. Standard questions in the Perception console (general questions with no retrieval) are included and do not consume NTUs. If a turn escalates into Analyze-class work - retrieval, tools, or deeper analysis - that billable work draws from your org NTU pool.

How do team members share NTUs?

Free orgs share one lifetime pool - each member adds 100 NTUs, up to five people. Paid Team and Scale plans share one monthly pool built from NTUs per seat, so finance has a single ceiling in Settings → Usage & Billing.

What happens if we run out of NTUs?

Nimbus alerts you near about 85% of your pool. On Free, invite another member (up to five) to add 100 lifetime NTUs, or upgrade. On Team and Scale, add seats or wait for the monthly reset. Quoted work pauses until you have capacity.

Can we scale without changing tiers?

Yes. Team and Scale support up to 50 seats. When you need a custom allowance, unlimited seats, or a dedicated deployment, talk to us about Enterprise.

Can I try Nimbus before committing?

Yes. Start on Free with no card. Each member adds 100 lifetime NTUs. Upgrade to Team or Scale when you need paid seats and a monthly NTU pool.

Do failed runs consume NTUs?

No. NTUs are booked on successful runs only. If a run fails you are not charged; a successful retry books the quoted amount.

Get started for free.

Connect your first tool and run a governed workstream in minutes.