Loading
Preparing this Costframe view
Preparing this Costframe view
Read-only cloud cost intelligence
Find cloud waste.
Prove what’s worth acting on.
Costframe turns billing, inventory, utilization, and selected governance signals into findings with evidence, estimated savings, ownership context, and clear review steps. Azure is the deepest path today; AWS and Google Cloud are readiness-gated and disclosed as such.
No provider writes · No savings commission · Evidence gaps disclosed
Synthetic demo finding
Financial optimizationMEDIUM confidenceread-only
Synthetic subscription
Commitment coverage gap
Steady synthetic VM spend is large enough to review committed-use coverage before buying more on-demand compute.
Estimated monthly impact
$777
Synthetic artifact value. Actual savings depend on provider pricing, discounts, scope, and utilization.
Evidence checked
On-demand compute baseline
Evidence missing
Existing private pricing and commitments; Hourly utilization stability
Next action
Review commitment coverage with finance and the platform owner before buying more on-demand compute.
FinOps and cloud ops
Prioritize waste, risk, stale evidence, and owners without turning a cloud console into another spreadsheet chase.
Engineering leaders
See the affected resource, why the recommendation exists, what evidence is missing, and the safest next review step.
Finance and procurement
Separate estimates from verified outcomes, preserve configured net-rate assumptions, and export reports for review.
Security reviewers
Confirm least-privilege read-only provider access, credential boundaries, audit logs, and explicit AWS/GCP limitations.
How Costframe works
A review workflow, not an auto-remediation engine.
The product exists to make cloud-cost decisions trustworthy before action. It does not describe ticket drafts as submitted tickets, Terraform drafts as applied changes, or reviewed findings as resolved savings.
01
Connect read-only access
Azure uses the broadest current path. AWS and Google Cloud are shown with provider-specific prerequisites and readiness gates.
02
Run detector logic
Costframe reads billing, inventory, utilization, pricing, and selected governance signals. It does not write to providers.
03
Review evidence-backed findings
Savings, risk, severity, affected resource, evidence gaps, and confidence remain visible before anyone changes infrastructure.
04
Assign accountable work
Recommendations, reports, ticket drafts, and review states support handoff. Drafted work is never labeled as completed remediation.
Authenticated product
See the evidence workflow before you connect a cloud.
These are direct captures of the authenticated Costframe interface in its verified no-customer-data state. They contain no invented tenant, savings, testimonial, or certification claims.
Identity
Optional access, capability boundaries, recovery guidance, and verification stay visible together.
Findings
Financial impact, evidence confidence, and unavailable data are kept distinct.
Findings truth model
High severity is not the same thing as high savings.
Financial opportunities, security posture signals, governance issues, evidence confidence, and stale or unavailable data are kept separate so a customer can understand what is known, what is estimated, and what still needs review.
Financial and non-financial examples
Savings finding
Commitment coverage gap: $777 estimated per month
Included in the synthetic savings total because it is a financial optimization finding.
Risk finding
Broad inbound management access: $0 savings impact
HIGH severity means risk. This finding contributes no monetary savings.
Artifact summary
58 synthetic findings; 22 preserve evidence-unavailable wording
The public demo contains no customer tenant, billing, user, or secret data.
Provider maturity
Same operating model, different provider depth.
Costframe is multi-cloud, but it does not claim equal evidence coverage across Azure, AWS, and Google Cloud. The onboarding path and scan eligibility stay provider-specific.
Azure
Most matureCost Management, inventory, selected governance signals, and Azure VDI paths have the deepest implementation.
Review setupAWS
Readiness-gatedIAM role setup, external ID, Cost Explorer, inventory, and optional permissions are validated against narrower coverage.
Review setupGoogle Cloud
Readiness-gatedService-account or federation setup and billing-export requirements determine which findings can be trusted.
Review setupCommercial clarity
Flat pricing, finance-readable reports, and no percentage of savings.
Starter and Growth are self-serve subscriptions. Enterprise is contract-managed. Savings are labeled as estimates until verified and reports preserve the assumptions behind the numbers.
Procurement-ready boundaries
Pricing
Starter €199/month and Growth €499/month, excluding VAT
Plan limits are based on active cloud connections and provider-family scope.
Reports
PDF and CSV exports are available according to the plan table
Exports support review; they are not proof that a recommendation was applied.
Savings model
Estimated findings first, verified outcomes after customer review
Costframe does not take a savings commission.
Security and trust
Built around read-only access and explicit evidence limits.
Security reviewers should be able to find the access model, credential boundary, tenant-isolation assumptions, certification status, and legal pages without digging through a sales pitch.
Trust checklist
Least-privilege provider access only
Provider secrets decrypted only in the worker boundary
Evidence gaps stay visible on findings
Formal certifications are not claimed without an issued report
Buyer evaluation questions
What a real buying committee needs answered.
These are not testimonials. They are the recurring proof questions the public site must answer before a serious customer signs up, routes procurement, or connects a cloud provider.
Can I defend this number to finance?
Costframe labels savings as estimated, preserves pricing assumptions, and keeps non-financial findings out of savings totals.
Will this write to production?
No. Provider integrations are read-only. Recommendations and generated artifacts require customer review before action.
What happens when evidence is missing?
The finding stays visible with lower confidence, unavailable evidence, and a next step instead of pretending certainty.
Ready for a trustworthy first audit?
Start with the evidence, then decide what to change.
Sign up, choose a workspace, connect a supported provider with read-only access, and review the first findings with limitations visible.