All Posts

Terms like “Platform as a Product” and “X-as-a-service” are everywhere, yet many companies still centralise all platform responsibilities in a single team. This results in cognitive overload, bottlenecks, and missed opportunities to tap into institutional knowledge. This article reframes the discussion from “headcount” to “collaboration.”

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!

A good internal platform is one that delivers speed, safety, efficiency, and scalability to meet the evolving needs of software teams.

We built Syntasso Kratix Enterprise (SKE) to support the orchestration of any platform resource—Kubernetes-native or not—with automation, governance, and scale in mind.

Check out the PlatEngDay London talks that included the Syntasso team. We cover platform as a product, banking platforms, product thinking, and platform adoption

Building on ideas first introduced in her blog post, Paula Kennedy, COO and co-founder of Syntasso shared real examples, answered questions, and gave tips for teams just getting started.

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

The most successful platform businesses rely on the network effect. The more valuable stuff your platform offers, the more users will be attracted to join. The more users you have consuming value, the more producers will want to add valuable stuff to your platform and so on. Cat Morris, Staff Product Manager at Syntasso talks about this in her latest blog post

In my recent talk at KubeCon EU, I aimed to share insights into the connection between software architecture and platform architecture

Platform Democracy is a model where developers, security teams, SREs, and even external service providers collaborate seamlessly.

Recognising these antipatterns is essential to building platforms that empower devs, ops, and, critically, everyone else in your org.

Internal platforms often manage highly sensitive data, making them prime targets for breaches, insider threats, and cyberattacks.

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

In my recent talk at QCon San Francisco, I had the opportunity to share my thoughts on the evolution of platform engineering.

A summary of my talk, "Engineering Resilience into the Foundations: Key Strategies for Building Robust Internal Development Platforms."

I am excited to announce that OpenCredo has partnered with Syntasso to accelerate platform engineering initiatives.

Earlier in the month, I had the privilege of presenting two talks about platform orchestration at the JAX London event.

We often celebrate the individual platform engineering or DevOps hero or heroine who (purportedly) creates something ingenious alone, but...