0009: Adopt better-supabase and PermDock from npm
CentraKit moves its Supabase data access onto better-supabase and its roles and permissions onto PermDock, consuming both as published npm packages.
0011: Multi-brand path routing
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.
0009: Adopt better-supabase and PermDock from npm
CentraKit moves its Supabase data access onto better-supabase and its roles and permissions onto PermDock, consuming both as published npm packages.
0011: Multi-brand path routing
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.
Subscriptions, invoices, payment methods and the billing contact are read from the Stripe Sync Engine's tables instead of a hand-written Stripe mirror.
CentraKit kept its own copy of Stripe's billing objects: organization_billing_customers, organization_subscriptions with a history table, organization_payment_methods, organization_invoices and organization_tax_ids, refreshed by a webhook processor and a reconcile job (about 2,500 lines). The better-supabase billing and entitlements blocks read Stripe's objects from the Stripe Sync Engine and never call Stripe to find out what a tenant pays for. Keeping the mirror would mean asking the blocks to work against an app-specific copy, which their design argues against.
Run the Stripe Sync Engine 0.48.5 (@supabase/stripe-sync-engine, pinned in the catalog) as a library inside the API app. The Stripe webhook consumer lets the engine store each platform event in the stripe schema and then hands the event to the better-supabase billing block, which links the customer to its organization. The engine owns the stripe schema and installs it with its own migrations (pnpm stripe:sync:migrate); CentraKit's declarative schema never defines it, and every CentraKit function that reads it checks that the table exists. CentraKit keeps its plan catalog, credit packages, price publishing and invoice recipients, and derives each organization's plan from the subscription item's price (billing.organization_plans).
POSTGRES_URL in the SaaS and API apps. docs/operations/stripe-billing.mdx lists the hosted steps.invoice_status type in another schema and stores timestamps as integer; the migration script works around the first, and dates after 2038 cannot be stored.refreshFromStripe, which runs syncCustomer, after plan changes, cancellations, billing detail updates and admin invoice transitions. That doubles the Stripe calls for each change, because the webhook consumer stores the same events moments later. The follow-up removes the inline sync from mutations, returns the state from the Stripe response, and keeps syncFromStripe as the explicit refresh.getPaymentClientSecretForPortal creates a new PaymentIntent while the page renders when the open intent no longer matches the balance. A page view should never create Stripe objects. The follow-up moves Elements to deferred intent creation (mode: "payment" with amount and currency), so the intent is created in a Server Action when the customer pays.Last updated on
0009: Adopt better-supabase and PermDock from npm
CentraKit moves its Supabase data access onto better-supabase and its roles and permissions onto PermDock, consuming both as published npm packages.
0011: Multi-brand path routing
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.