01
Dynamic-page cache rules
Cart, checkout, and account pages contain customer-specific state and should remain outside full-page caching.
Managed WooCommerce hosting
Run a WordPress store on LiteSpeed and NVMe storage with daily recovery points, while keeping cart, checkout, account, inventory, and payment behavior in the application’s control.
Bitfoo manages the hosting platform; you manage the application.
Server managed by Bitfoo
Dynamic pages stay live
Let’s Encrypt available
Restore through JetBackup
Choose by responsibility
Catalogue size alone does not determine the answer. Traffic patterns, extensions, imports, search, scheduled jobs, and checkout activity all affect the resource profile.
Managed platform
Start with the conventional WordPress stack and a control-panel workflow.
Custom environment
Move when the store’s workload or dependencies require a server environment your team controls.
Production foundation
The store’s uncached requests and operational workflow matter more than an isolated headline speed claim.
01
Cart, checkout, and account pages contain customer-specific state and should remain outside full-page caching.
02
Product queries, inventory changes, orders, and extension activity all share the hosting account’s allocation.
03
Serve the full store over HTTPS and validate that themes, assets, callbacks, and integrations avoid mixed content.
04
Daily restore points help with recovery, but restore timing must be reconciled with orders and payment records.
Plan comparison
Business is the practical starting point for a production store. Pro adds capacity for larger or more active stores and for agencies managing several installations.
Swipe horizontally to compare every plan.
| Specification | Starter Testing or a very small catalogue | Business A production store with moderate activity Recommended starting point | Pro Larger stores, more traffic, or several installations |
|---|---|---|---|
| Storage | 10GB NVMe SSD | 50GB NVMe SSD | 150GB NVMe SSD |
| RAM | 512MB | 1GB | 2GB |
| Bandwidth | Unmetered | Unmetered | Unmetered |
| Sites | 1 | 10 | Unlimited |
| Backups | Daily | Daily | Daily |
| SSH access | — | Yes | Yes |
| Price | Coming soon | Coming soon | Coming soon |
| Availability | Join waitlist → | Join waitlist → | Join waitlist → |
Exact prices will appear when ordering opens. Shared hosting includes platform management; application maintenance remains with you.
Before deployment
A homepage check is not enough for an ecommerce launch. Validate the stateful flows that produce and fulfill an order.
Verify product selection, tax, shipping, payment, confirmation email, order status, and refunds in the intended environment.
Keep cart, checkout, account, and other customer-specific endpoints out of full-page caching.
Check background actions, subscription renewals, webhooks, imports, and any extension-specific scheduled tasks.
Know how orders created after the selected backup would be reconciled before restoring the database.
No. WooCommerce identifies cart, checkout, and account pages as customer-specific. They should bypass full-page caching so each shopper receives current session data.
Starter can support testing or a very small installation, but Business is the practical starting point for a production store because it provides more account capacity and SSH access.
Bitfoo manages the shared hosting platform. Store configuration, extensions, product data, payment providers, updates, and checkout testing remain the store owner’s responsibility.
Consider VPS when the store requires custom services, persistent processes, or an environment outside shared-hosting limits—and when someone is ready to administer that server.