SaaS Architecture Patterns: Multitenancy, Billing, and Feature Flags

SaaS architecture differs from traditional software in three critical ways: multiple customers share the same infrastructure (multitenancy), business model depends on subscription billing, and different customers get different features (feature flags/gating). Get these wrong early and you'll refactor under production load.

Multitenancy Strategies

Pool model: All tenants share the same database tables. Rows include a tenant_id column. Simple to implement and operate; row-level security in PostgreSQL enforces isolation. Used by most early-stage SaaS products.

Silo model: Each tenant gets a separate database or schema. Maximum isolation and compliance—ideal for enterprise customers with strict data residency requirements. Much higher operational complexity.

Hybrid: Small/mid tenants in pool; enterprise tenants in dedicated silos. The best of both, implemented when you have enterprise demand.

Subscription Billing with Stripe

# Create subscription on user signup
subscription = stripe.Subscription.create(
    customer=customer_id,
    items=[{"price": "price_monthly_pro"}],
    payment_behavior="default_incomplete",
    expand=["latest_invoice.payment_intent"]
)
# Store subscription_id and status in your database

Use Stripe webhooks (customer.subscription.updated, invoice.payment_failed) to keep your local subscription state in sync. Never trust client-side subscription status.

Feature Flags for Plan Gating

def user_can_use(user, feature: str) -> bool:
    plan_features = {
        "free": ["blog", "contact_form"],
        "pro": ["blog", "contact_form", "analytics", "api_access"],
        "enterprise": ["blog", "contact_form", "analytics", "api_access", "sso", "audit_logs"]
    }
    return feature in plan_features.get(user.plan, [])

Startup Operational Metrics Framework

The following Python script illustrates how to build a clean programmatic model to track unit economics, CAC payback period, NRR (Net Revenue Retention), and LTV ratios dynamically:

class SaaSUnitEconomicsTracker:
    def __init__(self, mrr: float, total_users: int, sales_marketing_cost: float, new_users: int, churned_users: int) -> None:
        self.mrr = mrr
        self.total_users = total_users
        self.sm_cost = sales_marketing_cost
        self.new_users = new_users
        self.churned_users = churned_users

    @property
    def arpu(self) -> float:
        """Average Revenue Per User (Monthly)"""
        return self.mrr / (self.total_users if self.total_users > 0 else 1)

    @property
    def cac(self) -> float:
        """Customer Acquisition Cost"""
        return self.sm_cost / (self.new_users if self.new_users > 0 else 1)

    @property
    def churn_rate(self) -> float:
        """Monthly Churn Rate"""
        return self.churned_users / (self.total_users if self.total_users > 0 else 1)

    @property
    def ltv(self) -> float:
        """Customer Lifetime Value"""
        return self.arpu / (self.churn_rate if self.churn_rate > 0 else 0.01)

    @property
    def ltv_cac_ratio(self) -> float:
        return self.ltv / (self.cac if self.cac > 0 else 1)

    @property
    def payback_period_months(self) -> float:
        """Payback period in months"""
        return self.cac / (self.arpu if self.arpu > 0 else 1)

# Example execution
if __name__ == "__main__":
    tracker = SaaSUnitEconomicsTracker(
        mrr=50000.0, total_users=1000,
        sales_marketing_cost=15000.0, new_users=50,
        churned_users=20
    )
    print(f"LTV:CAC Ratio: {tracker.ltv_cac_ratio:.2f} (Target: >3.0)")
    print(f"Payback Period: {tracker.payback_period_months:.1f} months")

Production Trade-offs & Implementation Decisions

Deploying this solution in production environments requires a careful analysis of the trade-offs involved. For instance, focusing purely on consistency (such as ACID compliance) can limit network throughput and horizontal scalability. On the other hand, adopting an eventual consistency model can lead to dirty reads and requires complex conflict resolution strategies in the application layer.

At MirahLabs, our engineering teams balance these architectural constraints by separating critical transaction paths from analytics workloads. We apply message-driven architectures with idempotent consumer systems to guarantee that network failures or retries do not result in double processing or state contamination.

Real-World Benchmarks & Resource Planning

Below is a typical performance comparison profile compiled by our engineering team in staging environments under simulated loads (10k concurrent virtual users):

When capacity planning, we recommend scaling out horizontally using containerized workloads rather than vertically upgrading underlying instance models. This maximizes uptime and provides cost efficiency through dynamic scaling policies.

Security Considerations & Vulnerability Mitigations

No production blueprint is complete without addressing security. Ensure that all data paths utilize encryption in transit (TLS 1.3) and at rest (using AES-256). Furthermore, implement strict Role-Based Access Control (RBAC) to limit operations. For APIs, always enforce rate limits (e.g. using token bucket algorithms in Redis) and run continuous static application security testing (SAST) in your CI pipeline.

How MirahLabs Applies This in Practice

Our experience building high-volume solutions like MirahCare.ai and Ayurveda.ai has taught us that early optimization is often a trap, but ignoring structural security and data design early leads to fatal development blocks. We design all client products from day one to support modular extensions, robust query indexing, and standard schema definitions, ensuring rapid iteration without technical debt growth.

Startup Operational Metrics Framework

The following Python script illustrates how to build a clean programmatic model to track unit economics, CAC payback period, NRR (Net Revenue Retention), and LTV ratios dynamically:

class SaaSUnitEconomicsTracker:
    def __init__(self, mrr: float, total_users: int, sales_marketing_cost: float, new_users: int, churned_users: int) -> None:
        self.mrr = mrr
        self.total_users = total_users
        self.sm_cost = sales_marketing_cost
        self.new_users = new_users
        self.churned_users = churned_users

    @property
    def arpu(self) -> float:
        """Average Revenue Per User (Monthly)"""
        return self.mrr / (self.total_users if self.total_users > 0 else 1)

    @property
    def cac(self) -> float:
        """Customer Acquisition Cost"""
        return self.sm_cost / (self.new_users if self.new_users > 0 else 1)

    @property
    def churn_rate(self) -> float:
        """Monthly Churn Rate"""
        return self.churned_users / (self.total_users if self.total_users > 0 else 1)

    @property
    def ltv(self) -> float:
        """Customer Lifetime Value"""
        return self.arpu / (self.churn_rate if self.churn_rate > 0 else 0.01)

    @property
    def ltv_cac_ratio(self) -> float:
        return self.ltv / (self.cac if self.cac > 0 else 1)

    @property
    def payback_period_months(self) -> float:
        """Payback period in months"""
        return self.cac / (self.arpu if self.arpu > 0 else 1)

# Example execution
if __name__ == "__main__":
    tracker = SaaSUnitEconomicsTracker(
        mrr=50000.0, total_users=1000,
        sales_marketing_cost=15000.0, new_users=50,
        churned_users=20
    )
    print(f"LTV:CAC Ratio: {tracker.ltv_cac_ratio:.2f} (Target: >3.0)")
    print(f"Payback Period: {tracker.payback_period_months:.1f} months")

Production Trade-offs & Implementation Decisions

Deploying this solution in production environments requires a careful analysis of the trade-offs involved. For instance, focusing purely on consistency (such as ACID compliance) can limit network throughput and horizontal scalability. On the other hand, adopting an eventual consistency model can lead to dirty reads and requires complex conflict resolution strategies in the application layer.

At MirahLabs, our engineering teams balance these architectural constraints by separating critical transaction paths from analytics workloads. We apply message-driven architectures with idempotent consumer systems to guarantee that network failures or retries do not result in double processing or state contamination.

Real-World Benchmarks & Resource Planning

Below is a typical performance comparison profile compiled by our engineering team in staging environments under simulated loads (10k concurrent virtual users):

When capacity planning, we recommend scaling out horizontally using containerized workloads rather than vertically upgrading underlying instance models. This maximizes uptime and provides cost efficiency through dynamic scaling policies.

Security Considerations & Vulnerability Mitigations

No production blueprint is complete without addressing security. Ensure that all data paths utilize encryption in transit (TLS 1.3) and at rest (using AES-256). Furthermore, implement strict Role-Based Access Control (RBAC) to limit operations. For APIs, always enforce rate limits (e.g. using token bucket algorithms in Redis) and run continuous static application security testing (SAST) in your CI pipeline.

How MirahLabs Applies This in Practice

Our experience building high-volume solutions like MirahCare.ai and Ayurveda.ai has taught us that early optimization is often a trap, but ignoring structural security and data design early leads to fatal development blocks. We design all client products from day one to support modular extensions, robust query indexing, and standard schema definitions, ensuring rapid iteration without technical debt growth.