Managed WordPress for WooCommerce, Agencies, and High-Traffic Publishers
One managed platform with four deployment options. Pick the deployment your traffic and uptime needs call for.
You pay for the CPU and RAM your site draws each hour, metered as peak RAM or average CPU.
Capacity grows in small steps called cloudlets (128 MiB RAM + 400 MHz CPU); cluster packages also add web servers by load.
We run the servers, SSL renewal, and 14 daily backups. You manage plugins and themes.
Reach Togglebox engineers by chat or ticket at any hour, every day of the year.
Who Runs WordPress on Togglebox
If one of these matches your site, you’ve found your topology (the shape of your deployment: how many servers, databases, and regions). Confirm the details below, then run a cost estimate or hand it to an engineer.
Agencies and multi-site teams
Teams running 5–50 client sites, each with its own staging environment. One-click clone, role-based access, parallel staging, and Git deploy.
Choose Standalone From $7/mo per siteWooCommerce at scale
Stores running flash sales, holiday traffic, or daily checkout volume that can’t tolerate a single-server outage. Autoscaling adds web servers as traffic climbs, and every cart write is copied across a database cluster in real time, so checkout survives a failed node.
Choose Cluster From $32/moA warm copy in a second region
Sites that need a standby in another region without paying for a full cluster in each one. The standby copy stays current within seconds, and traffic reroutes automatically if a region fails.
Choose Multi-region standalone From $12/moA full cluster in two regions
Sites that need full cluster performance every day and can’t go down if a data center fails. Each region runs the complete cluster; the second region stays seconds behind the first, and DNS health checks reroute traffic on regional failure.
Choose Multi-region clustered From $44/moPrices above are starting baselines; the cost calculator estimates your actual configuration. Not sure which topology fits? Chat with an engineer: five minutes of traffic context usually settles it.
Inside Each WordPress Topology
Pick a topology to see how it’s built and what changes between tiers.
One container, scaled vertically
LiteSpeed + MariaDB + Redis + WordPress in a single dedicated stack. RAM and CPU scale in 128 MiB cloudlet steps within your limits. Best for blogs, brochure sites, agency portfolios, and moderate WooCommerce traffic.
- A single dedicated stack, with no load balancer or multi-node tier
- One MariaDB instance: no Galera cluster, no replication layer
- Vertical autoscaling only, no horizontal web nodes
- Git deploy, SFTP, and SSH access
- Same managed baseline as every tier: LiteSpeed cache, Redis, WAF, 14 daily backups
- Outgrowing one container? Clone to a Cluster topology without rebuilding the site
Standalone stack
SSL, WAF, LiteSpeed, Redis, MariaDB, PHP, and WordPress in one container.
A load-balanced cluster of app nodes
Provisioned from one marketplace template. The load balancer distributes traffic across app nodes, Galera replicates writes synchronously across the database cluster, GlusterFS keeps uploaded media consistent across web nodes, and horizontal autoscaling absorbs traffic spikes.
- LiteSpeed ADC or NGINX load balancer with health checks and HTTP/3
- Up to 16 app nodes with horizontal autoscaling on load
- MariaDB Galera multi-primary cluster with ProxySQL read/write routing
- GlusterFS replicated shared media mounted at
/data - Sequential restart, sub-5s failover, parallel staging, one-click clone
WordPress cluster topology
Load balancer, multi-node app tier, Galera database cluster, and GlusterFS shared storage.
One self-contained stack per region
Each data center runs its own LiteSpeed + MariaDB + Redis + WAF stack. Asynchronous cross-region replication keeps content in sync within seconds. DNS health checks reroute on regional failure. No shared storage layer, no clustered database, which keeps the baseline cost lower than full HA.
- Independent WordPress stack in each region with vertical autoscaling
- Asynchronous MariaDB cross-region replication
- DNS-based geographic routing with health-check failover
- Region pairing confirmed by an engineer at provisioning
- Independent backup schedule per region
Multi-region standalone
Independent stacks per region with async MariaDB replication.
A full cluster in every region
Each region runs the full Cluster topology with LiteSpeed ADC, Galera, GlusterFS, and ProxySQL configured at deploy. Synchronous Galera within a region prevents data loss on within-region node failure; asynchronous replication between regions keeps the remote copy seconds behind.
- Full HA cluster per region with horizontal autoscaling
- Galera synchronous within region, async between regions
- GlusterFS geo-replication for shared media
- DNS health-check reroute on regional failure
- Region pairing confirmed by an engineer at provisioning
Multi-region clustered topology
Full HA cluster per region with cross-region async replication and DNS failover.
Cluster topology and replication detail
Replication modes, ProxySQL routing, GlusterFS, failover behavior, and the consolidated clustering FAQ.
What Every Stack Includes
These features come with every topology. Choosing a topology changes how WordPress is wired together, not what the platform manages underneath.
- LiteSpeed + HTTP/3: LSCache page caching and HTTP/3 out of the box.
- Redis object cache: repeat database queries served from memory instead of disk.
- MariaDB with automatic tuning: a managed database on every tier (clustered tiers add ProxySQL routing and sub-5s failover on top).
- LiteSpeed WAF + brute-force protection: WordPress-aware filtering and login attempt limits.
- 14 daily backups, restore to clone: two weeks of restore points for safe pre-promotion validation.
- One-click marketplace provisioning: WordPress, LiteSpeed, MariaDB, and Redis preconfigured. No LEMP setup, no install wizard.
Launching WordPress on App Hosting
One marketplace template provisions the load balancer, multi-node app tier, and Galera database cluster together — GlusterFS shared storage is one checkbox away, with no manual wiring between layers.
Create regional stacks and the cross-region replication path in one flow, then route traffic with DNS health checks for regional failover.
Reviews from the Businesses We Keep Online
WordPress Hosting Questions
How does pricing work?
WordPress Hosting is billed hourly from a prepaid balance. You set a reserved baseline and maximum cloudlets. Autoscaling stays within those limits.
What is a cloudlet?
A cloudlet is one unit of compute: 128 MiB RAM + 400 MHz CPU. You set baseline and burst scaling in cloudlets.
What is a WordPress cluster (and do I need one)?
A WordPress cluster uses a load balancer and multiple web nodes (plus caching and shared storage) to improve availability and handle spikes. If you need redundancy and scaling headroom, it's a better fit than a single server.
What load balancer options do you support?
LiteSpeed ADC or NGINX load balancer, depending on your stack selection.
What web server options do you support?
LiteSpeed Web Server or NGINX PHP servers, with preconfigured autoscaling triggers.
What database options do you support for WordPress?
Highly available MariaDB Galera Cluster or primary-secondary replication (choose based on your workload and requirements).
How does autoscaling work for WordPress (vertical vs horizontal)?
WordPress clusters scale vertically (resources per node) and horizontally (add or remove web nodes) within limits you control. The exact behavior depends on your stack and application design.
Can I control scaling limits so costs stay predictable?
Set a reserved baseline and a maximum number of cloudlets. The cost calculator estimates your spend, and autoscaling and cost controls explains how the limits work.
What WAF options are available for WordPress?
LiteSpeed WAF if LiteSpeed is selected. Otherwise, ModSecurity with NGINX.
Do you include SSL certificates?
Paid accounts include Let's Encrypt SSL, and it renews automatically. No manual certificate management required.
Do you support WordPress multisite?
WordPress Multisite Networking is fully supported.
How do you handle media uploads in a multi-node WordPress setup?
Shared storage is included so media assets are available across web nodes.
How is WordPress on App Hosting different from WordPress on a VPS?
WordPress on App Hosting runs on a managed platform with preconfigured topologies, so you don't assemble or operate each layer yourself. If you want OS-level control and a single VM you manage end to end, see Cloud VPS.
Who should use multi-region WordPress hosting?
Multi-region WordPress hosting is best for teams that need strong global performance and resilience during spikes and regional outages.
Can I start with a trial first?
Start with a WordPress trial, then expand to multi-region as traffic and uptime needs grow.
Do you help with WordPress migration?
We can help plan migration sequencing, cutover timing, and rollback safety. Reach out to map your migration path.
How do I choose the right data center region?
See available regions and facility details on the data centers page. Choose the region closest to your users, or the one that meets your data residency requirements.
No matching questions found.
See How Your App Runs Here
- Pay as you go: baseline plus actual use, not a fixed tier
- Turnkey clustering: traffic reroutes once clustering is enabled
- From Git push to live: in minutes, not hours
- Engineers on call: real support around the clock
Start a real trial environment
Deploy your app, test the platform, and estimate cost before you commit. After the trial, your first deposit gets a 50% bonus added automatically.