saas-architecture

What problem does it solve?

Early SaaS architecture decisions, especially tenancy model selection, are extremely costly to change later, with cascading impacts on data models, billing systems, compliance posture, and operational complexity. This Skill eliminates the risk of costly architectural rework by providing proven patterns for end-to-end SaaS platform design.

Core Features & Use Cases

• Multi-Tenancy Model Selection: Guidance on choosing between silo, bridge, pool, and hybrid tiered tenancy models based on isolation requirements, customer segment, and budget.
• Tenant Isolation Implementation: Production-ready patterns for PostgreSQL RLS, schema-per-tenant, and Kubernetes namespace-per-tenant isolation to prevent cross-tenant data leaks.
• Billing and Access Control: Stripe integration patterns, entitlement enforcement, usage quota tracking, and noisy neighbor protection for production SaaS workloads.
• Compliance and Offboarding: Data residency routing, SOC2 checklist items, and GDPR-compliant tenant offboarding procedures to meet regulatory requirements.
• Use Case: A SaaS startup scaling from SMB to enterprise customers can use this Skill to select a hybrid tiered tenancy model, implement RLS for data isolation, set up per-tenant Stripe billing, and build compliant offboarding flows.

Quick Start

Use the saas-architecture skill to design a multi-tenant SaaS platform with pool tenancy, PostgreSQL row-level security isolation, and Stripe billing integration for your new SaaS product.