All Posts

The multi-vendor collaboration and Kubernetes SIG home demonstrates real momentum for kro. Each cloud provider recognises the value of a portable, Kubernetes-native model for grouping and orchestrating resources, and the importance of reducing manual dependency management for platform teams.

The goal of this article is to explain what an internal developer platform and an internal developer portal are, how they differ, and where they overlap. We’ll also demonstrate how they can work together to support developer self-service, compliance, and streamlined workflows.

Platform engineering promises to accelerate delivery and reduce complexity, but if not approached deliberately, it can quickly become a cost sink. This article examines the hidden costs in platform engineering and explores cost-optimisation strategies to maintain a lean approach without compromising innovation.

When building a platform, engineering leaders often focus on technology choices without first building a shared vision with developers, specialist teams and other stakeholders. This results in low adoption or, in the worst case, wasted investment. This article will provide a practical leadership framework for securing developer support before a single platform component is built.

Platform engineers often lack visibility into their platform. With the new SKE GUI, that changes. Now available to Syntasso Kratix Enterprise users, it lets you view all Promises and resources, track their states, debug in real time, and explore how everything connects, all from a single interface.

As internal platforms evolve, composability has become a key way to build safe, scalable systems that still give developers freedom. This post explains how composable environments and business-aware PaaS help deliver the value of platform engineering, and how to use them without making common mistakes.

When we talk about internal developer platforms (IDPs), we’re often talking about abstracting complexity away from application teams, as explored in our post on platform democracy. But how far should that abstraction go? Poorly defined CI/CD abstractions can stall delivery and erode platform trust. This post examines how platform teams can avoid common pitfalls and design flexible, composable abstractions that empower developers while ensuring consistency and compliance.

As internal developer platforms evolve, one of the most pivotal decisions platform teams face is where to draw the line between platform and application ownership in continuous integration and continuous delivery (CI/CD). Abstraction is necessary for scale, but how much is too much? In this post, we’ll walk through four distinct CI/CD abstraction options and help you decide when each one makes sense.

At SOOCon23, Abby Bangser delivered an insightful talk titled "Building a Great Internal Platform Starts with the API." Read the summary here!

For many years, my peers and I have been discussing the concept of building “golden paths” for developers. These golden paths lead the...

The internal developer platform (IDP) market is expanding, and more tools are emerging as complete solutions to your platform needs. It’s tempting to believe that selecting one of these tools off the shelf will instantly make your team more productive. This article explains why IDPs must be composable, allowing teams to design systems where parts can be added, replaced, or scaled to suit the organisation’s needs without rebuilding the entire platform.

Software development should be seamless. The longer Developers have to wait, the less they create and this is why we need IDPs