Sites, environments and installs
WP Engine's documentation defines a site as a group of up to three environments, and each environment as an individual and completely separate instance of WordPress. A site can have one environment of each type. Every environment gets a default address in the form environmentname.wpenginepowered.com, and environment names can never be changed, even after deletion, so do not name production after a temporary project.
On shared plans from Lite to Scale, only the production environment can carry a custom domain; on Premium plans any environment can. That makes production the only environment students should ever see, and staging and development places for you to break things.
| Environment | WP Engine's stated purpose | How to use it for a course site |
|---|---|---|
| Production (PRD) | Intended to be taken live | The only environment with your domain, real students and real payments |
| Staging (STG) | Testing minor changes such as plugin updates | Copy production here before every LMS, membership or payment plugin update |
| Development (DEV) | Developing larger changes such as a new theme | Build a redesigned course template or test a new LMS without touching staging |
| Sandbox site | Non-billable site with one DEV environment | A throwaway space; plans include from 1 (Lite) to 150 (Premium) |
What does not travel when you copy an environment
The Copy Environment tool pushes or pulls between any environments in the site. Several WP Engine settings are not copied: redirect rules, custom cache exclusions, SSL certificates and Nginx rules. Web rules can be duplicated separately in the portal. If you built your site on development and copy it to production, set redirects, cache exclusions and SSL on production itself and confirm them there.
Copying also overwrites. Once students are enrolling, a database copy from staging to production replaces enrolments, progress and orders recorded since the staging copy was made. Treat copies toward production as file-only unless you have a plan for the data.
Backups and restores
WP Engine makes daily backup checkpoints automatically for production, staging and development, stores them offsite on Amazon S3 in the same region, encrypts them in transit and at rest, and keeps 30 days of backups. A manual checkpoint is created from Sites > environment > Backups > Create backup. You can prepare a full or partial ZIP of any checkpoint, and the download remains available for 7 days.
Restores are destructive: files not in the chosen checkpoint are removed, and a restore can take from a few minutes to several hours depending on size and file count. To restore a backup into a different environment, use Copy environment, choose Push to, set the push type to Custom and pick the backup point. Rehearse that route in week one by restoring last night's production checkpoint into staging and logging in as a test student.
| Included in a checkpoint | Excluded from a checkpoint |
|---|---|
| WordPress core files | Temporary files such as cache and versioning files |
| Themes and plugins | Stock sample and template files |
| The database | Backup files such as .bak and snapshots, log files, and obsolete software such as timthumb |
Cache rules that matter for students
WP Engine's page cache expires after 10 minutes, and cache-control headers cannot be set below 600 seconds; anything that must be fresher needs a full exclusion. By default the cache skips wp-admin, wp-login.php, pages named cart, checkout, store or check-out, and any request carrying a cookie whose name contains wordpress_ with a value set. That last rule is what keeps logged-in WordPress users out of the cache. If WooCommerce is detected, its API paths, add-to-cart arguments and session cookie are excluded as well.
Many LMS and membership plugins use their own URLs for login, registration and account pages, and logged-out visitors on those pages do not yet have a wordpress_ cookie. Add path exclusions for them under the environment's Cache page, Cache exclusions, Add new exclusion. Rules can take 10 to 15 minutes to apply, cookie-based exclusions must be requested from Support, and the self-service option is not available on every account. WP Engine also notes that Edge Full Page Cache does not respect custom cookie exclusions, and that it may remove exclusions that harm server performance, so keep the list specific.
| Portal button | What it clears | When to use it |
|---|---|---|
| Clear all caches | Page cache, network caches, object cache if enabled, NitroPack cache | After a theme change or a content fix students must see now |
| Clear page cache | Varnish page cache only | After editing a single public sales page |
| Clear network caches | Advanced Network and GES caches including CDN; shown only when a domain is added | After replacing an image or stylesheet |
| Clear object cache | Stored query results | If settings changes do not appear; the WordPress admin Clear All Caches button does not clear it |
Cron, SSL and users
By default WordPress checks for due scheduled tasks on each page load, which WP Engine notes can make low-traffic sites miss scheduled times. WP Engine Alternate Cron instead checks every minute by requesting wp-cron.php. Enable it under the environment's Utilities page with the Alternate cron toggle; adding the DISABLE_WP_CRON line yourself does not enable it. It does not work behind custom basic-auth protection, only WP Engine's own password protection, and a 502 in the access log means a cron run took longer than 60 seconds.
WP Engine says most domains sit on its Advanced Network or Global Edge Security and get an SSL certificate installed automatically; check the SSL column on the environment's Domains page. If you need a Let's Encrypt certificate instead, open the environment's SSL page, Add certificate, Get Let's Encrypt, only after DNS points to WP Engine, and add both www and non-www because each needs its own certificate. Certificates managed by WP Engine default to Auto-Renew and Secure All URLs. Let's Encrypt certificates last 90 days and WP Engine attempts renewal 22 days before expiry, opening a ticket and emailing you if it fails.
Portal access is separate from WordPress admin access. Owners can do everything including deleting sites; Full users reach every environment; Partial users reach only the environments the Owner assigns. Invite users under Users > Account Users > Invite account user. WP Engine states its staff will never invite or create portal users, so treat any such invitation as suspicious.
Before you invite students
- Production has the custom domain, an Active certificate for www and non-www, and Secure All URLs.
- Cache exclusions added for LMS login, registration, account and checkout paths; tested logged out and logged in.
- Alternate Cron enabled on production; a renewal or drip email scheduled for the next hour actually sent.
- A manual backup checkpoint created with a description such as pre-launch.
- Last night's production checkpoint restored into staging once, to prove the route works.
- Collaborators set to Partial with only staging or development unless they must touch production.
- Redirect rules and Nginx rules recreated on production if the site was built in another environment.
Questions before you decide
Is a WP Engine site the same as a WordPress install?
No. A site is a container for up to three environments, production, staging and development, and each environment is a completely separate WordPress install with its own database, backups and settings.
How long does WP Engine keep backups?
WP Engine makes daily backup checkpoints automatically and keeps 30 days of backups. A prepared ZIP download of a checkpoint stays available for 7 days.
Are logged-in members served from WP Engine's page cache?
By default, requests with a cookie whose name contains wordpress_ are excluded from page cache, as are wp-login.php, wp-admin and pages named cart or checkout. Custom LMS paths may need their own exclusion.
Do cache exclusions copy to production with the site?
No. WP Engine lists custom cache exclusions, redirect rules, SSL certificates and Nginx rules among the settings that do not transfer when you copy an environment.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- WP Engine Support: Environments Accessed 30 Oct 2026
- WP Engine Support: Backup and restore Accessed 30 Oct 2026
- WP Engine Support: Cache Accessed 30 Oct 2026
- WP Engine Support: WP-Cron and WordPress scheduling Accessed 30 Oct 2026
- WP Engine Support: SSL Accessed 30 Oct 2026
- WP Engine Support: User Portal users Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.