0010: Billing on the Stripe Sync Engine
Subscriptions, invoices, payment methods and the billing contact are read from the Stripe Sync Engine's tables instead of a hand-written Stripe mirror.
0012: The Data API for module access from request paths
Request paths reach better-supabase modules and Auth through the Data API and the Auth admin API; direct Postgres is reserved for the libraries that only speak SQL.
0010: Billing on the Stripe Sync Engine
Subscriptions, invoices, payment methods and the billing contact are read from the Stripe Sync Engine's tables instead of a hand-written Stripe mirror.
0012: The Data API for module access from request paths
Request paths reach better-supabase modules and Auth through the Data API and the Auth admin API; direct Postgres is reserved for the libraries that only speak SQL.
Every brand is served from one app host with the API, MCP server and docs as path rewrites, and the SaaS app renders each brand through a hidden brand root param.
ADR 0003 served every surface from its own host: app.*, api.*, docs.*, the sample.* marketing site and the showcase on the apex, all derived from one NEXT_PUBLIC_SITE_URL in packages/foundation/src/public-urls.ts. One deployment now serves several product brands (CentraKit, MechUp and StableDock), each on its own domain. With host routing every brand would need its own API, docs and marketing hosts, plus OAuth redirect URLs and Auth allow list entries for each, and a single site URL cannot describe more than one brand. The public website of each brand moves to Lovable, so the apex and www hosts no longer belong to this deployment.
Serve each brand from one app.<brand> host and route by path. The root vercel.json sends /api/* and the public /portal/calendars/:token and /portal/files/:token routes to the api service, /mcp to its /api/mcp handler, /.well-known/oauth-protected-resource to api, and /docs/*, /llms.txt and /llms-full.txt to the docs service, which has basePath: "/docs". Everything else goes to saas. Only saas, api and docs deploy. apps/marketing and apps/showcase stay in the repo but leave Vercel, and the apex and www domains point at Lovable through DNS. The api.*, docs.* and sample.* hosts are cut over without redirects.
The brand registry in packages/foundation/src/brands.ts lists every brand with its hosts per environment. production and development are picked from VERCEL_ENV, and anything else is local. NEXT_PUBLIC_SITE_URL only overrides the default brand's origin in the local environment, for E2E builds on a port.
| Brand | Production | Development (develop) | Local |
|---|---|---|---|
| CentraKit | app.centrakit.com | app.centrakit.dev | app.localhost |
| MechUp | app.mechup.com | mechup.centrakit.dev | mechup.localhost |
| StableDock | app.stabledock.app | stabledock.centrakit.dev | stabledock.localhost |
| Caresly | app.caresly.app | caresly.centrakit.dev | caresly.localhost |
| PropDock | none yet | propdock.centrakit.dev | propdock.localhost |
| MarryDuck | none yet | marryduck.centrakit.dev | marryduck.localhost |
| SignalDock | none yet | signaldock.centrakit.dev | signaldock.localhost |
| Spacelio | none yet | spacelio.centrakit.dev | spacelio.localhost |
| LegalDock | none yet | legaldock.centrakit.dev | legaldock.localhost |
The SaaS route tree is app/[locale]/[brand]/.... The proxy maps the host to a brand with a synchronous lookup in a frozen Map and inserts the brand after the locale in the next-intl rewrite, so [brand] never shows in a public URL. It adds no fetch, database, cookie or header work. Rendering reads the brand root param, so every static shell is prerendered per brand with the right name, logo, fonts and theme. Server Actions and route handlers have no root params and read the brand from the request host instead.
Each organization belongs to one brand through organizations.brand, set from the request host when the organization is created. The CentraKit host is where the tenants of every brand are managed, so it lists and opens all of a user's organizations. A product brand host lists and opens only that brand's organizations, and another brand's slug renders not found there. Platform admins see every brand in /admin, with a brand column and filter, and a trigger lets only platform admins and the service role change an organization's brand. Organization links decide between staff and portal before navigation, so customer-only users get /<orgSlug>/portal links.
Per-brand theming is tokens only: [data-brand="<id>"] overrides for neutrals, primary, ring, charts, radius, menu accent, --font-sans and a new --font-heading, generated from a shadcn preset. Every brand's preset is still null, so all brands render the CentraKit tokens and placeholder marks. BrandMark in @workspace/ui takes a brand id, and AppBrandMark in apps/saas reads the root param.
The MCP resource moves from <origin>/api/mcp on the API host to <brand app origin>/mcp, and the protected resource metadata is built per host. The accepted token audiences are the /mcp URL of every brand host in the environment, Supabase's default authenticated audience and MCP_RESOURCE_AUDIENCE.
https://app.<brand>/mcp. Tokens issued for the old https://api.centrakit.com/api/mcp audience are rejected unless MCP_RESOURCE_AUDIENCE still carries that value, so this is a breaking change for MCP clients.https://app.<brand>/api; the CLI defaults to the CentraKit app host and takes --host for another brand.type URIs move to https://app.centrakit.com/docs/developers/errors#<code> on every brand host.site_url, which is the CentraKit host) still say CentraKit. Emails take the brand's name as the sender name but keep the one EMAIL_FROM address.typedRoutes stays on in apps/saas.apps/showcase is the CentraKit template site, not a brand host, so it is exempt from the rule against hardcoded product names. Its copy may name CentraKit directly. apps/marketing is not exempt.main and develop, a Portless alias, and its preset, fonts and assets.Last updated on
0010: Billing on the Stripe Sync Engine
Subscriptions, invoices, payment methods and the billing contact are read from the Stripe Sync Engine's tables instead of a hand-written Stripe mirror.
0012: The Data API for module access from request paths
Request paths reach better-supabase modules and Auth through the Data API and the Auth admin API; direct Postgres is reserved for the libraries that only speak SQL.