Pricing
Free to start. Install the MCP. Pay only when it becomes team infrastructure.
Your personal context layer is free and unmetered: connect ClariLayer to Claude Code, Cursor, or Codex and use recall, remember, bootstrap, and reconcile for your own data. Usage credits and Enterprise Controls only enter the picture when your context merges into shared team infrastructure.
Start free
Install the MCP and use recall, remember, bootstrap, and reconcile for your own data — free, unmetered, no card.
Add credits
When your context becomes shared team infrastructure, credits cover variable AI, warehouse, validation, deploy, and rollback work.
Talk Enterprise
Enterprise Controls add SSO, SCIM, audit export, committed credits, support, and security review for production rollouts.
Free Core · single-player
The context layer for your AI — free for one analyst.
Stop re-explaining your data to your AI every session. Install ClariLayer as an MCP server and your agent stops making the same data mistakes — wrong table, wrong join, refunds counted in revenue. No card, no usage meter, no per-seat fee.
- Install the ClariLayer MCP into Claude Code, Cursor, or Codex — one connection
- recall, remember, bootstrap, and reconcile — the four context verbs, unmetered
- Bootstrap your real working context from the SQL and dbt models you already have
- Reconcile a saved definition against your warehouse — mismatches surface as a caveat
- Your context compounds session after session — no per-seat fee, no usage meter
Honest note: reconcile grounds a saved definition against your real warehouse result and flags mismatches as a caveat — it does not stamp entries as “verified” today. A stronger verified mark is the documented trajectory, not a current capability.
When it becomes production infrastructure, you pay for usage and controls.
ClariLayer starts as your personal context layer. As teams adopt it, the personal context analysts build merges into shared, owned, governed team context. That team-merge moment — not the single-player loop — is what Usage Credits and Enterprise Controls cover.
When it becomes shared infrastructure
Usage Credits
When your context merges into shared, owned team metrics, credits cover the variable AI, warehouse, validation, deploy, and rollback work that grows with real operational usage.
- AI conversations, generated summaries, catalog refreshes, validations, deploys, and rollbacks can spend credits
- API contract reads stay observe-only during beta — recorded for visibility, not debited
- Self-serve credit packs are available from billing settings after signup and admin setup
- Committed credits are handled through sales-led agreements
- Admins review balances, warnings, receipts, and reversals in billing settings
Sales-managed
Enterprise Controls
Talk to sales when ClariLayer becomes production infrastructure that needs deeper security, admin controls, and committed terms.
- SSO/SAML, SCIM, and advanced identity administration
- Advanced integrations and admin controls
- Audit export, log retention, and data lifecycle controls
- Committed-credit terms, security review, and support commitments
- Migration planning for existing paid subscribers
Capability Model (for teams)
Two clear buying lanes once a team adopts it, no feature-tier maze.
Credits scale the parts of the team product with variable AI, warehouse, and automation cost. Enterprise Controls cover the security, compliance, and commercial commitments that need a shared rollout plan. The single-player MCP stays free underneath all of it.
When teams adopt it
- Shared, owned, governed team metrics — the merge of personal context
- Metric authoring, definition governance, and registry browsing
- Release bundles, approval collaboration, and reasoning notes
- Members, roles, basic API keys, and connectors
Uses credits
- AI conversations and generated summaries
- Warehouse catalog refreshes and validations
- Validation fixes, approved deploys, and rollbacks
- Paid top-ups and committed-credit agreements
Stays free during beta
- API contract reads (observe-only — recorded, not debited)
- Normal product navigation and registry reads
- Comments, approvals, notes, and pinned context
- Manual metric edits and governance collaboration
Enterprise-only controls
- SSO/SAML, SCIM, and advanced identity policy
- Advanced integrations and admin controls
- Audit export, retention, and data lifecycle administration
- Committed credits, security review, and support commitments
What happens after the free credits
The single-player MCP never spends credits. For the team product, every workspace receives 5,000 free credits each month. Admins can buy self-serve packs from billing settings after signup and admin setup. Larger committed-credit agreements remain sales-led.
The single-player MCP — install, recall, remember, bootstrap, reconcile — is free and unmetered. There is no solo paywall and no single-player usage meter.
Free Core is the public signup path. New workspaces still have revenue-safety throttles and an emergency activation disable switch behind the scenes.
Public dollar prices are not listed on this page. After signup and admin setup, workspace admins can buy approved self-serve credit packs from billing settings.
Committed credits, custom terms, security review, and support commitments remain sales-led.
API contract reads are recorded for visibility during beta but do not spend credits. AI assistance, warehouse work, validation, deploy, and rollback automation can spend credits.
If credit usage is reversed after a failed operation, the reversal appears in the billing receipt trail.
Existing customers will receive migration communication before any subscription or credit transition action.
Credit Consumption (for teams)
Credits are for AI assistance, warehouse work, and deployment automation.
These are team-product actions. Free monthly credits are consumed before paid or committed credits. Normal reads, comments, approvals, notes, and API contract reads stay free or observe-only during beta — and the single-player MCP is never metered at all.
AI-assisted metric conversation
Starting a guided AI conversation to define or refine a team metric.
25 credits per conversation start
About 200 if used only for this action
AI-written metric summary
Generating an AI-written explanation for a metric contract.
50 credits per generated summary
About 100 if used only for this action
Warehouse catalog refresh
Refreshing warehouse metadata so metric work uses current tables and columns.
100 credits per catalog refresh
About 50 if used only for this action
Warehouse validation run
Checking a metric against the connected warehouse from the workflow.
100 credits per validation run
About 50 if used only for this action
Draft metric validation
Checking a draft metric change before release.
100 credits per draft validation
About 50 if used only for this action
Validation fix or retry
Running a follow-up fix, retry, or investigation from validation results.
100 credits per validation action
About 50 if used only for this action
Approved metric view deploy
Deploying an approved Tier 0 metric as a warehouse view.
250 credits per deployment
About 20 if used only for this action
Metric view rollback
Rolling back a previously deployed metric view.
250 credits per rollback
About 20 if used only for this action
The examples assume all 5,000 monthly free credits are spent on one action type. Real usage is a mix, and every debit or reversal appears in billing settings.
Expansion Path
Start free as one analyst, expand through usage and controls.
Prove the personal context loop first — for free. As your context merges into shared team metrics and agents, dashboards, and internal systems start depending on it, credits and Enterprise Controls create a commercial path without ever closing off the free single-player core.
- 01
Connect your AI and install the ClariLayer MCP — free, no card.
- 02
Use recall, remember, bootstrap, and reconcile against your own data.
- 03
Merge your context into shared team metrics as colleagues adopt it.
- 04
Add credits for variable AI and automation; talk to sales for Enterprise Controls.
Stop re-explaining your data. Connect your AI — free.
Install the MCP and start now. Add usage credits or Enterprise Controls only when your context becomes shared team infrastructure.