One login, many businesses
Agencies and multi-brand operators: every business, one account, real separation.
Run one business or a family of them: each organization has its own data, brand, site, and members — cleanly separated — while you switch between them with one login. Agencies white-label the whole stack; roll-up dashboards see across the family.
How it helps you
Real multi-tenancy, not folders
Each org is isolated at the data layer — clients can never see each other.
White-label to your brand
Partners run their own branded sites and portals on top of the same backend.
See across the family
Parent orgs get roll-up views of the children — an agency dashboard that is actually live.
The walkthrough
Create a new organization in-app
Sub-accounts spin up from the dashboard, GHL-style, with defaults seeded.
Each gets its own site
A branded clone of the same template, on its own domain, upgradeable forever.
Operate from one seat
Switch orgs with one login; permissions per org; roll-ups for the parent.
Shipped features behind this
From the same machine-readable catalog we publish at /features.json — what your AI reads to learn the platform.
Add an organization (seed a prospect)
An operator seeds a prospect organization — a lightweight pricing-anchor stub for a business that isn't a Genesis customer yet — so they can price against a real organization_id. The referred owner's email is captured (optional but encouraged) as a future claim key; no login or role is created. Brand/marketing/naming for the seeded org inherit from the caller's white-label root (resolved by the backend + comms layer, not chosen on the form).
Roles & permissions admin
The reusable RBAC-admin example: member list with roles, effective permissions with role-vs-override provenance, grant/revoke overrides, plus a guide page explaining the model. The page partners copy when they need admin surfaces.
Billing & plan
The org's platform subscription on the record: plan, status, current billing period, and the last three invoices with per-line L-MONEY amounts (plan / extra seats / AI credits / total). Read surface — plan changes run through the platform's processor flows, not template forms.
Common questions
Can my clients build their sites with AI tools?
Yes — that is the point of the platform: they bring any front end (Lovable, v0, Bolt, hand-built) and connect it to their organization’s backend. See /build for the copy-paste prompts.
See it, then build on it
This whole site runs on the same platform — fork the template, or point a front end you built with Lovable, v0, Bolt, Claude, or Cursor at the backend.