🔍⌘K

Start typing to search docs.

Platform Overview

1.0.0

Conceptual tour of App Factory Forge, multi-tenant boundaries, and customer outcomes.

On this page
  1. Why Forge exists
  2. Core tenants
  3. Lifecycle at a glance
  4. Where to go next

Why Forge exists

App Factory Forge gives multi-tenant SaaS teams a single pipeline from idea to production domain. Every customer login, generated app, and domain record runs through the same audited workflow to keep data isolated while avoiding infrastructure sprawl.

  • Shared Supabase project with prefixed tables powers auth, storage, and edge functions.
  • Vercel handles dashboard and customer apps with automatic certificate provisioning.
  • Stripe drives billing, entitlements, and usage analytics.

Info

Forge ships with opinionated defaults, but every layer (providers, billing, hosting) has escape hatches so enterprise teams can fork without rewriting the platform.

Core tenants

  1. Tenant isolation by configuration – ops/apps.yaml describes providers, domains, table prefixes, and secrets for each tenant application.
  2. Single source of truth – CLI, dashboard, SDKs, and generated apps consume the same configuration loader from @app-factory/config.
  3. Auditable automation – Semantic-release, Pulumi outputs, and Supabase migrations all emit artifacts back into the repo for review.

Lifecycle at a glance

View

Capture customer requirements, select plan, and configure tenant metadata in the dashboard. Forge stores everything in Supabase, ready for CLI automation.

Where to go next