Hand over an existing Open edX platform to Cubite: what we need from you

Short answer (updated November 17, 2026)

Cubite runs managed Open edX from $1,260 a month for up to 1,000 concurrent learners, and it can take over a platform you already run: the platform starts on the release it already runs, and bringing it current is scoped before the managed term starts. To plan the handover, Cubite needs your named release and how it is deployed, where it runs, your customizations and where their code lives, when your learners are quietest, and your peak concurrent learners. Named-release upgrades are included in every managed Open edX tier (Lean $1,260 a month, Resilient $1,850 a month, Scale from $3,400 a month), each rehearsed on a UAT environment before production.

What Cubite needs from you

Send these before the call, or bring them to it:

  • Your named release, and its patch tag if you know it. A platform Cubite takes over starts on the release it already runs, and if that release is no longer supported, bringing it current is a fixed quote agreed before the managed term starts.
  • How it is deployed today, with Tutor (and which version) or another way, and where it runs: your own cloud account, a hosting provider or your own servers.
  • Your customizations: plugins and XBlocks, your theme, micro-frontend changes and any changes to the edx-platform source, including whether the platform runs a forked edx-platform.
  • Where their code lives: the repositories that hold your Tutor configuration, plugins, theme and infrastructure code, or a note of anything that is in no repository.
  • When your learners are quietest. Each upgrade runs in the quiet window we agree with you, rehearsed first on a UAT copy of your platform, with a backup taken just before it so a rollback is ready.
  • Your peak concurrent learners, such as your busiest exam hour: managed Open edX is priced by the learners online at the same moment, not by accounts. Lean ($1,260 a month): up to 1,000 concurrent learners; Resilient ($1,850 a month): up to 2,000 concurrent learners; Scale (from $3,400 a month): elastic, scales on demand.
  • Your identity provider, if your learners sign in with SSO: SSO (SAML / OIDC) implementation is included in every tier, and your IT team does the identity provider's side.
  • If you are running a formal evaluation or an RFP, the requirements document: Cubite comes back with a scoped response.

Check your release and upgrade pathWhat managed Open edX includes, and what your team still doesSSO on managed Open edX

Can Cubite take over the Open edX platform we already run?

Yes. Cubite runs managed Open edX from $1,260 a month for up to 1,000 concurrent learners, and a platform Cubite takes over starts on the release it already runs; bringing it current is scoped before the managed term starts. Named-release upgrades are included in every managed Open edX tier (Lean $1,260 a month, Resilient $1,850 a month, Scale from $3,400 a month), each rehearsed on a UAT environment before production.

Which Open edX release will our platform run after Cubite takes it over?

A new managed Open edX platform from Cubite, on every tier from $1,260 a month, starts on the current named release (Verawood on Tutor 22, as of November 2026); a platform Cubite takes over starts on the release it already runs, and bringing it current is scoped before the managed term starts.

How named-release upgrades workEvery Open edX release and its support status

What if the Open edX platform we hand over to Cubite runs an old, unsupported release?

On managed Open edX from Cubite, bringing an inherited platform up from an unsupported release is a fixed quote agreed before the managed term starts. Open edX is upgraded one named release at a time, so a platform several releases behind passes through every release in between. After that, named-release upgrades are included in every Cubite managed Open edX tier, from $1,260 a month.

Will our theme, plugins and patches carry over when Cubite takes over our Open edX platform?

Yes: on managed Open edX from Cubite, carrying your plugins, theme and build-time patches through each release is part of the included upgrade, and new features you ask for at upgrade time are quoted in advance.

Cubite deploys every managed instance with Tutor, builds the LMS and Studio image from the upstream named release rather than a forked edx-platform, and ships customizations as plugins and a build-time patch set; micro-frontends and themes are customized per client. A platform you hand over that runs a forked edx-platform is moved onto that model at its first named-release upgrade with Cubite.

Can our Open edX platform stay in our own cloud account when Cubite takes it over?

Yes: Cubite can deploy and operate managed Open edX in your own cloud account. On Lean ($1,260 a month) and Resilient ($1,850 a month) the tier price is the same and your cloud provider bills you for the infrastructure directly, in place of the cloud resources those tiers otherwise include; on Scale (from $3,400 a month) cloud infrastructure is billed at cost either way, by Cubite as a pass-through or by your provider directly. Cubite specifies and provisions the sizing.

If we leave Cubite later, what do we keep from our Open edX platform?

Cubite's managed Open edX exit terms are written for a platform Cubite deploys. A platform Cubite takes over is either moved into your own GitHub organization at the takeover or left as it is, so agree which before the managed term starts.

The platform underneath is open source: Open edX, deployed with Tutor. For a managed Open edX platform Cubite deploys, the Tutor configuration, plugins, themes and infrastructure code are kept in your own GitHub organization from the first deploy, the container images are built from that code, and courses can be exported as OLX at any time. If you leave, you take a working system and a full export of courses and learner data, and you can hire anyone to run it. Custom deliverables built under a statement of work become yours on full payment, as the project agreement specifies (Terms of Service, section 10). Cubite's pipeline tooling stays Cubite's, licensed while you are a customer. Exit terms stated 2026-10-19.

Terms of Service

Talk to a person

Book a 30-minute call, or email amir@cubite.io.

Support

How can we help?

Send us a message and we'll get back to you shortly.

We typically respond within 24 hours