Multisite hosting where site 148 behaves like site one.
A network is one WordPress install and one database serving many sites. Everything that matters - domains, certificates, backups, updates - has to work per site anyway.
One install, many sites, no compromises.
The network is shared. The things your customers see should not feel like it.
Domains mapped, certificates automatic
Point a customer's domain at the network and the certificate is issued and renewed without anyone remembering to. Each mapped domain gets its own, not a wildcard shared with strangers.
A shared cache the network actually shares
One object cache in front of the whole install, so a lookup warmed by one site is warm for the next. Growth in site count does not become growth in query time.
Restore one site, not the network
Backups cover the whole install, and a restore can target a single site's tables and uploads - so one customer's mistake is not everyone's rollback.
Updates with per-site results
Run core and plugin updates across the network and see which sites succeeded rather than a single pass or fail for the whole thing.
Add a site without a deploy
New sites are created from the dashboard and inherit the network's configuration immediately. No provisioning ticket, no waiting.
See the whole network at once.
One dashboard for every site in the network: which are updated, which failed, which are growing. Add a site, map a domain, or roll one back without touching the others.
- Add sites and map domains in a click
- Network-wide update runs with per-site status
- Per-site resource and storage view
- Alerts when one site starts misbehaving
Site 148 is as fast as site one.
Every site in the network gets edge caching, NVMe storage and the shared object cache, so growth shows up in your dashboard rather than in your load times.
What we change for Multisite
A network fails differently from a single site: the shared parts become bottlenecks and the per-site parts become admin.
| Setting | What we do | Why |
|---|---|---|
| Domain mapping | Per-domain certificate, issued and renewed automatically | A network's customers each bring their own domain, and manual certificate renewal across dozens does not scale. |
| Object cache | Shared across the install, keyed per site | One cache in front of a shared database is what stops query time rising with the number of sites. |
| Backups | Whole install, restorable per site | Rolling the network back because one site broke would punish every other tenant. |
| Update runs | Network-wide with per-site results | A single pass or fail across 148 sites tells you nothing about which one needs attention. |
| Uploads | Per-site directories with their own quota accounting | Storage has to be attributable to a site or you cannot bill it or cap it. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Can each site in the network use its own domain?
How many sites can one network hold?
Can I restore just one site?
Do updates run across the whole network at once?
Run the network, not the servers.
Bring an existing network across - migration is free, including the mapped domains.