If you’ve been around Cycloid socials, you’ll know that we’ve had a quiet change of name – from Cycloid Hybrid Cloud DevOps Platform to Cycloid Platform Engineering. Besides the fact that the new title is less of a mouthful, it’s also a better reflection of what we do here at Cycloid. We are not having a sudden change of heart and reimagining everything the Cycloid platform does – quite the opposite. The core principles of the emerging trend of platform engineering are aligned with the vision Cycloid has been bringing into the world of DevOps and hybrid cloud since its conception – so the soft rebrand was in order.
In a recent article, Gartner described platform engineering as a strategy aimed at “improving developer experience and productivity by providing self-service capabilities with automated infrastructure operations.” This term is trending because of its promise to accelerate product teams’ delivery and increase business value.
Cycloid’s core focus is enhancing developer experience and improving operational efficiency. We’ve seen the need for DevOps and developed a concrete and practical way of achieving it – by enabling developer self-service and opening up DevOps and hybrid cloud adoption to everyone. Platform engineering is simply another word for something we’ve been doing for a long time.
But with this shift towards platform engineering as Gartner predicts, new questions come up – does this mean the end of DevOps? How does platform engineering align with hybrid cloud management? Let’s take some of your most burning questions.
What is Platform Engineering?
