The plan ceiling keeps being crossed
Bots, uptime pingers and image hotlinking count toward billable visits alongside real humans. Overage charges show up on the next invoice.
Visit count brought under the cap
Working with WP Engine?
Most WP Engine accounts that reach us are either paying overage charges every month, locked out of a plugin the platform disallows, or trying to move on or off and finding neither side is as straightforward as the sales pitch suggested. We look at the actual constraint and work the problem from there.
What it is
WP Engine, Inc. is a managed hosting platform built specifically for WordPress, founded in 2010 in Austin, Texas, and now majority-owned by the private equity firm Silver Lake. It covers everything a WordPress install needs on the operational side: automatic core updates, a page cache layer, dev, staging and production environments, Git push, an SSH Gateway, a bundled CDN, and daily backups kept in off-platform storage.
Over the years the company has absorbed several well-known pieces of the WordPress ecosystem. StudioPress and its Genesis Framework came in during 2018, Flywheel and the Local development tool followed in 2019, and Faust.js plus the Atlas product now cover headless WordPress deployments. Since 2024 WP Engine has been involved in a widely reported dispute with Automattic over access to WordPress.org resources, which in practice has affected how customers update plugins and themes.
The honest version
No technology is all upside. This is where WP Engine earns its place and where it tends to cause trouble.
Sound familiar?
The WP Engine problems that bring people to us, and what you have once each one is fixed.
Bots, uptime pingers and image hotlinking count toward billable visits alongside real humans. Overage charges show up on the next invoice.
Visit count brought under the cap
WP Engine disables plugins it considers redundant or risky. Usually there is a platform feature doing the same job, but the switch is not automatic.
Equivalent set up and verified
An older theme or plugin that only works on PHP 7.4, with an auto-upgrade date already on the calendar.
Code brought up to a supported version
The firewall catches a Gutenberg save, a form builder submission or a WooCommerce call, and the editor sees a 500 with no explanation.
Rule tuned, admin working again
Large database, LargeFS-stored media, and DNS that was pointed before the staging push finished running.
Cutover completed, mail still routing
A migration from an old CMS brings thousands of redirects that the per-site platform cap refuses to store.
Rules split between platform and edge
The User Portal, billing and the environment are all in someone else's login. Nothing can be changed until ownership moves.
Account and billing in your name
What we do
Call us for one blocked plugin, or hand us the whole platform decision.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. We rehearse the move on a staging copy first, bring the database and uploads across, and only point DNS once the new side is verified against the old one. Mail is handled separately because WP Engine does not host mailboxes, so if the current provider does both we pick a mail destination as part of the plan rather than after the fact.
Analytics only counts browsers that run JavaScript. WP Engine counts every request that reaches the origin and is not already a known static asset, which includes search engine crawlers, uptime monitors, feed readers and the hotlinked image traffic other sites pull from yours. The gap is usually explained once you compare server logs against the dashboard.
Routinely. The portal account, billing contact and SSH keys all need to be transferred into your name, and the previous developer's access revoked once the handover is complete. We handle the WP Engine support side of the transfer and leave you with an environment you actually control.
The platform-level web application firewall is deliberately strict, and it occasionally flags legitimate admin-ajax, REST API or form submission requests as attacks. The fix is normally a targeted rule exception requested through support, backed by a log line showing the specific rule ID that fired.
For most of our clients the answer has been to stay put and watch, because leaving a working host mid-dispute costs more than it saves. If plugin updates or logins through WordPress.org actually stop working for you, that calculus changes and we would plan a move. We will give you our read on your specific setup rather than a blanket recommendation.
Estimates are free. Share the install URL and a short note on what is going wrong, and you get a plan and a price before anything is touched.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: