You've just launched a niche t-shirt shop, stocked with 120 designs, and you expect a handful of customers to browse during a quiet weekday. You want a platform that won't choke on ten simultaneous visitors, that will keep order data safe, and that won't bleed your budget. The Ember plan gives you exactly that baseline.
Here's what the Ember environment looks like for a WooCommerce store.
What Ember Provides for WooCommerce
Ember (£20 /mo) includes:
- 3 sites on a single account
- 40 GB SSD storage
- PostgreSQL 16 per-customer database
- 12-hour encrypted backups to Backblaze B2
- PHP-FPM 8.3 with OPcache enabled
- PHP-FPM concurrency sized to the plan's reserved resources
- Kernel-enforced resource limits and nftables firewall
Ember is the entry point for WooCommerce: it is the first plan with PHP and a database (Flameling is static-only and cannot run WooCommerce at all). Ember's per-customer PostgreSQL 16 handles concurrent writes - such as order inserts - rather than serialising them behind a single-writer lock, limited mainly by PHP concurrency and available RAM. This removes the biggest theoretical bottleneck for small shops.
How Many Products and Visitors Fit Comfortably
A typical product row in WooCommerce occupies about 2 KB in the database. With 120 products you're using roughly 240 KB of storage for catalog data - a drop in the bucket compared with the 40 GB you have available.
The real limiter is PHP concurrency. Each request that touches the cart or checkout consumes a PHP worker and about 80-120 MB of RAM. Ember's PHP-FPM concurrency therefore caps how many checkout-related requests can run at the same time. Catalog pages are far lighter; they often finish within 150 ms and free the worker quickly.
In practice, a store with:
- Up to 200 products
- 30-40 concurrent visitors (most browsing, a few adding to cart)
- 30-50 daily orders
will feel snappy on Ember. You'll see queueing only if many customers try to complete checkout in the same second, which is rare for low-traffic shops.
Measuring the Real-World Load
You can verify the load with a quick top or htop session while you simulate traffic. For example:
# Show PHP-FPM processes and memory usage
ps -C php-fpm -o pid,cmd,%mem,%cpu --sort=-%cpu | head -n 5If you see the PHP workers pinned near 80 % CPU and memory usage creeping toward the per-site limit, you're approaching the ceiling.
Another useful metric is the OPcache hit rate. High hit rates (90 %+) mean PHP bytecode is staying in memory, reducing CPU work on each request. You can see this in Tools → Site Health → Info → Server inside WordPress.
When to Consider Upgrading
If you notice any of the following, it's time to look at the Blaze plan:
- More than 80 daily orders - order bursts will start queuing on the available PHP workers.
- A product catalog over 500 items - database size still isn't a problem, but page generation time grows and you may want extra RAM.
- Regular traffic spikes of 60-80 simultaneous shoppers - typical of flash sales or holiday promotions.
Blaze (£40 /mo) provides more PHP capacity, expands storage to 60 GB, and tightens the backup interval to 6 hours. For most small-to-medium shops that run occasional promotions, Blaze provides the headroom without a huge cost jump.
Keeping the Store Healthy on Ember
- Enable a page-caching plugin - cache catalog pages, leave cart and checkout dynamic.
- Monitor worker usage - a simple cron job can log the number of busy PHP-FPM processes and alert you if it stays at the max for more than a minute.
- Run an on-demand backup before a big sale - the backup button in the portal creates a fresh snapshot, giving you a clean restore point.
- Keep OPcache warm - avoid unnecessary file changes. When you do update a theme or plugin, a single PHP-FPM restart (
site restart php) clears stale bytecode.
Bottom Line
Ember gives a small WooCommerce shop a solid foundation: PostgreSQL for concurrent writes, PHP-FPM capacity for checkout, and 12-hour backups for peace of mind. Up to around 200 products, 30-40 simultaneous visitors and 50 daily orders fit comfortably. Once you start edging past those numbers, Blaze offers the next logical step without over-engineering.
If you're building a boutique shop that expects modest traffic, Ember is the pragmatic choice. It lets you focus on product photography and marketing, while the underlying stack stays reliable and transparent. When growth pushes you beyond its limits, the upgrade path is clear and affordable.