Interactive demo — nothing gated
No meeting to book and no sales team to sit through. Open the sandbox, walk the loop on a sample estate, then check our claims yourself.
The sandbox — nothing gated
A fictional company with ninety days of AWS, Azure and Google Cloud billing, commitments and AI usage — the dashboards, Cost Explorer and ranked actions the product generates, on invented data that is labelled as such. Its figures are its own, from a different estate than the walkthrough below. It is read-only: a write from the sandbox is refused.
Step one · nothing to install
Three changes on the walkthrough estate. Pick one — with a click or the arrow keys — and the product answers it the way it answers every change: what changed, why, who owns it, what to do, and on what basis. The chart’s data table is open, because every chart has one. The three flagged changes account for the entire window change — nothing is left over. Add them up; that is the point of showing you the whole window rather than a headline.
The walkthrough estate. The live demo is a different fictional estate — three clouds and 90 days of history — with its own numbers.
Daily cloud spend · 14-day sample
$59,020 in 14 days
+$4,420 vs the previous 14 days ($54,600) — three events explain all of it.
Daily spend across a sample 14-day window, from $3,500 to $5,000 a day. The prior-window average of $3,900 a day is drawn as a rule across the chart. Days 1 to 8 track that rule within eighty dollars. Spend steps up on Day 9, steps up again on Day 11, then falls back on Day 13 while staying above the rule. Three changes are flagged; each is listed under Top movers, and selecting one opens the drill-down.
Daily spend, Day 1 → Day 14. The dashed rule is the prior-window average of $3,900/day and the dots mark the three cost events; the coloured rule along the bottom marks how long the selected change has been running. The money axis starts at $3,500, not at zero.
| Day | Billed cost | vs usual $3,900 | What started that day |
|---|---|---|---|
| Day 1 | $3,940 | +$40 | billed |
| Day 2 | $3,840 | −$60 | billed |
| Day 3 | $3,930 | +$30 | billed |
| Day 4 | $3,890 | −$10 | billed |
| Day 5 | $3,970 | +$70 | billed |
| Day 6 | $3,820 | −$80 | billed |
| Day 7 | $3,920 | +$20 | billed |
| Day 8 | $3,890 | −$10 | billed |
| Day 9 | $4,575 | +$675 | checkout-api · Compute · ECS Fargate |
| Day 10 | $4,465 | +$565 | billed |
| Day 11 | $4,825 | +$925 | analytics-warehouse · Data transfer · cross-AZ |
| Day 12 | $4,745 | +$845 | billed |
| Day 13 | $4,650 | +$750 | log-archive · Storage · S3 |
| Day 14 | $4,560 | +$660 | billed |
| Days 1–14 | $59,020 | +$4,420 | total · vs $54,600 in the prior 14 days |
Top movers
The autoscaling floor was raised from 6 tasks to 20 during the Day 9 incident. The incident closed on Day 10; the floor was not lowered.CloudJaeger sees the billed step on the service tag; it does not read the autoscaling setting. A configuration change is context for investigation, not proof of causation.
This build has no execution path: nothing is applied to your cloud, with or without an approval.
Step two · still no account
In your browser
Drop an AI usage export; it is priced where you are and never uploaded.
10 formats, detected automatically · AI price book 2026-10-v1, every rate labelled with how it is knownPreviewruns in your browser · AI price book 2026-10-v1Run the AI cost auditA real deliverable
The sample architecture-cost review, built by the product's own review engine over a fictional estate.
Public, printable · fictional estate, never customer data · every figure projectedPreviewAWS estates onlyRead the sample reportFor engineers
The REST and MCP surfaces, documented before you sign anything.
OpenAPI 3.1 · MCP read tools; the draft tools can only propose, and a signed-in admin confirmsOpen the developer docsStep three · nothing here needs us
Five things this site claims, and the exact way to falsify each one. Only the MCP check needs an account.
The list on /connect-security is parsed from the policy file as the page renders — 82 actions today. Count them yourself.
Open the network panel in your browser’s dev tools, then run an audit: no request carries the file.
Call it with a read key and compare the figure with the same view in the app. This one needs an account; sign-in for third-party MCP clients is still unfinished.
curl -s -X POST https://cloudjaeger.com/api/mcp -H "Authorization: Bearer cp_…" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'The manifest at /api/mcp/marketplace.json declares the archive’s checksum; fetch both and compare.
curl -s -o plugin.zip https://cloudjaeger.com/api/mcp/plugin.zip && shasum -a 256 plugin.zipEvery feature on /product and /evidence carries its status from our feature register — Live, Preview, Demo-only or Planned. /evidence adds where each one was proven and what it cannot do yet.
Try it on the sample estate first — then bring your own bill.
Apply for a design partner slot