Open edX Hosting: The Complete Guide (2026)

Open edX Hosting: The Complete Guide to Self-Hosted, Managed & SaaS Options (2026)

Cubite sells managed Open edX; competitor prices below are copied from each provider's public page on September 30, 2026.

Short answer (September 30, 2026): Cubite runs managed Open edX from $1,260 a month for up to 1,000 concurrent learners, with cloud resources included; its Resilient tier costs $1,850 a month for up to 2,000, and its Scale tier runs on Kubernetes from $3,400 a month, with cloud billed at cost. The table below shows the other providers' prices where we could read them on their own sites on September 30, 2026: OpenCraft, Raccoon Gang and Abstract Technology, each with its source. Self-hosting with Tutor has no license fee, but you pay for the cloud and for the engineer who runs every upgrade.

Open edX powers 2,283+ live sites and serves over 100 million learners — from Harvard and MIT to NVIDIA and NASA. The software is free. Running it is not.

Open edX hosting is the single decision that determines your platform's cost, uptime, security, and how painful every upgrade will be for years to come. Get it right and you have a scalable learning platform that grows with your organization. Get it wrong and you're burning $50,000+/year on infrastructure and DevOps salaries before a single learner logs in.

Managed option: Cubite runs managed self-hosted Open edX from $1,260/mo, all-in, load-tested to 1,000 concurrent learners, including SSO, SCORM, xAPI and LTI, branding, and cloud resources. See managed Open edX or book a call.

This guide is the comparison we wished existed when we started hosting Open edX platforms: published prices with their sources, honest tradeoffs, and a framework to help you decide.

Here's what you'll find:

• Three hosting paths compared side-by-side (self-hosted, managed, SaaS)
• Published prices with sources and dates, not "contact us" black boxes
• A total cost of ownership breakdown updated for 2026
• A decision framework matched to your org type, budget, and team

What Is Open edX — And Why Does Hosting Matter?

Open edX is the open-source learning management system originally built by Harvard and MIT to power edX. Today it's maintained by Axim Collaborative and a community of 1,334 contributors. The platform grows at 18% year-over-year, with 207+ million course enrollments worldwide. New to the platform? Our What Is Open edX? overview and Open edX review (42 verified users) are good starting points.

Free is the reason organizations choose Open edX. Hosting complexity is the reason many of them struggle.

Unlike Moodle's single-server LAMP stack, Open edX runs a distributed microservices architecture. A production deployment requires seven coordinated services running simultaneously:

That's seven services to deploy, monitor, patch, back up, and scale. Every one is a potential point of failure. This is why the hosting decision matters more for Open edX than for almost any other LMS.

Open edX Hosting Options: Self-Hosted vs Managed vs SaaS

Every Open edX deployment falls into one of three categories. Here's what each actually means — not the marketing version, but the operational realit

The short version: Self-hosting gives you maximum control at maximum cost and complexity. Open edX cloud hosting through a managed provider gives you the scalability of AWS or GCP without the ops burden. SaaS gives you speed at the expense of flexibility. Managed hosting is the middle ground — and where most organizations land.

Let's look at what each path really involves.

Before reading further, take 30 seconds to assess where your organization stands:

Evaluate your team and situation against these criteria:

If 4-5 checked: Self-hosting may actually make sense for you. Read the next section carefully to confirm your team can handle the 9 operational challenges. If 2-3 checked: Managed hosting with a BYOC (bring your own cloud) option is likely your sweet spot. You get control where it matters without the full ops burden. If 0-1 checked: Managed hosting or SaaS is your path. Skip the self-hosting section if you want — or read it to understand what you're paying your provider to handle.

Self-Hosting Open edX: What It Really Takes

Self-hosting means you own everything: the servers, the deployment, the upgrades, the 3 AM alerts when MongoDB runs out of disk space. Here's the unvarnished picture.

Server Requirements

Tutor, the only officially supported deployment tool since the Maple release, lists these minimum requirements:

Those minimums are deceptive. For a production deployment serving ~300 active users, community members report needing 16 GB RAM for the application server plus separate VMs for MySQL (8 GB), MongoDB (8 GB), and a reverse proxy (8 GB). That's 40 GB of RAM across four servers — for 300 users.

A single Tutor instance tops out at roughly 1,500 active users. Beyond that, you need to separate MySQL, MongoDB, Redis, and Elasticsearch onto dedicated services and scale the application tier horizontally, with more application nodes behind a load balancer or with Kubernetes.

For Open edX AWS hosting, most self-hosted deployments use EC2 instances for compute, RDS for MySQL, DocumentDB or self-managed MongoDB, and ElastiCache for Redis, and you pay that cloud bill on top of the engineer who manages it. Cubite's Lean ($1,260) and Resilient ($1,850) prices include cloud resources; its Scale tier bills cloud at cost.

Deployment: Tutor Is Your Only Option

The legacy Ansible-based installer (edx-configuration) was officially archived in May 2024. If you're still running it, you're on unsupported infrastructure.

Tutor (maintained by Edly) provides two deployment modes:

• tutor local: Docker Compose on a single server. Good for small deployments and development.
• tutor k8s: Kubernetes deployment, for horizontal scaling across nodes. Cubite's Resilient tier serves up to 2,000 concurrent learners on two application nodes behind a load balancer for $1,850 a month; Kubernetes is only in its Scale tier, from $3,400 a month.

This gets you a local development instance. Production deployment requires DNS configuration, SSL certificates, SMTP setup, and significantly more infrastructure planning. See the Tutor docs for the full production checklist.

The 9 Self-Hosting Challenges

Based on eduNEXT's analysis and community forum discussions:

1. Complex multi-service architecture — Not a single app, but seven coordinated services
2. Incomplete documentation — Official docs assume significant prior expertise and aren't always current
3. Infrastructure design decisions — AWS vs GCP vs Azure, instance sizing, networking, storage architecture
4. Customization complexity — Theming, branding, and XBlock configuration require deep platform knowledge
5. Upgrade pain — The recommended approach is backup, destroy the server, and rebuild. Skipping versions creates complex migration paths with deprecated dependencies
6. Scaling architecture — Each service (MySQL, MongoDB, Redis, Elasticsearch) needs its own HA configuration as you grow
7. Security responsibility — Continuous audits, credential management, encryption, data privacy compliance
8. Monitoring and alerting — You need New Relic, Datadog, or equivalent — plus someone watching the dashboards
9. Ongoing maintenance: biannual named releases (currently Verawood, released on July 30, 2026; Ulmo is no longer supported) each require migration work

Most organizations find that managed hosting costs less than a single DevOps engineer's salary — while delivering better uptime, faster upgrades, and zero 3 AM pages.

Quiz: Self-Hosting Reality Check

Open edX Hosting Providers Compared (2026)

Cubite is one of the providers in this Open edX hosting comparison and publishes it, so every provider price in the table below comes from the provider's own page, with the date it was checked. openedx.org's installation and hosting directory lists 44 providers (checked September 30, 2026); the table below covers the ones in this guide.

Published Open edX hosting prices (checked September 30, 2026)

Cubite prices managed Open edX by capacity tier, not per learner: $1,260 a month covers up to 1,000 concurrent learners. See every tier on Cubite pricing, the service on managed Open edX, and the side-by-side Open edX provider comparison.

What to Look For in a Provider

Not all providers are equal. openedx.org's installation and hosting directory shows provider experience ranging up to 10+ years. Here's what matters:

Must-haves:

• Named release upgrade track record — Ask how many upgrades they've completed and what their process looks like
• Core contributor status — Providers who contribute to the Open edX codebase understand it at a deeper level
• SLA with specific uptime numbers — "High availability" is marketing. "99.9% with 30-second health checks" is an SLA
• Data ownership terms — Your data should be fully yours, exportable at any time, in standard formats
• Transparent pricing — If a provider won't show pricing, ask yourself why

Red flags:

• No public pricing and no ballpark range on request
• No clear upgrade path or release cadence
• Vendor lock-in terms that make migration difficult
• Less than 4 years of Open edX-specific experience
• No references or case studies from similar organizations

What Managed Hosting Providers Actually Handle

If you've read the self-hosting section and thought "I don't want to deal with any of that" — this is what you're paying for with managed hosting.

A good managed Open edX hosting provider handles:

• Automatic upgrades: named releases arrive twice a year (Verawood is current; Willow is scheduled for December 2026). Your provider migrates you, tests compatibility, and handles rollbacks if needed
• 24/7 monitoring — Services checked every 30 seconds with automatic escalation.
• Automated backups — Daily snapshots with point-in-time recovery and disaster recovery testing
• Custom theming — Your brand's colors, logos, and layouts applied without touching code.
• XBlock management — Installing, configuring, and testing plugins (SCORM, LTI, drag-and-drop, peer assessment) for compatibility with each release
• SSO integration — SAML 2.0, OAuth, LDAP, and Shibboleth configured and maintained.
• Auto-scaling infrastructure — Traffic spikes from enrollment periods, exam windows, or course launches handled automatically
• Security and compliance — Encryption at rest and in transit, regional data hosting options, regular security patches applied within hours of release
• Full data ownership — Your data stays yours. Export it anytime in standard formats

What you focus on instead: Course content, learner engagement, instructional design, and organizational strategy. The stuff that actually moves the needle.

How to Choose the Right Open edX Hosting for Your Organization

Stop asking "which provider is best?" and start asking "which hosting path fits my organization?" Here's a decision framework based on org type:

5 Questions to Ask Every Provider

Before signing a contract, ask these:

1. "How many Open edX upgrades have you managed, and what's your rollback process?" — This separates experienced providers from newcomers
2. "Do you contribute to the Open edX codebase?" — Core contributors understand the platform at a deeper level and can fix issues upstream
3. "What's your SLA, and what happens when you miss it?" — Get specific numbers: uptime percentage, response time guarantees, and financial penalties for breaches
4. "Can I export all my data at any time in standard formats?" — The answer should be an immediate yes with no conditions
5. "What happens if I want to switch providers or go self-hosted?" — A confident provider will help you migrate. A lock-in-dependent provider will make it difficult

Open edX vs Moodle: Hosting Compared

If you're still deciding between Open edX and Moodle, this LMS hosting comparison covers the differences that actually matter — architecture, resource requirements, and cost For the full Moodle side of the decision, see the Moodle hosting guide.

Choose Open edX if: You need to scale to thousands of concurrent learners, require rich multimedia and interactive content (XBlocks), want a modern microservices architecture, or are building an EdTech product on top of the platform.

Choose Moodle if: You need a simpler setup, have a smaller deployment (<5,000 users), want lower hosting costs, or your use case is traditional course-based education without heavy multimedia.

Either way: Managed hosting makes more sense than self-hosting for most organizations in both ecosystems.

Quiz: Are You Ready to Choose?

Frequently Asked Questions

How much does managed Open edX hosting from Cubite cost?

Cubite offers managed self-hosted Open edX from $1,260/mo, all-in, load-tested to 1,000 concurrent learners, with SSO, SCORM, xAPI, LTI, branding and cloud resources included. Resilient ($1,850 a month) adds a second application node behind a load balancer for up to 2,000 concurrent learners, and Scale (from $3,400 a month) runs on Kubernetes with cloud billed at cost.

How much does it cost to host Open edX?

The total cost depends on three factors: your number of active learners, required features (SSO, custom theming, analytics), and whether you self-host or use a managed provider. Self-hosted TCO (total cost of ownership) reaches $50,000-200,000+/year when you factor in infrastructure, a DevOps engineer, monitoring tools, and the opportunity cost of maintenance. Most organizations under 2,000 active users find managed hosting significantly cheaper.

Can Open edX be self-hosted?

Yes, Open edX is open-source and can be self-hosted using Tutor, the official Docker-based deployment tool. You'll need at minimum 8 GB RAM and 4 CPU cores. However, self-hosting requires DevOps expertise in Docker, Kubernetes, MySQL, MongoDB, and Linux — making managed hosting more practical for most organizations.

Self-hosting gives you complete control over your infrastructure, data, and customization. The tradeoff is significant operational responsibility: you handle upgrades (twice yearly), security patches, backups, scaling, and monitoring. The legacy Ansible-based installer was archived in May 2024, so Tutor is your only supported path. For organizations with an existing DevOps team and 20,000+ active users, self-hosting can be cost-effective. For everyone else, the math favors managed hosting.

What are the server requirements for Open edX?

Open edX requires minimum 4 GB RAM and 2 CPU cores for development, but production deployments need 8-16 GB RAM, 4+ CPU cores, and 25+ GB storage. The stack includes Django, MySQL, MongoDB, Elasticsearch, Redis, and Celery. Beyond 1,500 active users, you'll need to separate database layers onto dedicated servers.

The official Tutor documentation lists 4 GB/2 CPU as the absolute minimum — but that's for development only. Community reports suggest production deployments serving 300+ active users need 16 GB RAM for the application server, plus separate instances for MySQL (8 GB), MongoDB (8 GB), and a reverse proxy. A single-server deployment caps at roughly 1,500 active users; beyond that you scale the application tier horizontally, with more application nodes behind a load balancer or with Kubernetes.

Is Open edX free to use?

Open edX software is free and open-source under the AGPL license. However, running it requires server infrastructure, DevOps expertise, and ongoing maintenance.

Think of it like WordPress: the software is free, but you still need hosting, a domain, themes, plugins, and someone to maintain it all. Open edX's infrastructure requirements are significantly higher than WordPress, which is why the "free" label can be misleading. You're not paying for a software license — you're paying for the expertise and infrastructure to run a complex distributed system reliably.

What is Tutor for Open edX?

Tutor is the official, community-supported deployment tool for Open edX. It uses Docker containers to package and run all Open edX components. Since the Maple release, Tutor replaced the legacy Ansible-based installer as the sole supported deployment method. It supports both single-server (Docker Compose) and Kubernetes deployments.

Tutor is maintained by Edly and adopted as the official Open edX deployment method via OEP-45. It simplifies deployment by containerizing all services, but "simplified" is relative — you still need Docker, DNS, SSL, and SMTP expertise for production. Tutor's plugin system allows extensions (SCORM, Kubernetes, MFE customization), and it's how managed hosting providers deploy their instances too.

How do I upgrade Open edX?

Upgrading Open edX with Tutor involves pulling the latest images and running migration commands. However, skipping versions creates complex migration paths with deprecated dependencies and database changes. Managed hosting providers handle upgrades automatically, which is one of their strongest value propositions — eliminating downtime risk and migration headaches.

Open edX releases two named versions a year. The current release is Verawood: Verawood.1 shipped on July 30, 2026, later than its date on the release schedule, and Ulmo (January 2026) is now listed as unsupported. Each upgrade requires database migrations, plugin compatibility checks, and potentially theme updates. The recommended upgrade approach for self-hosted instances is to back up all data, tear down the old environment, and deploy fresh — then restore data. This carries real downtime and failure risk, which is why upgrade management is one of the top reasons organizations choose managed hosting.

Who uses Open edX?

Open edX powers 2,283+ live sites serving 100+ million learners. Users include Harvard, MIT, and Western Governors University in education; NVIDIA, Tesla, Cisco, and McKinsey in enterprise training; and NASA, the US DoD, and UK Cabinet Office in government. The platform grows 18% year-over-year.

The platform spans every sector: higher education, corporate training, government, and NGOs. Recent developments include a partnership with India's National Skill Development Corporation (NSDC) and growing AI integration — Axim's 2025 Impact Report notes that over 50% of new partnerships feature AI as a central component. The next Open edX Conference (2026) is hosted by Western Governors University in Salt Lake City.

Open edX vs Moodle: which is better for hosting?

Open edX excels at scale (built for millions of learners) with modern microservices architecture, but requires significantly more hosting resources (8+ GB RAM vs Moodle's basic LAMP stack). Moodle is simpler to self-host. For large-scale deployments with rich multimedia content, Open edX's architecture is superior. For smaller deployments, Moodle hosting is simpler and cheaper.

The right choice depends on your scale and needs. Open edX's distributed architecture (Django, MySQL, MongoDB, Elasticsearch, Redis, Celery) is heavier to host but built for massive concurrency. Moodle's monolithic PHP stack is easier and cheaper to run but hits scaling limits sooner. Both have healthy managed hosting ecosystems. If you're serving under 5,000 users with traditional course-based content, Moodle is simpler. If you need rich interactive content, XBlock extensibility, and enterprise-grade scaling, Open edX is worth the additional hosting investment.

The Bottom Line

Open edX is a world-class LMS trusted by the most demanding organizations on the planet. But it's also a complex distributed system that requires serious infrastructure commitment.

Here's what to remember:

• Self-hosting costs add up once you account for infrastructure AND staff.
• Cubite's managed Open edX starts at $1,260 a month; the lowest published price for a managed instance in the table is EUR 599 a month (Abstract Technology's Standalone Server, ex VAT).
• SaaS options trade customization and control for a faster launch
• The provider you choose matters — look for core contributor status, transparent pricing, named release upgrade track records, and clear data ownership terms
• Tutor is the only supported deployment method — any provider or article recommending Ansible-based deployment is outdated

The question isn't whether you can afford managed hosting. It's whether you can afford not to.