Skip to main content

Interactive demo — nothing gated

Follow a cost increase from chart to review.

Explore CloudJaeger on a fictional sample estate. See what changed, inspect ownership and review the next action — no signup required.

Opens immediately, with nothing to fill in and nobody to book

The sandbox — nothing gated

Open the sandbox and click through the real thing.

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.

No signup, no card, no install — a fictional estate you can click through.

Step one · nothing to install

See the change, the owner and the next review.

Pick one of three sample cost changes with a click or the arrow keys. Explore the owner, the team’s explanation and the suggested review. The three flagged changes add up to the change for the whole sample period.

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.

Sep 1 – 14, 2026 · compared with Aug 18 – 31 · billed cost · USD

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.

Daily spend on the walkthrough estate, Day 1 to Day 14, USD, against the usual $3,900 a day. The total row equals the window total.
DayBilled costvs usual $3,900What started that day
Day 1$3,940+$40billed
Day 2$3,840−$60billed
Day 3$3,930+$30billed
Day 4$3,890−$10billed
Day 5$3,970+$70billed
Day 6$3,820−$80billed
Day 7$3,920+$20billed
Day 8$3,890−$10billed
Day 9$4,575+$675checkout-api · Compute · ECS Fargate
Day 10$4,465+$565billed
Day 11$4,825+$925analytics-warehouse · Data transfer · cross-AZ
Day 12$4,745+$845billed
Day 13$4,650+$750log-archive · Storage · S3
Day 14$4,560+$660billed
Days 1–14$59,020+$4,420total · vs $54,600 in the prior 14 days

Top movers

What changed
+$3,720 over the window on checkout-api. Compute on checkout-api stepped up on Day 9 and has not come back down.
Why
A note from Payments, written by a person — not detected by CloudJaeger: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.
Who owns it
Payments — matched from the service tag on the running tasks.
What to do
Review the task floor with Payments; if it returns to 6 tasks, the step stops.$18,600/month projected at today’s run rate. Savings stay projected until your bill proves them.
On what basis
AWS billing (Cost Explorer, by tag) · synced 4 hours ago · high confidenceThe step holds across six consecutive billing days. Ranking, not a measured probability.

CloudJaeger FinOps has no execution path: nothing is applied to your cloud.

Illustrative product view — not customer data.

Step two · still no account

Then run it on something real.

In your browser

Price your own AI spend, in this tab

Drop an AI usage export; it is priced where you are and never uploaded.

10 formats, detected automatically · AI price book 2026-10-v2, every rate labelled with how it is knownPreviewruns in your browser · AI price book 2026-10-v2Run the AI cost audit

A real deliverable

Read the deliverable in full

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 report

For engineers

Read the API before you have a key

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 docs

Step three · nothing here needs us

See how the workflow is backed.

Inspect the permissions, browser-local audit and supporting evidence. The MCP check requires an account.

  1. The AWS role for CloudJaeger FinOps is read-only, and listed action by action.

    Inspect the published policy on /connect-security — its 109 actions are read directly from the policy file.

    Open the permissions list

  2. The file you drop into the AI cost audit never leaves your browser.

    Open the network panel in your browser’s dev tools, then run an audit: no request carries the file.

    Open the AI cost audit

  3. Key-based MCP answers agree to the cent with the web app.

    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"}'
  4. The agent plugin we publish is hash-pinned in a public manifest.

    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.zip
  5. Find the supported providers and prerequisites for each feature.

    Feature labels on /product and /evidence show availability, supported scope and prerequisites. The evidence page includes validation details.

    Open the evidence page

Try it on the sample estate first — then bring your own bill.

Request access