FinOps
Know the bill before it arrives.
RunningLake prices the work in your cloud’s own dollars, added up by project, environment, submitter and engine. On top of that bill it projects the month, flags unusual spending and shows where money can be saved. No advice is applied until you plan it.
Cost attribution BUILDING Forecast and alerts PLANNED Cost advice PLANNED Maintenance line PLANNED
Four rules
A forecast is a range.
The cost page projects the month as a range from low to high, and says what it was projected from. It is a projection, not a promise.
An anomaly is an alert.
When spending looks unusual, RunningLake says so. The alert never stops, slows, suspends or moves your work.
Advice shows its dollars.
Each piece of advice names what it saw and the dollars at stake: snapshots piling up, a warm pool kept warm for nobody. You plan it as your own change, or leave it.
Maintenance is its own line.
Compacting files, expiring old snapshots and removing orphan files cost money in your cloud. That cost appears as its own line.
What we leave out
A credit unit, a figure we cannot trace to your cloud’s own bill, and an alert that acts on its own.