Saas Dash
Architecture

Platform Model

Internal operating model for owning, running, and evolving client SaaS products

What Saas Dash is for

Saas Dash is the internal platform for:

  • owning and operating SaaS applications
  • building and maintaining client platforms
  • managing tenant configuration
  • controlling app availability and plans
  • running migrations, resets, and operational workflows
  • connecting product, engineering, and marketing decisions in one control plane

This is not a public docs site. It is the internal operating manual for the platform.

Business model

The platform supports three connected tracks:

  • operated SaaS products
  • custom SaaS development for clients
  • marketing and growth services around those products

That means the system has to support both:

  • a clean internal control plane
  • repeatable product delivery across multiple tenants

Core system shape

The platform is split into:

  • platform control
  • tenant runtimes
  • admin surfaces
  • marketing and operational tooling

Platform control owns:

  • tenants
  • apps
  • plans
  • entitlements
  • providers
  • worker configuration
  • shared metadata

Tenant runtimes own:

  • workspace data
  • end-user behavior
  • product-specific execution

Non-negotiable rule

The platform DB is the source of truth.

There is no long-term YAML authority, no hybrid fallback, and no workspace-local truth for first-party app existence.

On this page