The signal most teams ignore until it’s too late
The first sign is usually the same across organizations: a course launch that coincides with a performance drop. Or an academic director asking for a completion report nobody can generate accurately. Or a weekend when the platform goes down right when enrollment is peaking.
None of these episodes mean the platform was built wrong. They mean the program grew faster than the infrastructure supporting it. This is the point where the question stops being “how do I launch my platform?” and becomes “what Open edX® hosting can handle a program that already has sustained, active enrollment?”
Edunext Cloud Growth is edunext’s answer to that turning point: a middle ground between a basic setup and an enterprise-grade operation, with the reliability, performance, and operational support a growing program needs.
What changes from the entry-level tier
EC Growth keeps the same Open edX® foundation — LMS and Studio on the latest official release — but adds Aspects, Open edX®’s analytics engine, to the software package. That gives the academic and operations team real visibility into user behavior on the platform, something that tends to become essential once a program moves past the pilot stage and starts reporting to a board or a client.
On the open source enablers side, EC Growth adds soft multitenancy to the options already available at the entry level (EOX and composable theming), allowing the organization to run multiple sites or brands within a single installation with more operational flexibility. The architecture keeps the same dedicated, Tutor-compatible Kubernetes namespace, but the high-availability databases now include Clickhouse alongside MongoDB and MySQL — the engine needed to sustain the volume of analytics data Aspects generates.
More capacity, with room for spikes
Compute managed by edunext goes from 25 to 40 GB of RAM and from 20 to 30 vCPU, with a quota calibrated to support up to 150 concurrent users for no more than 20% of the time, equivalent to roughly 2,500 monthly active users. That’s a direct jump in capacity compared to the entry tier, built for programs that already run sustained active enrollment rather than one-off launches.
Unlike the entry-level tier, EC Growth allows compute to expand beyond the included quota whenever the academic calendar demands it: additional compute available at 500 USD per month for each extra block of 50 GB of RAM and 40 vCPU. That option gives the program room to absorb enrollment spikes, mass course launches, or one-time campaigns without forcing a mid-cycle product migration.
Less time exposed if something breaks
The availability SLA rises to 99.5%, with proactive monitoring, availability reports, and service credits for SLA breaches. Standard security protections — encryption in transit via TLS 1.2+, encryption at rest via KMS, secret management through vault — are joined by vulnerability management aligned with Open edX® best practices.
Daily backups are retained for 60 days, with recovery time (RTO) and recovery point (RPO) objectives of 24 hours each — half the time of the entry-level tier. That shrinks the exposure window after any incident and speeds up service restoration if it’s ever needed.
For programs that need to validate changes before pushing them to production on a recurring basis, EC Growth offers the option of a permanent staging environment in an independent namespace for an additional 5,000 USD per year, on top of the temporary environment already available during every upgrade.
A support team built for more than isolated incidents
Priority technical support in EC Growth includes 15 tickets per year, with response times under 48 hours during 8×5 business hours, in addition to permanent access to the knowledge base and AI-powered responses available 24×7. Onboarding includes a one-hour live training session, geared toward teams that already have experience running the platform but need to bring new staff or new areas of the organization up to speed.
How do you know your program needs EC Growth?
The signals tend to show up together: usage analytics has become a decision-making tool rather than a nice-to-have, service availability now directly affects daily operations, and user volume produces spikes the entry-level quota no longer absorbs comfortably. Growing university programs, companies running active corporate training across multiple departments, or education initiatives managing several cohorts at once tend to find in EC Growth the right balance between capacity and cost.
Moving to EC Growth doesn’t mean changing architecture or provider: it’s a natural extension of the same Open edX® foundation, with more capacity, more data, and more operational support to sustain growth without friction.
Frequently asked questions
How do I know if my Open edX® platform needs more capacity?
The most common signals are performance drops during launches, unreliable analytics reporting, and enrollment spikes that exceed the contracted compute quota. EC Growth is built to address all three at once.
What is Aspects and why do I need it?
Aspects is Open edX®’s official analytics engine. It generates usage, progress, and course-completion reports based on real platform data.
Can I scale compute without switching plans?
Yes. EC Growth allows on-demand additional compute at 500 USD per month for each block of 50 GB of RAM and 40 vCPU, without needing to move up to a higher-tier product.
How long does it take to recover the platform after a failure on EC Growth?
The recovery time objective (RTO) is 24 hours — half the time defined for the entry-level EC Core tier.
