WordPress on WP Engine
WP Engine publishes its own guide for deploying WordPress.
PHP content management system that requires a database and persistent filesystem for uploads and plugins.
What WordPress needs.
Every host claims to run WordPress, so the claim on its own decides nothing. These are the things WordPress actually requires from the platform underneath it, and what WP Engine publishes about each. WP Engine documents 2 of the 4.
Persistent storage
Not documented
Uploads, themes and plugins are written to disk while the site is running. A host that resets the filesystem on every deploy loses them.
Managed databases
Not documented
Every post, option and user lives in MySQL. Without a managed database you are running, patching and backing one up yourself.
Storage (entry plan)
10 GB storage on the Essential plan at its cheapest capacity tier
A media library grows steadily and is almost never pruned. Disk is the cap a WordPress site reaches first.
Sources (1) →Sources ↓
- Managed Hosting Plans for WordPress | WP Engine ↗
“10 GB storage”
Read 2026-09-05 · official pricing
Monthly visits cap
25,000 visits/mo on the Essential plan at its cheapest capacity tier
Managed WordPress plans meter traffic rather than CPU, so the visit ceiling is the real size of the plan you are buying.
Sources (1) →Sources ↓
- Managed Hosting Plans for WordPress | WP Engine ↗
“25,000 visits/mo”
Read 2026-09-05 · official pricing
What WP Engine documents.
WP Engine publishes its own guide for deploying WordPress.
Environments are individual and completely separate instances of WordPress.
Sources (1) →Sources ↓
- Environments — WP Engine Support ↗
“Environments are individual and completely separate instances of WordPress.”
Read 2026-09-05 · official docs
What it costs to run there.
- When you exceed a cap
- Not throttled or cut off; billed $2 per 1,000 extra monthly visitors
- Regions
- Google Cloud: Iowa (us-central1), South Carolina (us-east1), Montreal (northamerica-northeast1), Belgium (europe-west1), London (europe-west2), Frankfurt (europe-west3), Netherlands (europe-west4), Finland (europe-north1), Taiwan (asia-east1), Tokyo (asia-northeast1), Sydney (australia-southeast1), Singapore (asia-southeast1), Tel Aviv (me-west1). AWS and Azure regions are Premium-plan only.
Sources (2) →Sources ↓
- Overage Pricing & Visitor Limits | WP Engine Support ↗
“We never throttle customers or cut their sites off for getting a traffic spike.”
Read 2026-09-05 · official docs
- Select or Change a Website's Data Center Location ↗
“Below are all of the Google datacenter locations that a WP Engine website can be located in: North America: Iowa (us-central1); North America: South Carolina (us-east1); North America: Montreal (northamerica-northeast1); Europe: Belgium (europe-west1); Europe: London (europe-west2); Europe: Frankfurt (europe-west3)*; Europe: Netherlands (europe-west4); Europe: Finland (europe-north1); Asia/Pacific: Taiwan (asia-east1)*; Asia/Pacific: Tokyo (asia-northeast1)*; Asia/Pacific: Sydney (australia-southeast1); Asia/Pacific: Singapore (asia-southeast1); Middle East: Tel Aviv (me-west1)”
Read 2026-09-05 · official docs
Whether it suits you.
WordPress teams that deploy with Git rather than SFTP — GitPush works over SSH — and want bandwidth overages handled by a conversation rather than an automatic charge on shared plans.
Consider something else if…
Scripts must finish inside 60 seconds; the execution limit can be lowered but not raised.
Visit WP Engine documentation