Managed WordPress hosting features: staging, CDN, SSL and limits
How managed WordPress hosting features work on a course site: staging, PHP upgrades, CDN, SSL, CPU and email limits, and what to check first.
These guides cover the hosting features you use after signup rather than the choice of host. Start with the question that is costing you time right now: an update you are nervous to push, a resource or email limit you keep hitting, or a certificate or caching problem.
If you plan changes to a live course site, read the staging and PHP upgrade guides first, because they explain how to test logins, checkout and lesson progress before anything reaches students. Then read the resource and email limit guides so you know which numbers to watch as enrollment grows.
Use the SSL and CDN guides when setting up or troubleshooting, and compare what your host documents against what your site actually needs. If a limit turns out to be the real constraint, the hosting decision guides cover when moving to a different plan or host makes sense.
Which CDN Kinsta, WP Engine and SiteGround bundle, whether it caches HTML or only static files, bandwidth terms and add-ons, and what a CDN does and does not do for logged-in lesson pages.
What SiteGround documents about CPU seconds, executions, memory, inodes and database size, why logged-in course pages use them, and a checklist for reading the usage graph before upgrading.
SiteGround's published hourly sending caps and recipient rules, set against the emails a course site sends at enrollment and during drip schedules, with a worked example of when to move transactional mail elsewhere.
A checklist built from SiteGround's knowledge base: confirm DNS, check SSL Manager, cover www, reinstall Let's Encrypt, enforce HTTPS the recommended way, fix mixed content and know when to contact support.
PHP workers, full-page and edge cache, object cache, staging, SSH/SFTP, visits and bandwidth, each matched to the label Kinsta, WP Engine and SiteGround use and what it means for logged-in students.
Why drip releases, membership expiries and renewal reminders run late on quiet course sites, how WP-Cron is triggered, and how SiteGround, Kinsta, WP Engine and a DigitalOcean Droplet each document replacing it with a server-side schedule.
What an inode is, how image sizes, cache folders, local backups, staging copies and mailboxes inflate the file count on a course site, the published inode limits for SiteGround and KnownHost plans, and how to measure and cut usage.
A cross-host table built from Kinsta's and WP Engine's published banned-plugin lists and the Liquid Web and Nexcess managed WordPress pages, flagging the caching, backup, migration, related-posts and view-counter plugins course sites often run, with each host's stated alternative.
Which of SiteGround, Kinsta, WP Engine, Liquid Web, KnownHost and DigitalOcean include mailboxes, which only relay transactional mail or block SMTP, and what a course owner should budget for mailboxes and a sending service when the host provides neither.
Which PHP versions Kinsta, WP Engine, SiteGround, Liquid Web and KnownHost document, how each handles end-of-life versions and automatic upgrades, how much notice they describe, and the php.net support dates a course site should plan around.
A developer-access table for Kinsta, WP Engine, SiteGround, Liquid Web, KnownHost and DigitalOcean: SSH and authentication, WP-CLI, Git deployment, SFTP, root access and plan restrictions, so you know before buying whether a developer's workflow will work.
The exact dashboard location, retention window and download route for PHP error and access logs at Kinsta, WP Engine, SiteGround and a DigitalOcean WordPress Droplet, with a worked example of tracing a failed checkout.
Published upload and POST size limits at WP Engine, SiteGround and Kinsta, whether each can be raised, the Cloudflare proxy cap that overrides them, and SFTP routes for large course assets.
Which hosts issue free certificates, which cover wildcard subdomains for course portals, which accept uploaded certificates, and who renews each, at Kinsta, WP Engine, SiteGround and DigitalOcean.
What Kinsta, WP Engine and SiteGround document about proxying through your own Cloudflare account, the SSL mode each expects, the conflicts with their built-in layers, and a setup order that avoids certificate and redirect loops.
A day-by-day orientation to the Site Tools sections a course owner actually uses on SiteGround (domain, SSL, backups, caching, cron, email, staging, security and resource usage) with what to check on day one and what can wait.
A tour of the MyKinsta areas that matter for a course or membership site (domains, caching, backups, staging, users, email, analytics) with the setting to confirm in each during your first week.
How sites and environments relate in the WP Engine User Portal, and the backup, cache, cron, SSL and user settings to confirm before you invite students.
What the WordPress 1-Click image installs, what its setup script does, and the firewall, backup, monitoring, mail and cron jobs you own from day one, each tied to DigitalOcean documentation.
What you control on a new KnownHost managed VPS, how WHM and cPanel divide the work, how to create a cPanel account per site, and the backup, SSL and security settings to confirm in week one.
Portal orientation, staging, backups, automatic plugin updates with Visual Comparison, and PHP workers on Liquid Web managed WordPress, sequenced for a course launch.
WordPress.org's recommended versus legacy requirements, what PHP, the database, HTTPS and the web server each do, and how to confirm them on any plan before you buy.
A minimal inbound and outbound rule set for a WordPress Droplet built from DigitalOcean documentation, the limits and defaults that surprise people, and how to avoid locking yourself or the Droplet Console out.
What Kinsta's built-in APM records, how long it runs and keeps data, its documented performance cost, and how to read a slow quiz or checkout trace to decide whether a bigger plan, more PHP memory or a code fix is the right spend.
What DevKinsta can pull from and push to Kinsta according to Kinsta's docs, what each push overwrites, and how to keep student data and live payment keys safe on a local copy of a course site.
How Local's Connect feature pushes and pulls with WP Engine production, staging and development environments, what a push overwrites, which files never move, and a safe sequence when the live site holds membership data.
A weekly, monthly, quarterly and yearly maintenance calendar for a WordPress course or membership site run by one person, covering updates, backup restore tests, PHP support dates, certificates, licenses and access reviews.
A step-by-step staging workflow for LMS, membership and checkout plugin updates, with what Kinsta, WP Engine and SiteGround document about copying, email, cron and database pushes, and a test script for enrollment and checkout.