Platform Engineering: 8 KPIs for 2025

“What is productivity in development? I mean, even with metrics like lead time, it might work against taking the time to do good things.”  Julien ‘Seraf’ Syx, CTO & Product Lead, Cycloid  Invisible processes sap energy and resources – not just from people, but also complex systems. Imagine the hidden waste that exists in cloud … Read more

When should you adopt Platform Engineering?

If you’ve not been living under a rock for the last year and a half, chances are you’ve heard of Platform Engineering. The latest industry trend promises to do everything DevOps tried to do and failed, yet again: lighten your devs’ workload, improve DevX, skyrocket operational efficiency, and turn your projects into rivers of gold.

In truth, Platform Engineering continues the process DevOps started. With PE, leaders have an actionable plan to build toolchains and workflows that empower developers of any skill level with self-service capabilities. It’s an all-round solution that not only improves devs’ autonomy and collaboration, but also enhances resource management, and provides ecosystem and plug-in integration.

You see why it’s an extremely attractive proposition for IT departments – and a very daunting undertaking. After all, it takes nearly 3 years and 20 dedicated specialists to start seeing tangible results. And yet, Gartner predicts that by 2026, 80% of IT departments will adopt internal platform engineering teams. 

Obviously, you don’t want to be left behind, but does this mean you should join the race now? When should you adopt Platform Engineering?

Let’s look at the factors that mean your organization needs to consider platform engineering seriously.

Read more

Quand devriez-vous adopter l’ingénierie de plateforme ?

Si vous ne vivez pas sous un rocher depuis un an et demi, il y a de fortes chances que vous ayez entendu parler de l’ingénierie de plateforme. La dernière tendance du secteur promet de faire tout ce que DevOps a essayé de faire et a échoué, une fois de plus : alléger la charge de travail de vos développeurs, améliorer DevX, faire monter en flèche l’efficacité opérationnelle et transformer vos projets en rivières d’or.

En réalité, l’ingénierie de plateforme poursuit le processus entamé par DevOps. Avec l’ingénierie de plateforme, les dirigeants disposent d’un plan d’action pour construire des chaînes d’outils et des flux de travail qui permettent aux développeurs de tout niveau de compétence de disposer de capacités en libre-service. Il s’agit d’une solution complète qui améliore non seulement l’autonomie et la collaboration des développeurs, mais aussi la gestion des ressources et l’intégration de l’écosystème et des modules d’extension.

Vous comprenez pourquoi il s’agit d’une proposition extrêmement attrayante pour les services informatiques – et d’une entreprise très intimidante. Après tout, il faut près de 3 ans et 20 spécialistes dévoués pour commencer à obtenir des résultats tangibles. Et pourtant, Gartner prévoit que d’ici 2026, 80 % des services informatiques adopteront des équipes internes d’ingénierie des plateformes.

Il est évident que vous ne voulez pas être à la traîne, mais cela signifie-t-il que vous devez vous lancer dans la course dès maintenant ? Quand devriez-vous adopter l’ingénierie de plateforme ?

Examinons les facteurs qui font que votre organisation doit envisager sérieusement l’ingénierie de plateforme.

Read more

Migrating infra to IaC is a business imperative: Infra Import Use Case

Imagine this: you’re looking to scale your infrastructure to match your rapid business growth. Infrastructure-as-code is an excellent way of modernizing infrastructure. You know that the longer you wait to make the move to IaC, the deeper your business will sink into the quicksand of human error and, eventually, slower deployment. However, industrializing your manually-deployed infra is a daunting and resource-extensive task.

Read more

Developer self-service: your key to adopting Platform Engineering!

Wider teams are resisting adopting an internal developer platform, and platform engineers are pulling their hair trying to understand why, according to the State of DevOps 2023 Report. Is it too complex? Does it not do the job? Is the UI not sleek enough? Possibly all of the above, but the real culprit is under-education and under-communication about the possibilities of an internal developer platform to your wider team.

Developer self-service is an integral part of platform engineering, and one that has the most number of users across an organization. If you can get your team to adopt developer self-service, your platform engineering strategy is in the bag. But for this to happen, it should satisfy the needs of all – both end-users (devs, solution architects, IT teams) and Ops.

So, building developer self-service, which is more than simply designing a fancy UI (though it is very important and overlooked by many!) – it’s about building a functional tool with a user in mind. It’s not just making it user-friendly – make it user-oriented!

Treating the platform as a product that answers your customers’ (wider teams’) needs is what will help you build a platform that’s going to be easy to adopt.

How can you make developer self-service more user-friendly?

Address the user’s needs

Just like any relationship, it’s all about communication. In an ideal world, end-users communicate their needs, and the platform team responds to them as best they can. The platform team’s role is to put their end-users in the best position to handle tools, processes, and infrastructure, but how exactly that’s done depends on individual members.

Treat your colleagues as if they were your customers, and the platform as a product, then the roadmap becomes so much simpler and clearer. 

If your team can’t articulate their wants and needs clearly, take the next best thing – an out-of-the-box industry standard solution. We’ve written loads on the benefits of buying vs building, but the gist is this – why spend hours of your precious time perfecting what’s already been perfected by experts? There’s nothing your team is going to gain from reinventing the wheel, so you’ll be safer with market-tested solutions.

StackformsCycloid’s own self-service portal StackForms prioritizes end-user experience to make configuring new environments as seamless and autonomous as possible. We aim for flexibility, simplicity, and control when it comes to self-service, concealing complex tech behind a user-friendly interface (so hopefully we know what we’re talking about!)

Autonomy and security

Read more