How Much Platform Is Enough Platform?

KubeCon + CloudNativeCon Europe 2026

Session Date: March 25, 2026 — London

What Makes a Platform?

"Software to make other software go — it's an enabler.
Lowering the cognitive load.
As a product, it tends to have a brand and customers."

The Framework

Three questions to answer:

  1. Cognitive load — Is it low enough for developers?
  2. Change can flow — Are developers unblocked?
  3. Safety and ownership — Can changes be made safely, with ownership?

Sustainable Pace

  • Goal: once a week you get software out the door
  • Trying harder is not the answer — having the right platform is
  • Need an internal high-level champion with authority to say "no" early
  • Ideally, developers never leave the IDE

12-Factor App as Quality Standard

  • The 12-factor app philosophy identifies expected software quality
  • Build a platform backend that supports these principles
  • Adhering provides benefits for both platform and consumer
  • Creates a shared language between platform team and app teams

Automation and Self-Service

  • Minimum viable platform — do what is needed but no more
  • Everything costs upkeep
  • Must be delivered in a way teams can actually accept
  • Don't build features nobody asked for

Backstage: Too Much Platform?

  • Doesn't work as easily as expected
  • "Skill issue" — too big for most organizations
  • Backstage is an IDP — not every org is ready for an IDP
  • If you just need scaffolding, you don't need Backstage

Conclusion: Backstage might be too much platform.

Key Takeaways

  1. Platforms enable, they don't impose
  2. Right-size for organizational maturity — not every team needs enterprise tooling
  3. Weekly releases are the sustainable pace target
  4. Champions with authority prevent scope creep
  5. Minimum viable platform — everything costs upkeep, so do less but do it well

Questions?

KubeCon EU 2026 — London