I knew PlatformCon 2025’s first New York City Live Day would bring the usual debates about whether platform engineering is the new DevOps. What I didn’t expect was a guy roaming the lobby in a white sash screaming, in block-letter embroidery, “Platform Engineering is Dead.” If the goal was to provoke, mission accomplished — but the irony was thick. You could barely move in the sold-out Convene space, shoulder-to-shoulder with more than 400 practitioners eager to compare Terraform modules, golden paths and OpenTelemetry pipelines.
PlatformCon’s final registration numbers — 40,000+ virtual sign-ups and a projected 100,000 session views — tell a different story: Platform engineering is very much alive. And the biggest takeaway for me, a DevOps believer, is that the rivalry between DevOps and platform engineering has quietly faded. Instead, we’re watching an overdue reconciliation that promises to make every release pipeline faster, safer and a lot more fun.
From Turf War to Tag Team
Back in 2022, you could scarcely open LinkedIn without a hot take declaring “Platform Engineering will replace DevOps.” The framing never made sense —DevOps is a culture and set of practices; platform engineering is an organizational response to scale. That distinction finally felt settled in NYC. Speaker after speaker pointed out that a healthy Internal Developer Platform (IDP) is a force multiplier for DevOps teams, not a replacement.
Kelsey Hightower’s morning keynote set the tone. “Platforms aren’t magic APIs,” he reminded us. “They’re agreements that make engineers faster at delivering business value.” Our job in DevOps has always been to accelerate that value stream. The platform engineer just gives us better raw material to work with — golden-path templates, standardized environments and opinionated guardrails. Less yak-shaving, more shipping.
AI: The Great Convergence Engine
If DevOps and platform engineering needed a common enemy — or ally — to bond over, AI provided it. A panel featuring Nvidia, Google, Rootly and Thoughtworks explained how large language models are automating “the last mile” of toil, from incident response bots that reason over Grafana dashboards to code-gen pipelines that spit out compliant Terraform.
Workshops went even deeper. Gitpod walked attendees through an “AI Technology Radar” exercise to decide which GenAI tools to adopt, trial, assess or hold. And then there was Sedai’s bravely named “Self-Driving Cloud” lab: Think agentic AI closing the feedback loop between cost, performance and deployment decisions with almost no human in the path.
For DevOps engineers, this means two things:
- The cognitive load shifts. Troubleshooting a flaky deployment may start with prompting an LLM that already read all your runbooks.
- The platform boundary blurs. If AI can orchestrate infra and app layers together, DevOps and platform teams must design those control planes side by side or risk “dual brains” fighting for supremacy.
Observability: The New Gravity Well
Every conversation about platform maturity eventually landed on observability. Mezmo’s hands-on OTel pipeline workshop was standing-room only; folks were literally sitting on the hallway carpet to follow along. The logic is straightforward: You can’t automate what you can’t see. For DevOps practitioners, high-fidelity telemetry is now table stakes — whether you’re feeding an agentic AI, debugging an ephemeral sandbox, or proving compliance to auditors. Expect platform blueprints to ship with observability baked in, not bolted on.
Sponsors Tell the Story
Look at the badges behind every coffee urn and you’ll spot familiar DevOps and DevSecOps logos — GitHub Actions, Mezmo, Teleport, Cortex, Sedai, Tailscale. Many of these vendors cut their teeth in CI/CD, IaC, or shift-left security long before “platform engineering” was a LinkedIn hashtag. Their presence reinforces a simple point: The DevOps ecosystem isn’t being cannibalized; it’s expanding into platform architecture, policy-as-code and developer portals.
Three Big DevOps Takeaways
- Platform = Product = Velocity
Treating the platform like a product — complete with backlogs, SLAs and NPS — gives DevOps teams the reliable substrate they’ve always begged for. Less firefighting frees us to optimize flow, not fix YAML. - Agentic AI Will Test Your Guardrails
Auto-remediating bots and self-driving clouds are amazing until they deploy a breaking change at 2 a.m. DevOps pros must harden policy engines, progressive delivery gates and observability loops to keep the machines honest. - Collaboration Over Handoffs
The healthiest orgs I interviewed position DevOps inside the platform team or vice versa. That unity prevents the “throw it over the wall to the platform squad” anti-pattern and keeps integration and deployment from becoming the next bottleneck.
About That “Platform Engineering is Dead” Sash
So why the funeral garb? My guess: A tongue-in-cheek jab at hype cycles. Just as “DevOps is dead” clickbait pushed us to sharpen our message, the sash was a reminder that real value — not buzzwords — keeps a movement alive. Judging by the hallway traffic and workshop queues, platform engineering is passing that test.
Where We Go Next
I left Midtown convinced that we’re entering a post-label era, where the strict DevOps vs. platform binary distinction dissolves. High-scale organizations already blur the lines: Platform engineers own golden paths; DevOps engineers extend them; both instrument the heck out of everything, all while teaching an LLM to babysit the cluster at 3 a.m.
Expect to see:
- Shared scorecards that measure both platform adoption and deployment frequency.
- Joint SLO ownership where DevOps and platform teams co-sign error budgets.
- AI-native incident command rooms where bots write the first draft of every post-mortem.
Final Word
DevOps isn’t dead, and neither is platform engineering. The sash guy had it backwards: The rivalry is what’s dead. In its place, we have a pragmatic partnership aimed at giving developers the safest, fastest runway imaginable. That’s a win for everyone — from the two-pizza team pushing to prod on Friday afternoon to the CISO sleeping better at night.
If PlatformCon NYC proved anything, it’s that the DevOps ethos of collaboration, automation and continuous improvement now has a bigger, better stage. And I, for one, can’t wait to see what happens when the lights come up and the AI co-pilots take the wheel.