Platform Mesh

Concepts

Use this section when you want to understand why Platform Mesh exists, how its parts fit together, and which integration path applies to your work.

Recommended reading path

1. Why Platform Mesh? - the motivation, design principles, and service-management problem Platform Mesh addresses.
2. Architecture - the runtime layers and how user requests flow through the system.
3. Personas - the role guide for platform owners, service providers, and service consumers.
4. Account model - how organizations and accounts map to isolated control planes.
5. Control planes and workspaces - how Platform Mesh uses kcp workspaces without duplicating the full kcp docs.
6. API sharing - how provider APIs become available in consumer workspaces.
7. Identity and authorization - how identity, authorization data, and kcp enforcement relate.
8. Integration paths - when providers should use api-syncagent, multicluster-runtime, or related mechanisms.
9. Interaction patterns - common provider-consumer, provider-provider, and cross-consumption flows.

For factual lookup, use Reference. For guided local setup, start with Tutorials.

This site is open source. Improve this page.