SYNTASSO BLOG

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 actu

How The Access Group scaled AI-driven development with platform engineering, using Kratix to add structure, ensure reliability, and support 2,000+ applications.

At KubeCon, Nitish Malhotra from Veeam Software and Cat Morris from Syntasso explored how to avoid the day 2 platform hangover

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 Platfor

Pulumi components enable reuse, but they don’t provide a safe, self-service platform for developers. Exposing raw infrastructure abstractions creates friction. What’s missing is a platform API that turns components into well-defined capabilities with built-in workflows, governance, and consistency.

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.

In a recent Syntasso webinar, Rachael Wonnacott, Head of Cloud Engineering at Fidelity International, explored a simple but powerful idea: your platform is not an island. Platform teams do not operate in a vacuum. They sit inside a wider organisational ecosystem shaped by people, team structures, legacy technology, established processes, and differing levels of engineering maturity.

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.

We’ve just arrived home after an exciting few days in Amsterdam for KubeCon EU 2026. Here's a summary of our key learnings from PlatEngDay and the main event.

We’re excited to share that Syntasso has been recognised in the Cord Spring 2026 Tech Hiring Rankings, including: #1 Gender Diversity Sourcing (Small Companies) and #3 Most Popular Small Company for Engineers