Who Provides Support for Erlang/OTP 25 and 26 After End of Life?

The short answer

For Erlang/OTP 25 and 26, which the OTP team no longer patches, OSSeva publishes patched builds, along with OTP 24, and ships them as tested pairs with the RabbitMQ release each one runs. Erlang Solutions sells support plans for Erlang, Elixir, RabbitMQ, MongooseIM and EMQX, including an Extended plan for moving an Erlang/OTP environment to a new platform with tested upgrades, and says its engineers can build patches into releases. For OTP 27, 28 and 29, the OTP team's own releases are the answer, with OTP 27 supported until OTP 30 ships.

The question that usually decides it is not Erlang at all but the software running on it. Each RabbitMQ release supports a narrow band of OTP releases, so a broker you cannot upgrade pins the runtime too, and that pair needs covering together.

Which Erlang/OTP releases are supported

The Erlang/OTP security policy supports the last three OTP releases with maintenance and security patches. A new major ships each May, so each one gets about three years.

RabbitMQ 3.13 tops out at OTP 26.2.x, and 3.11 runs only on OTP 25, so many brokers sit on a runtime the OTP team no longer patches. RabbitMQ and Erlang version compatibility maps every broker release to its OTP range, the Erlang/OTP end-of-life chart tracks each release, and Erlang/OTP vulnerabilities by version lists the advisories.

Erlang/OTP support providers compared

Each row reflects what the provider publishes on its own site as of 7 October 2026.

Perforce OpenLogic, HeroDevs and TuxCare do not list Erlang/OTP among the technologies they cover.

How the providers differ

The Erlang/OTP team

If your software can run on OTP 27 or later, the OTP team's own releases are free and current, and OTP 27 is supported until OTP 30 ships. The limit is the software on top: a RabbitMQ, ejabberd or CouchDB release that does not support a newer OTP keeps you on an old one.

Erlang Solutions

Erlang Solutions is an Erlang and Elixir consultancy, and its support plans cover Erlang, Elixir, RabbitMQ, MongooseIM and EMQX. It says its engineers work closely with the OTP team on releases and can build patches directly into releases when a customer needs it, and its Extended plan is aimed at moving an existing Erlang/OTP environment to a new platform with tested upgrades. Its pages do not list patched builds of retired OTP releases, so if that is what you need, ask for it in writing. For RabbitMQ consultancy, its RabbitMQ team now trades as Seventh State. See OSSeva vs Erlang Solutions and OSSeva vs Seventh State.

OSSeva

OSSeva for Erlang/OTP ships drop-in builds of OTP 24, 25 and 26 from the same release line, so the version string your software checks does not change. Patch covers the TLS, SSH, public_key and crypto applications, with matched RabbitMQ and OTP build pairs tested together, signed artifacts and OS packages, and CVE disclosure notifications. Assure adds a compatibility matrix for your broker estate, a TLS and cipher suite audit, a distribution protocol and cookie review and a staged OTP upgrade plan with rollback. Operate adds 24/7 scheduler, memory and process monitoring, a 15-minute P1 response, a named Erlang engineer, crash dump forensics and rolling OTP upgrades, and patches Critical CVEs (CVSS 9.0 and above) within 48 hours and High within 7 days. The patched builds also cover Elixir applications on the same runtime. Erlang/OTP coverage is priced per cluster and is included with OSSeva for RabbitMQ.

How to choose

Moving RabbitMQ from OTP 26 to 27 covers the most common runtime move, and broker and runtime pairing covers why the two move together.

Where OSSeva fits

OSSeva covers the OTP releases the OTP team has retired, paired with the RabbitMQ releases that run on them. RabbitMQ support providers covers the broker side, and RabbitMQ 3.13 on Erlang 26 covers the most common pairing.

Frequently asked questions

Who provides extended support for Erlang/OTP 26?

OSSeva publishes patched OTP 26 builds, tested with the RabbitMQ releases that run on it. OTP 26 left community support when OTP 29 shipped in May 2026, and its last patch release was 26.2.5.21. Erlang Solutions sells Erlang support plans but does not list patched builds of retired OTP releases.

Is Erlang/OTP 25 still supported?

No. The OTP team supports only the last three releases, now OTP 29, 28 and 27, so OTP 25 has had no patches since 2025. OSSeva publishes patched OTP 25 builds, which RabbitMQ 3.11 needs.

Which companies offer commercial Erlang/OTP support?

Erlang Solutions sells support plans for Erlang, Elixir, RabbitMQ, MongooseIM and EMQX. OSSeva ships patched OTP 24, 25 and 26 builds with optional 24/7 operations. The OTP team supports the last three releases in the open.

Do I need to patch Erlang if RabbitMQ is up to date?

Yes. TLS, SSH, public_key and crypto come from OTP, not from RabbitMQ, so a current broker on an unpatched runtime is still exposed. Since RabbitMQ 3.13 cannot run on a supported OTP release, its runtime needs a separate patch source.

Can I upgrade Erlang without upgrading RabbitMQ?

Only within the OTP range your RabbitMQ release supports. The compatibility guide lists each range, and outside it the broker has to move first.