Connect read-only
Add an AWS account through a cross-account IAM role (read-only). GCP and OCI use the same pattern. We never gain write access to your accounts.
read-only IAM · STS:AssumeRole
A continuous, immutable log of every realised cost reduction — with the recommendation that triggered it, who applied it, and the cloud bill line that proves it.
By the numbers
totalCost + potentialSavings per account
0
daily cost snapshot
downsize · terminate · RI switch · …
0
recommendation types tracked
SHA-256, append-only
0
integrity hash chain
write access denied by design
0
ways to edit a past entry
How it works
Add an AWS account through a cross-account IAM role (read-only). GCP and OCI use the same pattern. We never gain write access to your accounts.
read-only IAM · STS:AssumeRole
When you act on a recommendation in Lumicost — apply, dismiss, send to Jira — we capture the actor, the resource id, and a JSON snapshot of the state before and after.
actor · resourceId · before/after
Each day a CostHistory row records totalCost and potentialSavings per account. The audit log lets you trace each event back to the action that caused it.
daily · per-account
What's inside
Most FinOps tools tell you what you could save. Lumicost tells you what you actually saved. Every accepted recommendation is reconciled against the next billing cycle, so the ROI you report is the ROI that hit the bill.
Every entry in the history is append-only and cryptographically chained — useful for SOC 2 control CC7.2 (change management) and ISO 27001 A.12.1.2.
Saving credit follows the team that owned the resource at the moment of the action — not the team that owns it today. Reorgs no longer rewrite financial history.
Capabilities
Before vs after Lumicost
Without Lumicost
With Lumicost
Where teams use it
Export a PDF showing $483K saved across 6 quarters, broken down by team and cloud — without spreadsheet archaeology.
Surface the 5 engineers who unlocked the most realised savings this half — with proof, not anecdotes.
Compare predicted vs. realised savings per recommendation type — so the next forecast is calibrated to your stack, not industry benchmarks.
From the field
“We chose append-only with a SHA-256 chain because savings without a paper trail are just a story. The audit log is the receipt.”
Plays nice with your stack
FAQ
We compare the cloud bill line for the affected resource in the 30 days before the change with the 30 days after, normalised by usage to remove organic growth or shrinkage.
No. Entries are append-only. If a recommendation is later reversed, that produces a new entry — the original record is preserved.
Keep exploring
Connect read-only credentials. First insights in 24 hours. No credit card.
90 seconds · read-only credentials · no credit card