AI
Token economics, not just totals
Split every dollar into rate, volume and mix. When the bill jumps 28% on lower usage, the waterfall says so — and names the model and token class that did it.
Blended rate $0.94 → $1.32/M on 9% lower volume
AI · Cloud · SaaS in one ledger
Technology spend, understood
Most tools tell you the bill went up. This one tells you whether that was price, usage, or what you moved between them — and shows the arithmetic.
Read-only keys · free beta · no card required
Why the bill changed — last 30 days+$5,757 (28%)
Volume fell. The increase was almost entirely rate — the price per token moved, not how much you sent.
Three kinds of spend, one place
They behave differently, so they are measured differently — and reconciled to the same total.
Cloud
Evidence before advice
Recommendations carry the utilization that justifies them — CPU, memory, disk, liveness — so rightsizing is a decision you can defend, not a guess from a billing line.
Idle VMs flagged with the CPU and memory that prove it
SaaS
Seats you're paying for and nobody uses
Licences reconciled against real activity from Microsoft Graph and a register you control, with an owner against every subscription.
59 vendors reconciled against real sign-in activity
From keys to a number you trust
01
Connect read-only keys
Anthropic, OpenAI, Azure, GCP, Microsoft 365. Nothing writes back.
02
Spend lands in one ledger
FOCUS-aligned, idempotent, restatement-safe — the first sync backfills history.
03
Act on what it finds
Every finding shows its arithmetic, so you can check it before you act.
Anomalies, with a baseline
A day is flagged against its own trailing history, per service and per key — so a runaway agent loop surfaces the morning it happens, not on the invoice.
Seats you can actually reclaim
Assigned licences checked against real activity, with an owner on every subscription so the cancellation conversation has someone to have it with.
Built to hold more than one company
Isolation is enforced by the database, not by remembering to write the right query.
Row-level security
Each tenant reads only its own rows, enforced by Postgres policies under a role with no bypass.
Read-only credentials
Connectors ask for read scopes and never write back to your providers.
Encrypted per tenant
Connector secrets are encrypted with a key derived per workspace, not one shared key.
Roles that mean something
Owner, admin, member, viewer — every action checks a capability, and unknown roles get nothing.
Create your workspace
Free while in beta. Connect one provider and the first sync backfills recent history, so there is something real to look at within minutes.
Takes a minute · no credit card · invite your team after