← Docs

WordPress Multisite on Belov Cloud

Running a WordPress Multisite network here — and what it costs. The short version: a network on one domain is one site on your plan with unlimited subsites included, everything (backups, staging, self-healing) operates on the whole network at once, and any subsite can get its own custom domain self-serve.

Path-based networks (subsites like example.com/blog and example.com/shop) are first-class: the connect plugin reads your network's shape and the same verified migration pipeline moves it in one click — network constants, subsite tables and all — with every subsite checkable on a private preview before DNS moves. Networks on subdomains (blog.example.com) are migrated by our team by hand for now, free — just contact support to arrange it.

Once hosted, the network behaves like one site in the panel: a daily snapshot contains every subsite's data, a staging copy is the full network on a private URL, push-to-live moves the network in one verified step, and the self-healing copilot, edge cache and WAF cover every subsite alike.

1. 1
   Migrate the network in

   Start a migration as usual — connect the network's main site with the Belov Cloud Connect plugin. A path-based network migrates automatically, subsites and all; if yours runs on subdomains, we'll move it for you by hand, free.
2. 2
   Give a subsite its own domain (optional)

   On the site's Network tab, attach a domain to any subsite. Reserving is free — you get the one DNS record to add at your registrar.
3. 3
   Check DNS and activate

   Once the record resolves, activate. We re-route the subsite to its new domain, update its canonical URLs and rewrite content links with boundary-safe precision — sibling subsites are never touched.
4. 4
   Detach any time

   Detaching reverts the subsite to its network path exactly as it was, and the plan slot frees itself.

← All guides