Listen

All Episodes

Audio playback

Platform Ops and the Future of DevOps

This episode unpacks the emergence of Platform Ops as a pivotal practice in modern DevOps, with insights into its principles, tools like Crossplane and Backstage, and the rise of platform engineering roles. We explore whether Platform Ops is a true evolution or a rebranding, while highlighting how AI and automation are reshaping workflows and infrastructure management. Tune in for strategies to foster organizational collaboration and build more efficient developer platforms.

This show was created with Jellypod, the AI Podcast Studio. Create your own podcast with Jellypod today.

Is this your podcast and want to remove this banner? Click here.


Chapter 1

What is Platform Ops

Naomi

Okay, so let's talk about Platform Ops! You’ve probably heard this term tossed around, but maybe you’re like, “Wait, what even is this?”

ChangoMuertos

Right. And at its core, Platform Ops is essentially an evolution of traditional DevOps. But instead of just focusing on bridging development and operations, it digs into managing and optimizing those systems with, you know, a more operational focus.

Naomi

Exactly! It’s like taking DevOps and levelling it up to handle things like multi-cloud... whatever that means...

ChangoMuertos

Multi-cloud basically means running applications or services across multiple cloud providers, instead of locking everything into one ecosystem. It’s complex, but a strong Platform Ops approach simplifies it for developers.

Naomi

And they’re all about making life easier for developers, right? Like with self-service tools and stuff!

ChangoMuertos

Right. Self-service is a huge focus. The idea is to give developers the ability to spin up the resources they need—think environments, infrastructure—without waiting on operations teams. This autonomy is—

Naomi

Total game-changer! I mean, who likes waiting?

ChangoMuertos

Certainly not developers. But it’s not just about speed. It’s also about maintaining control. With something like a centralized control plane, Platform Ops ensures that while developers have autonomy, there’s still governance, security, and reliability baked in.

Naomi

Ooh, governance! Fancy word. But what I get is—Platform Ops strikes this balance between structure and freedom, right?

ChangoMuertos

Exactly. And that's where the "platform as a product" mindset comes in. Instead of treating it like "just a tool," the platform is continuously improved, like software, based on feedback from the developers using it.

Naomi

Oh, so it’s like, “Hey devs, what do you need? Let’s make this platform better for YOU!”

ChangoMuertos

Precisely. But don’t forget automation—another cornerstone here. Automation isn’t just about expedience; it’s critical for creating scalable, repeatable processes. It’s what truly helps platforms handle those growing multi-cloud architectures and microservices.

Naomi

Microservices! Can we just pause and appreciate how everything’s becoming, like, micro this and micro that? But yeah, go on—automating all these operations must save teams loads of time.

ChangoMuertos

It does. And pair that with robust observability practices—you know, monitoring, analyzing logs, performance metrics—it ensures the system remains healthy, reliable, and cost-effective.

Naomi

Sounds kinda dreamy for a tech setup, honestly. So, the point of Platform Ops is...

ChangoMuertos

…to solve some of the pain points traditional DevOps teams face. By dedicating resources to manage and optimize infrastructure, it makes the platform efficient enough for developers to stay focused on their real work—building features and applications.

Naomi

Love that for them. And it sounds like tools like Crossplane or Backstage are part of this whole setup?

ChangoMuertos

Yes. Crossplane, Backstage, and others play significant roles in implementing those self-service principles. They’re essential for creating that seamless developer experience.

Chapter 2

The Rise of Platform Engineering

Naomi

So we’ve got Platform Ops making life easier for developers, but here’s my question—how does that overlap, or differ, from this whole Platform Engineering thing that everyone’s suddenly hyped about?

ChangoMuertos

It’s not sudden. It’s the logical next step. Platform engineering focuses on building Internal Developer Platforms—or IDPs—to support developers. Think of it as creating a product specifically for your internal teams to make their lives easier.

Naomi

Ooh, a product just for developers? Fancy! So, what does an IDP even do? Like, roll out a red carpet for devs?

ChangoMuertos

In a way, yes. An IDP gives developers self-service tools that reduce cognitive load. Instead of juggling different systems or waiting on IT, developers can self-provision resources, set up environments, and get work done faster.

Naomi

Okay, love that! No more “Hey, can you spin up this thing for me?” emails clogging inboxes. But what makes this different from just, I don’t know, good DevOps tools?

ChangoMuertos

The difference lies in how it’s packaged and scaled. IDPs operate as a cohesive platform designed for usability. They centralize everything—tools, governance, even security policies—so that developers have a seamless experience.

Naomi

Oh, so it’s all in one place. Like the ultimate one-stop shop for coding ninjas. Got it!

ChangoMuertos

Exactly. And technologies like Argo and Qovery are leading this charge. They enable automation, resource provisioning, and importantly, maintain compliance and security. It’s these tools that bring platform engineering to life.

Naomi

Argo, Qovery… cool names, but quick question: is this just for, like, massive companies? Or can, you know, smaller teams use this?

ChangoMuertos

Good question. While larger organizations benefit the most from the scalability, smaller teams can adopt these practices too. The beauty of platform engineering is its modularity—it grows with you. Even a minimal platform, or what we call a Thinnest Viable Platform, can deliver value.

Naomi

Thinnest Viable Platform? Love the sound of that. Let’s keep it lean, right?

ChangoMuertos

Exactly. Start small, focus on key priorities for developers, and expand based on need. What it really comes down to is operational excellence. Ensuring resilience, scalability, and, of course, developer happiness.

Naomi

Cloud-native feels, like, tailor-made for this, right? Devs can scale, tweak, and go wild without worrying about infrastructure drama?

ChangoMuertos

Precisely. Cloud-native solutions are accelerating this shift. They dissolve the old fears people had about adopting new tech. Organizations are finally investing in mature platform engineering practices, and it’s paying off.

Chapter 3

Platform Ops: Evolution or Rebranding?

Naomi

Right, so with all this cloud-native momentum and keeping it lean, here’s my big question: is Platform Ops just the next level of DevOps, or is there actually something deeper going on?

ChangoMuertos

It's a fair question. Honestly, some might see it as just a shiny new label. But dig deeper, and you’ll find there are key differences. Platform Ops builds on DevOps but adds scalability, governance, and structured services that DevOps teams often struggle to achieve on their own.

Naomi

Oh, so it’s less “reinvention” and more an evolution. But how do teams balance the whole “let devs do what they want” vibe with keeping, uh, structure and control?

ChangoMuertos

It’s a delicate dance. The key lies in governance frameworks. By standardizing tools and practices—things like golden paths and approved resources—you give developers the freedom to innovate while ensuring security and compliance are still top-notch.

Naomi

Golden paths? Cute name, but basically, you’re saying, “Here’s the best way to do stuff—have fun!”

ChangoMuertos

Pretty much. It’s all about reducing friction. And that’s where AI-driven automation comes into play. Imagine being able to provision infrastructure or optimize workflows without lifting a finger. AI simplifies these tasks and pushes Platform Ops ahead of traditional DevOps.

Naomi

Wait, wait—AI can, like, write code and set up infrastructure? Are we talking robots replacing developers here?

ChangoMuertos

Not quite. It’s more about augmentation. AI speeds up mundane tasks, like provisioning and monitoring, freeing up developers to focus on creative and high-value work. It’s an enabler, not a replacement.

Naomi

Okay, love that. So, teams and departments need to be on the same page for this to work, right? No rogue teams going “We don’t need no Platform Ops!”?

ChangoMuertos

Collaboration is crucial. Successful Platform Ops depends on clear communication and shared goals across departments. It’s about fostering alignment and ensuring everyone—from devs to security teams—feels part of the process.

Naomi

Got it. Teamwork makes the dream work, as they say! So, to wrap this up, what’s your take? Evolution or rebranding?

ChangoMuertos

It’s evolution. Sure, the foundational principles resemble DevOps. But the structured, scalable, and AI-enhanced practices of Platform Ops represent a leap forward, not just a rebranding.

Naomi

Alright, sold! Platform Ops: the glow-up DevOps always needed. And hey, that’s all for today, folks. Great chat, Chango!

ChangoMuertos

As always, Naomi. Until next time, keep your platforms resilient and your devs happy!