A platform owner operates Platform Mesh as the shared service-management layer for an organization. They make sure providers can publish services, consumers can safely use them, and the platform has a consistent account, identity, and authorization model.
Create a secure and operable mesh where service capabilities can be offered and consumed without every team inventing its own integration pattern.
The platform owner owns the mesh itself — the control plane substrate, the account hierarchy, identity and authorization wiring, and the marketplace surface. They do not own provider implementations or consumer workloads. Their relationship to providers is onboarding and lifecycle; their relationship to consumers is enabling discovery, binding, and policy.
Start with Why Platform Mesh? for motivation, then read Architecture for component layout, Account model for the hierarchy, and Control planes and workspaces for how the kcp substrate is used. Use Identity and authorization for the runtime relationship between Keycloak, OpenFGA, and the kcp authorizer. Use Components for factual component lookup.