SYNTASSO BLOG

Available now for Syntasso Kratix Enterprise (SKE) users, the Promise Testing Framework enables you to focus on developing your Promise code, while we handle testing to ensure it works as expected. Check out the Promise Testing Framework docs!

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.

We’re heading to Atlanta for KubeCon + CloudNativeCon North America 2025, and this year’s lineup is one you won’t want to miss. From insightful talks on platform engineering patterns to deep dives into Kubernetes observability, the Syntasso team will share practical lessons, open-source insights, and a new O’Reilly report that’s shaping how enterprises think about internal developer platforms.

Despite $30–40 billion already invested in GenAI, MIT NANDA reports that 95% of initiatives fail to show measurable business impact. AI has arrived, but enterprise value hasn’t. That’s where the Model Context Protocol (MCP) fits. And it’s Syntasso Kratix Enterprise that turns MCP from an unrealised opportunity into a provided-by-default reality.

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.

Many organisations have successfully adopted GitOps for application delivery, but platform infrastructure provisioning often remains stubbornly manual, especially within enterprises. And by the end of this guide, you’ll see what this looks like in practice. You’ll request a Redis instance with a simple YAML manifest, Kratix will process the request, and Flux will automatically deploy the resources across your clusters.

Independent research reinforces this. MIT’s 2025 State of AI in Business report found that despite tens of billions in spend, only 5% of custom enterprise AI tools make it to production. Enterprises lead in pilot volume yet lag in scale. The findings point to approach, not model quality, as the real limiter. This article explores three platform-engineering principles that consistently turn AI from hype into working enterprise systems.

Workflow engines are having a moment in platform engineering. Tools like Temporal, Camunda, or n8n are being adopted to manage stateful automation, retries, and human approvals. They’re powerful, but they’re not platforms.  This post distils the workflow-engine thread from our webinar “Beyond the Platform Facade: Why Portals and Pipelines Aren’t Enough,” which Abby hosted and I presented.

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.