Runtime and processes
Check WordPress Multisite networks where site count, plugin compatibility, database growth, backups, domain mapping, and administrator boundaries matter more than one ordinary blog.
WordPress multisite hosting
Plan a WordPress network with enough room for its sites, uploads and database. Check plugin compatibility and administration requirements before ordering.
Hosting options
WordPress hosting with PHP, databases, HTTPS, email and Virtualmin. You maintain your site software and plugins.
See WordPress hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check WordPress Multisite networks where site count, plugin compatibility, database growth, backups, domain mapping, and administrator boundaries matter more than one ordinary blog.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
Multisite runs every subsite through one WordPress install and one database, so total traffic across the network drives PHP worker demand, not the traffic of the busiest site alone. Count active subsites, logged in editors, and scheduled tasks across all sites before choosing memory and CPU.
The wp_blogs, wp_site, and per site options tables grow with every added subsite, and autoloaded options load on each request for each site. Audit autoload size with a database query, keep per site plugin sets small, and test domain mapping and SSL for every mapped domain before launch.
Run a query against wp_options grouped by autoload to find the total autoloaded bytes per site. Large autoload data slows every request on every subsite that shares the install.
Network activated plugins update once for all sites, so test updates on a staging copy of the network first. A broken network wide plugin can take down every subsite at the same time.
A full network backup is large and slow to restore for a single broken subsite. Keep a method to export and restore one site's tables and uploads separately.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.