Managed LMS Hosting Built for Course Sites That Actually Scale

It depends on which of two models you pick. A managed xCloud server is one price for the server and the panel together. Self-managed is two line items: a per-server xCloud fee, and your own cloud server billed by whoever you host it with. A small course site runs comfortably on an entry-level 2 GB server; a few hundred concurrent students wants 4 GB or more. Nothing is metered per student, per visit or per site, so the cost of a successful launch is a server resize rather than a new invoice tier.

Concurrency is what matters, not total enrolment, because only the students actually logged in cost you anything. The limits are PHP workers and database throughput, both of which follow the size of the server. A 2 GB server is fine for a small cohort, 4 GB and up comfortably carries a few hundred students working at once, and past that you resize rather than migrate. Object caching is what moves that ceiling furthest, which is why it is on by default.

Yes. Each site on the server is isolated with its own database, its own PHP pool and its own SSL, so a LearnDash site and a Tutor LMS site can sit side by side, along with the rest of your WordPress LMS hosting, without sharing anything but the hardware. Sizing is the only real consideration: two busy course sites want the same headroom two busy course sites would want anywhere.

Yes. The built-in migration brings files and database across together, and Migrate Guru works if you prefer to run it from inside WordPress. Student records, course progress and enrolments all live in the database, so they arrive intact. You verify the copy on a temporary domain first and point DNS only when you are satisfied, which is how a cutover happens without interrupting a cohort mid-lesson.

You can, and you should not. Video is a long-running, bandwidth-heavy request, and every stream competes for the same workers and disk your lesson pages need, so one popular module can slow the whole site for everyone. Put video on Bunny Stream, Vimeo or object storage and embed it, then let the CDN carry the rest of the course assets. The server then spends its capacity on the part only it can do, which is the LMS itself.

Sometimes, for a while. A handful of students working through pre-recorded lessons will not trouble a decent shared plan. It stops being enough at the first launch, because the load arrives all at once and every one of those requests is authenticated and uncacheable. If your course sells in cohorts rather than trickling, the shared plan will fail on exactly the day it matters most.

Yes. Moodle deploys from the one-click library and is managed the same way as any WordPress site here, including staging, backups and real system cron. It is standalone PHP rather than a WordPress plugin, so it gets its own data directory and cache paths configured for it. Cheap Moodle hosting usually means shared PHP with no cron and no staging, which is precisely what breaks a Moodle upgrade.

Any of them. LearnDash, Tutor LMS, LifterLMS, MasterStudy and Sensei all run on the managed WordPress stack, Moodle runs standalone, and anything else built on PHP, Node.js or Docker deploys here too, so a headless or self-built LMS platform is not a special case. Pick the LMS on its features. The hosting requirements underneath are the same either way.