DoctorsCMS
One codebase, any brand
A white-label, multi-tenant Payload CMS: one codebase that re-skins per deployment through environment-driven brand config.
Industry
SaaS · White-label CMS
Timeline
Ongoing product
Tech Stack
The Challenge
Serving several brands and kinds of customer usually means a fork of the CMS per client, or a single-tenant app with a tenant column bolted on.
The Solution
The shared core handles the hard multi-tenant problems, so each deployment only needs its own brand and content. Collections, access control and API keys are tenant-scoped out of the box. Product name, enabled verticals and default settings come from environment config, so a new deployment is a config change, not a fork. Blocks, heroes and settings panels can be gated by a tenant’s business type, such as synagogue, real estate or general services, so one build serves several kinds of customer. Stripe subscription billing for tenants is wired in, with a manual path for accounts billed outside Stripe.
Results
One codebase
a new brand is a config change, not a fork
Multi-tenant
tenant-scoped collections, access control and API keys
Billing included
Stripe subscriptions for tenants, plus a manual billing path