Self-hosted SaaS site-builder infrastructure for TallCMS

Every site you run as a separate TallCMS install means separate updates, separate plugin licenses, separate server configs, separate admin logins. Multisite collapses all of that into one.

Launch sites in minutes, not hours

Create a new site, assign a domain, pick a theme, start adding pages. No provisioning, no migrations, no deployment pipeline.

Build a SaaS on your own terms

Self-hosted. No per-seat pricing from a platform vendor. Your infrastructure, your margins, your customer relationships.

TallCMS Multisite handles site routing, content isolation, and domain verification — but your server needs to be configured to accept traffic for multiple domains.

This means a web server that responds to all your site domains (a wildcard or catch-all config), and a way to provision TLS certificates (Caddy, Certbot, Forge, Ploi, or your hosting provider).

The plugin doesn't manage your server or issue certificates — it verifies that domains point to the right place and marks them ready for TLS. How you provision certificates is up to your stack.

Built-in TLS verify endpoint: The plugin ships with an /internal/tls/verify endpoint that your reverse proxy can call before issuing a certificate. Pass?domain=example.com and it returns 200 if the domain belongs to an active, verified site — or 404 if not. This is how tools like Caddy's on-demand TLS know whether to provision a certificate, preventing abuse from random domains pointing at your server.

We've published a step-by-step guide based on our own production setup: Multi-Tenant SaaS on DigitalOcean with Caddy, Cloudflare, Nginx and Ploi →"