DEV Community

Cover image for Uptime Isn’t Enough — My Shift from SRE to FinOps
Sai Krishna
Sai Krishna

Posted on

Uptime Isn’t Enough — My Shift from SRE to FinOps

Hey Dev.to 👋

I’ve spent the last several years working as a Staff Site Reliability Engineer, focused on keeping systems reliable, scalable, and — most importantly — up.

Like many SREs, my world revolved around:

  • SLAs, SLOs, and error budgets
  • Incident response and postmortems
  • Observability, automation, and resilience

And while uptime is critical… I started noticing something:

👉 We rarely talked about the cost of reliability.

The Shift

As systems scale, so do cloud bills.
And at some point, I realized:

Keeping systems up is only half the problem — keeping them cost-efficient matters just as much.

That’s what pulled me toward FinOps.

Not as a replacement for SRE — but as a natural extension of it.

Why FinOps?

Because:

  • Overprovisioning is easy under pressure
  • “Just scale it” often hides inefficiencies
  • Reliability decisions directly impact cost

And yet, cost is often treated as someone else’s problem.

It shouldn’t be.

Where I’m Headed

I’m currently exploring:

  • Cost-aware architecture patterns
  • Rightsizing and workload optimization
  • Bridging engineering and finance conversations
  • Building a culture where cost is a first-class metric ⸻

What to Expect Here

I’ll be sharing:

  • Practical FinOps learnings from an SRE perspective
  • Real-world trade-offs between reliability and cost
  • Tools, strategies, and mistakes along the way

Let’s Connect

If you’re working in:

  • SRE / Platform Engineering
  • Cloud Infrastructure
  • FinOps or cost optimization

…I’d love to learn from you.

Less downtime. Less waste. Better systems.

Let’s build that together 🚀

Top comments (0)