Skip to content
BENIBIX Learn

Platform Team

Also known as Platform Teams, Internal Platform Team

A team that builds shared tools other teams use on their own, like a service.

Think of it like

It is like the water pipes in a town. Every house uses them, and no one has to build their own.

Example

A shop in Paris has a platform team of six. It gives every product team one command to start a new service, with tests and logs set up.

Why it matters

Without it, every team builds the same base again. With a good one, teams spend their time on their own users.

Definition

A platform team builds shared tools that other teams use as a service. It is one of the four team types in Team Topologies. The tools might be a way to ship code, a place to store data or a login system. The other teams use them on their own, without filing a ticket. The platform team treats them like a product, with users to please. Its job is to take work off the stream-aligned teams.
The platform team sits under the others. Its arrow points up because teams use what it offers as a service.

Common mistake

Building tools nobody asked for, then forcing teams to use them. A platform must earn its users, like any product.

Key takeaways

  1. 1
    Self-service. Teams use it without asking.
  2. 2
    Run as a product. It is built for its users.
  3. 3
    Thin as possible. Keep the platform as small as it can be.

Compare