See Every Dollar.
Optimize Everything.

Only customers whose monthly cloud spend across all connected accounts exceeds $100,000. Below that threshold the fee is zero, on every tier. Above it, the fee is 10% of the savings we verify and you realize.

The fee starts the month the saving first appears on your bill — verified by month-over-month spend reduction on the specific resource we flagged. It runs every month only while you remain subscribed. The day you cancel, both subscription and savings fees stop together. There is no tail debt and no clawback.

A measurable, month-over-month reduction in your cloud bill on a specific resource (or commitment) that CLARITY flagged in a recommendation you implemented. Snapshots, idle resources, oversized instances, missed commitments, ghost clusters — every one tracked back to the recommendation that surfaced it. If your team finds and fixes something CLARITY didn't flag, that saving is yours alone.

Subscription billing stops at the end of your term, and the 10% savings fee stops the same day. New findings stop being tracked the moment you cancel. Savings already realized continue to flow to you forever — we never claw back. Renew, and savings continue to be tracked under your new term.

A customer on the Pro plan ($2,200/mo) has $400K/mo cloud spend. CLARITY identifies $30K/mo of recoverable waste. Their team implements the fixes in month 3. Starting month 3, their cloud bill is $370K instead of $400K — that $30K reduction is the realized saving.

• Months 1–2: $2,200 subscription. Savings fee: $0 (nothing realized yet).
• Month 3 onwards: $2,200 subscription + $3,000 savings fee (10% of $30K). Customer keeps $27K of the saving every month.
• Month 12 (subscription ends): if the customer doesn't renew, the savings fee stops the same day the subscription ends. They paid 10 months of fee = $30,000 to CLARITY. They keep the full $30K/mo savings going forward forever.
• If they renew: the savings fee on this finding continues to run for as long as the saving is realized and the subscription stays active. New findings tracked during the new term work the same way.

Total to CLARITY over 12 months at this finding's pace: $36,000. Net savings to the customer over those same 12 months: $324,000. Beyond that — every month, every saving — the customer keeps 100% if they cancel.

Because the value CLARITY delivers scales with the spend it watches over, not the feature flags it ships. Every paid tier gets the full optimization engine — forecast, anomalies, K8s, AI validation, reports, the works. What changes is capacity: how much monthly cloud spend you connect, how many accounts and users, how fast we sync, and what enterprise governance you need. You don't pay extra for AI insights you should have had on day one.

We surface a soft prompt in-app, give you a 30-day grace window to either bring spend back below the cap or upgrade tiers, and your account manager (or sales) opens a conversation about which tier fits your new footprint. Nothing breaks during the grace period — sync, insights, and reports keep running. Upgrade pricing is prorated to the next billing cycle.

No. CLARITY is delivered as a fully managed SaaS — we run it for you. There is nothing to install, deploy, or maintain on your infrastructure. You connect your cloud accounts via read-only IAM roles and access CLARITY through your browser.

CLARITY is not a shared-database multi-tenant SaaS. Every customer gets a dedicated deployment: their own application container, their own PostgreSQL database, their own Redis instance, their own filesystem access point with strict POSIX permissions, and their own secrets vault. There is no cross-tenant data path — your data never sits in the same database row as another customer's.

You choose your deployment region at signup. US East (N. Virginia) is currently active; US West, EU (Ireland), and APAC (Singapore) are wired through the provisioning pipeline and ready to come online as demand picks up. Your data and your tenant deployment stay in the region you picked — we don't replicate cost data across regions.

Read-only, scoped to billing and resource discovery. AWS uses a cross-account IAM role bound by an ExternalId you control — we never receive long-lived access keys. Azure uses a service principal with Reader + Cost Management Reader + Monitoring Reader. GCP uses a service account with viewer-tier roles only. No Create / Put / Update / Delete verbs are granted on any provider.

AES-256-GCM at rest, TLS 1.3 in transit. Cloud-account credentials are encrypted with a key derived from a tenant-specific session secret stored in AWS Secrets Manager. Database, filesystem, and backups all carry server-side encryption.

Yes — on every tier, including Starter. SSO is delivered through Cloudflare Access with JWT verification, supporting SAML and OIDC providers (Okta, Google Workspace, Microsoft Entra ID, Auth0, and any SAML 2.0 IdP). Local password auth is the fallback when SSO is not configured.

Every authentication, account change, sync run, report generation, and system-level configuration event is recorded in a structured audit log scoped to your tenant. Visible in-app for admins; exportable for SIEM ingestion. Retention is per your contract.