Pricing that starts read-only.
CloudJaeger pricing is scoped manually during beta based on tracked spend, connected accounts, usage, integrations, and support needs. Start with a read-only pilot; access and terms are owner-approved.
Read-only Pilot
A 14-day guided evaluation on your own bill — keep the findings report either way.
- 14-day guided evaluation
- One AWS account to start
- Read-only scan — we publish the exact policy
- Cost Explorer
- Action Center preview
- No execution · no credit card
What day 14 looks like
- Read-only connection completed — or the Day-0 CSV audit instead
- First findings report delivered (yours to keep)
- At least one architecture/cost recommendation reviewed together
- Missing-data and confidence labels understood — we show gaps instead of guessing
- Next action agreed: continue, pause, or validate one recommendation against your bill (projected until it settles)
Not ready to grant a role? Bring one month of CSV bill data — the Day-0 audit runs without credentials, inside the private beta.
Design Partner
For teams shaping the product — first, with the attention that implies.
- Founder-led onboarding
- Workflow review with your team
- Ownership, waste, Kubernetes, and Jira scope by need
- Pricing discussed after pilot scope
Growth / Scale
For larger estates and multi-account environments.
- Custom scope across accounts and clouds
- Security review
- Support and advisory cadence
- Usage- and spend-based commercial model
Private beta. Access and commercial terms are manually approved. No credit card. No live billing today.
Want to see what the pilot returns first? See a sample report → — a full architecture-cost review generated from a deterministic demo estate.
Why pricing is scoped manually during beta
CloudJaeger is in private beta. Pricing is scoped manually because the commercial model depends on tracked spend, number of connected accounts, users, integrations, Kubernetes usage, data/API/LLM volume, and advisory/support scope. None of these are metered per customer yet, so a printed price would be a guess wearing a suit.
No live billing exists during the beta — deliberately. There is no card on file and no self-serve purchase; commercial terms are agreed in writing before anything starts. A public price you cannot transact is marketing theater; a scoped conversation is a commitment we can actually honor.
Design-partner terms follow pilot scope. The first teams shape the product, and their terms should reflect that scope and contribution — not a rate card written before any pilot has run.
Post-pilot data will set public numbers — once. Public prices are anchors that are expensive to move in either direction. When pilots have produced measured estates and real usage, we will publish numbers with evidence behind them.
What affects your pricing
Nine factors — most are measured during the pilot, on your real estate.
- Tracked cloud spend
The monthly bill volume CloudJaeger syncs and analyzes.
- Users
How many people read, triage, and approve findings.
- Connected accounts
Accounts and payer organizations in scope.
- Integrations (Jira / workflow)
Ticket creation, status read-back, and workflow surface area.
- Kubernetes / Prometheus usage
Clusters and metrics volume on the cost-basis ladder.
- API / LLM usage
AI-cost ingest calls (token-level spend) and explanation volume.
- Data volume
Billing lines, inventory, and history retained.
- Support & advisory scope
Cadence and depth of founder-led advisory.
- Design-partner scope
What we shape together, and how much of it.
What happens next
Request → founder review → read-only role → first findings in the first meeting. On our estate, first findings landed in sixteen seconds.
- 1Submit request
Tell us about your estate and what you want to evaluate — no account is created.
- 2Founder review
A founder reads every request and approves access manually.
- 3Invite
Approved requests get a personal invite — access stays owner-approved.
- 4Read-only pilot
A read-only first scan — we publish the exact policy; delete the role any time.
Pricing FAQ
Why are there no public prices yet?
Because we could not honor them yet. The price drivers — tracked spend, users, accounts, integrations, usage — are not metered per customer today, and no live billing exists during the beta. Instead of printing a number you cannot transact, we scope terms manually in a conversation, and post-pilot data will set public prices once.
What affects pricing?
Nine things, listed above: tracked cloud spend, users, connected accounts, integrations such as Jira and workflow, Kubernetes and Prometheus usage, API and LLM usage, data volume, support and advisory scope, and design-partner scope. The pilot measures most of these on your real estate — which is why terms are discussed after it, not before.
What happens after the pilot?
The pilot is fixed at 14 days on one AWS account with a read-only role — we publish the exact policy and you can delete the role at any time. The findings report is yours to keep either way. If you continue, commercial terms are scoped to what the pilot actually measured; nothing converts automatically. No credit card. No live billing today.
Is there an SLA?
No. There is no SLA during the beta — we will not sell a service level we have not proven. An SLA arrives when we can stand behind one, and it will be written down before it is sold.
Questions about access, data, or execution? Read the FAQ or request access and we will reach out.
Read-only first: you connect a read-only role and we publish the exact policy. Execution ships off — arming it requires your written mandate with caps, and live purchases are hard-blocked today. Savings are projected first and graded against your real bill after you act. View security posture →