Clients edit their own pages
Every site has its own pages, navigation, colours and contact details in Directus. No staging branch per client.
Multi-site publishing
Client websites without the agency overhead.
Run every client site from one Directus instance and one Railway deployment. New domains take a DNS record, not a release.
Built for studios, freelancers and product teams
- Studios
- Freelancers
- Agencies
- Product teams
The work you keep, the overhead you drop
The platform handles routing, themes, SEO, forms and publishing. You focus on art direction and content.
One deployment, many domains
Subdomains and custom domains resolve to a site record at request time. Adding a client is a database row.
Publish without a deploy
A Directus Flow calls the revalidate webhook and the affected site is rebuilt from cache.
1
deployment to maintain
0
releases per new client
∞
domains you can attach
100%
of content client-editable
Questions owners ask first
Do I need a separate Directus project per client?
No. One Directus instance holds every site, page and lead. Permissions and the site relation keep data separated.
How do custom domains work?
Add the client's domain in Railway and point DNS at the deployment. The app matches the host to sites.domain — no code change.
Can clients break each other's sites?
Sites are separate records. Give each client their own Directus role scoped to their site if you want hard isolation.
What happens when I edit content?
Directus calls /api/revalidate with a shared secret, which clears the CMS cache. Visitors see the change on the next request.
Turn the platform into recurring revenue.
Start with one client site, then duplicate the record for the next. Hosting stays one Railway service.