~/solutions/headless-multisite
Headless Multisite
One backend. Every website.
Separate websites, each with its own custom front end, all managed from one place. One backend delivers the content everywhere, with access set per client and per person. It stays private and is only reached at build time, so the sites are static, fast and secure, with server powers where they need them.
how it works
Private backend. Static sites.
The backend manages everything but is never on the front line. The sites only meet it at build time.
One backend
One codebase holds the content, media, users and roles for every site. It lives behind a VPN, not on the public internet.
Build
When someone publishes, a build pulls that site’s content and turns it into a finished static site.
Independent sites
Each site has its own custom front end and its own domain. It’s served as static files, with server powers where it needs them.
Nothing to break into
The live sites have no database and no admin login, and they never talk to the backend.
Sites keep running
Backend down for maintenance? Every site stays online, because each one is already built.
One thing to maintain
Updates, security fixes and new features go into one backend, not one per site.
access control
One login. The right sites.
Everyone works in the same backend, but nobody sees more than they should. Access is set per client, per person and per section.
| Person | client-a.com | client-b.com | client-c.com | your-brand.com |
|---|---|---|---|---|
| Youowner | full access | full access | full access | full access |
| Client Aeditor | can edit | no access | no access | no access |
| Client Beditor | no access | can edit | no access | no access |
| Your teamwriter | no access | no access | no access | blog only |
| Translatoreditor | DE pages | no access | DE pages | no access |
Per client
Each client logs in to the same backend and sees only their own site.
Per person
Employees, writers and partners get their own login and their own rights.
Per section
Limit someone to the blog, one language or a single page type.
where it fits
Many sites, one place.
If you run more than one website, or run websites for other people, one backend saves work on every one of them.
Client websites
A studio or agency running many client sites, each client with their own login.
client-a.comclient-b.comclient-c.com
Several brands
One company, a separate site per brand or product line.
brand-a.combrand-b.com
Branches and locations
A site per city, shop or franchise, edited by the people who run it.
city-one.comcity-two.com
Countries and languages
A site per market, with translators who only see their language.
brand.debrand.bg
The stack, picked per project
- backend:
- one codebase, private, behind a VPN
- connection:
- build time only
- access:
- roles per client, person and section
- front_ends:
- custom per site, static
- content:
- your CMS of choice or your own API
- hosting:
- Managed Hosting →
- agents:
- Agent Ready →
Each site can look and work however it needs to. Only the backend is shared.
open for projects
More than one site? Manage them from one place.
Tell me how many sites you run and who edits them. I’ll tell you what one backend would look like for you.