saas-platform-architect

What problem does it solve?

This Skill helps you design the actual platform shape for a multi-tenant SaaS system so you can decide what is shared, what is isolated, and how tenant context flows through the product without guessing.

Core Features & Use Cases

• Per-component tenancy decisions: Chooses pooled, siloed, or mixed deployment for each component with a named isolation mechanism or provisioning story.
• Control plane vs data plane split: Separates tenant management, identity, billing, support, feature flags, and audit from tenant-facing workloads and data.
• Incremental migration planning: Converts a single-tenant app to multi-tenant in shippable steps with verification and rollback for each step.
• Use case: A team wants to move an existing app from one customer to many enterprise tenants while preserving security, compliance, and operational reversibility.

Quick Start

Ask for a multi-tenant SaaS architecture for your current product, including component-level pooling or isolation decisions, control-plane/data-plane boundaries, and a rollout plan with rollback.