Understand the technology behind WordPress hosting.
Practical explanations of hosting, caching, recovery, security and developer workflows — written to help you make informed decisions.
EXPLORE THE GUIDES
Understand how the WordPress stack works.
Practical explanations of the infrastructure, application and development workflows behind a modern WordPress platform.
01 · PERFORMANCE
Page Cache vs Object Cache vs OPcache vs DB Cache
See where Nginx page cache, Redis object cache, PHP OPcache and database caching sit in a WordPress request, what work each layer avoids, and why they complement rather than replace one another.
Understand when you need a temporary way to reach a site and when you need a genuinely isolated working copy, including staging safeguards, refreshes, snapshots and production deployment.
Follow a request through DNS, Nginx, Apache, PHP-FPM, WordPress, Redis and MySQL, understand what each layer does, and see where common hosting failures appear.
Understand what actually changes when WordPress moves from shared to dedicated resources, which problems dedicated hosting can solve, and when a site or agency portfolio has outgrown a shared resource boundary.
Understand how files, databases, snapshots, retention and off-site copies work together, and why a successful backup job is not the same thing as a proven recovery plan.
See what each developer tool actually provides, how they work together and why useful site-level access does not require unrestricted server administration.
Build and validate the destination before cutover using preview access or local resolution, then choose a controlled DNS or IP-takeover strategy when the new site is ready.
Work from the request path and evidence to separate cache, PHP, plugin, database, external-service and infrastructure problems before changing production.
The public resources are deliberately separated so product reference, troubleshooting guidance, customer support and live service state do not become mixed together.
Good operational guidance should help you understand what the platform is doing, make the smallest safe change and retain a recovery path when the change is significant.
UNDERSTANDRead the product behaviourDocumentation explains the control, its boundaries and the safeguards around it.
ACTFollow the task workflowKnowledge Base entry points take you to the relevant steps for the job or symptom.
ESCALATEBring useful contextWhen support is needed, include scope, timestamps, exact errors and what changed beforehand.
NEED HELP?
Use the customer portal for support.
Existing customers can keep technical requests and replies together in the support portal. For a new deployment, migration or architecture discussion, talk to a Webcore engineer.