Isolation is the product

The control plane is multitenant. Every customer Mesh is not. A compromise here must not become a read of your conversations. It can still become a launch assertion if the issuer is taken. That risk is named on purpose.

• No Mesh database access. This service stores fleet metadata, not agents, prompts, or connector tokens.
• Separate cookie jars. Control plane and tenant instances will use different registrable domains. Host-only cookies. No WorkOS token in Mesh.
• Isolated issuer. Signing keys live in KMS and are callable only from the issuer runtime, not from this website.
• Staff is another realm. Operators do not become customer owners. Impersonation is not in scope.