FinOps roadmap
Understand, allocate and reduce cloud spend without slowing engineering down: pricing, tagging and bills, waste and rightsizing, commitments, workload-specific costs, unit economics and the culture that keeps it up.
8 topics · 34 nodes · 19 covered · 6 partly · 9 planned · updated 2026-10-17
Sign in with your Mycelium account to see which nodes you have finished.
- Covered
- Partly covered
- Planned
1. Core
FinOps foundations
What the practice is and why cost is an engineering concern.
3 / 4 covered
2. Core
Visibility and allocation
You cannot manage spend nobody can attribute.
2 / 5 covered
3. Core
Optimising usage
Stop paying for what you do not use or need.
4 / 4 covered
4. Core
Optimising rates
Pay less per unit for what you do use.
1 / 2 covered
5. Recommended
Costs of specific workloads
Each kind of workload has its own cost shape.
6 / 8 covered
6. Core
Unit economics and forecasting
Cost per customer, per request or per feature: spend in the language of the business.
1 / 3 covered
7. Recommended
Automation and guardrails
Make the cheap choice the default and catch surprises early.
1 / 4 covered
8. Core
Culture and governance
FinOps is a team sport: engineers, finance and product.
1 / 4 covered