At AWS Summit London, one theme came up again and again across organisations of every size and sector: platform teams are getting much clearer about what they should build, and what they shouldn’t. From highly regulated financial institutions to global travel platforms, the most effective teams aren’t trying to recreate cloud services. They are deliberately offloading undifferentiated work to providers like AWS, and focusing their effort on the parts of the platform that actually create...

Organisations demand capabilities that are operable and scalable across a range of disparate platform technologies. The architectural patterns that achieve this are not unique to a single organisation, Infrastructure as Code (IaC) tool, or user interface choice. What platform teams need is a clearer model for what a scalable capability looks like so that every new capability does not become another special case to integrate, govern, and operate. That is the purpose of Platform Capability...

The relatively recent move towards more centralised platforms stems from a desire to exert greater control following an era of sprawl introduced by DevOps. Yet on reflection, using the word “control” is likely not only unnecessary but also wrong. In the end, control is one solution that can be applied towards the cost and risk reduction outcome organisations are most concerned with, which can be better summarised as coherence.

Despite all of the investment in portals, templates, and Kubernetes operators, organisations are realising that investing in tech implementation feels productive, while actually, they are just stuck on a treadmill of refactoring automation.

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.

Giving developers autonomy to provision infrastructure is now a table-stakes requirement for modern internal developer platforms (IDPs). What happens when a critical vulnerability is found in a shared service such as a database? This is where Kratix steps in. It enables you to build internal platforms where developers can self-serve, while providing platform engineers with powerful tools to manage services across the fleet.

Many organisations have invested heavily in Terraform, and rightly so. It’s a mature Infrastructure as Code (IaC) tool that automates infrastructure and streamlines workflows. However, when building an internal developer platform (IDP), IaC alone isn’t enough. To scale across teams and business needs, all while supporting seamless fleet management, you also need developer-friendly platform APIs and abstractions. That is where Kratix comes in.

Most internal platforms don’t fail on day one: they fail on day 2, 200, or 2000. What starts as a solid solution to today’s needs often turns into tomorrow’s bottleneck: brittle delivery processes, endless ticket queues, and systems so complex they collapse under their own weight. At Syntasso, we built Kratix to flip this pattern.

Helm is one of the most widely used tools in the Kubernetes ecosystem. But Helm has its limits, especially when it comes to building internal platforms that scale across business requirements, teams, and technologies. In this blog, I’ll walk through how Kratix lets you take your existing Helm charts and turn them into powerful platform APIs with a single kratix-cli command.

When the CNCF Platforms Working Group published the Platform Engineering Maturity Model in late 2023, it felt like an important milestone. Now, I’m excited to share that the next stage in this work is underway. After almost a year of deliberation, testing, and editing, it’s now available in prototype form.

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.

Explore what platform engineering can learn from over-the-air car updates; the secret is fleet management!

Learn how to build scalable internal developer platforms (IDPs) with Syntasso Kratix Enterprise (SKE).

Platform engineering focuses on creating internal platforms that align with your organisation's needs.

Kratix is excited to announce the latest addition to our marketplace – Unleash, a tool for feature flag management. With the addition of...

The Syntasso team has a long history of open source and community engagement as well as being leaders within the platform engineering...

In software there always seems to be more to do than time to do it. This is particularly true when it comes to often understaffed...

In the last couple of decades software delivery has gone through significant changes. Historically, software was subdivided into focused...

Over the last 6 years I have had the pleasure of working on a few amazing platform teams. In each case we had an outsized impact on the...

User-friendly platforms can be hard to design and even harder to implement. Platform engineers need to wrangle a large number of tools...