FinOps

What Is FinOps?

FinOps – short for Cloud Financial Operations – is an operational framework and cultural practice that brings engineering, finance, and business teams together to create cloud cost transparency and maximise business value per euro spent. FinOps does not replace the cloud; it makes cloud usage economically sustainable.

For mid-market companies, FinOps is particularly relevant: monthly cloud bills of €10,000 to €100,000 are common, and without systematic cost management, 20–40% of savings potential remains untapped. FinOps ensures every department understands what it spends in the cloud and why.

The Three Phases of the FinOps Framework

The FinOps Foundation's framework is based on an iterative cycle of three phases:

Inform – Create Transparency

The Inform phase focuses on complete cost transparency. You implement tagging strategies, set up cost allocation reports, and make visible which team, project, and environment incurs which costs. Tools like AWS Cost Explorer, CloudHealth, or Kubecost help prepare the data.

Practical example: A logistics company tags all AWS resources by department (logistics, e-commerce, administration) and environment (dev, staging, prod). Within two weeks, it becomes apparent that the development environment accounts for 35% of total costs – even though it is only needed during business hours.

Optimize – Reduce Costs

In the Optimize phase, you use the transparency gained to implement concrete savings measures:

• Right-Sizing: Adjust oversized instances to actual demand.
• Reserved Instances & Savings Plans: Secure discounts of 30–72% for predictable workloads.
• Spot Instances: Save up to 90% for fault-tolerant workloads like batch jobs.
• Idle Resources: Identify and delete unused resources (EBS volumes, old snapshots, unattached IPs).
• Scheduling: Automatically shut down dev and test environments at night and on weekends.

Operate – Sustain and Govern

In the Operate phase, you embed FinOps as an ongoing process in your organisation. This includes regular cost reviews, budget alerts, anomaly detection, and assigning cost ownership to respective teams. FinOps is not a one-time project but a continuous improvement process.

FinOps Principles

The FinOps Foundation has defined six core principles:

• Teams need to collaborate: Engineering, finance, and business work together on cost optimisation.
• Everyone takes ownership of their cloud usage: Decentralised responsibility rather than central control.
• A centralised team drives FinOps: A FinOps team coordinates best practices and tools.
• Reports must be timely and accessible: Real-time data instead of monthly invoices.
• Decisions are driven by business value: Not the cheapest, but the most value-creating solution wins.
• Take advantage of the variable cost model of cloud: The cloud is not a data centre with fixed costs – leverage its elasticity.

FinOps Tools Overview

A variety of tools support FinOps processes:

• Cloud-native: AWS Cost Explorer, AWS Budgets, Azure Cost Management, GCP Billing.
• Third-Party: CloudHealth (VMware), Cloudability (Apptio), Spot.io, Kubecost (for Kubernetes).
• Open-Source: OpenCost, InfraCost (for Terraform cost forecasts).

Which Tools Suit the Mittelstand?

For getting started, the cloud provider's native tools (e.g., AWS Cost Explorer + Budgets) are sufficient. Once your monthly cloud bill exceeds €20,000, a specialised tool like CloudHealth or Kubecost is worthwhile for deeper insights and automated recommendations.