Who Provides Extended Support for Apache Camel 3 and Camel 4 LTS?

The short answer

For Camel 3, which Apache stopped releasing at the end of 2024, OSSeva publishes patched builds of the 3.14 and 3.20 LTS lines, along with Camel 2.25 and the expired 4.4 and 4.8 LTS lines. Red Hat no longer supports Camel 3: its Camel for Spring Boot 3.20 product ended on 30 September 2024. For Camel 4, Red Hat supports its own build of Apache Camel 4 until 30 October 2029, while Perforce OpenLogic and meshIQ sell support contracts for community Camel.

The difference that matters is whether a provider ships new security fixes for the exact line you run, or helps you run it and upgrade. Red Hat ships fixes for its latest Camel 4 release only. OSSeva ships them for lines Apache has retired.

Which Camel versions Apache still supports

Camel's download page says LTS releases get bug and security fixes "for a longer time - up to one year", and it lists only the supported releases. Everything else sits in the release archive.

Two supported lines at a time, each for about a year, means a Camel estate falls out of support within twelve months of its last upgrade. The Camel end-of-life chart tracks every line, and Camel vulnerabilities by version shows which advisories reach the retired ones.

Apache Camel support providers compared

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

One row needs reading closely. Red Hat's policy is that defect and security fixes go only to the latest minor or micro release, so a Red Hat subscription keeps you current on Red Hat's Camel 4 stream rather than keeping an older line alive. HeroDevs is not in the table: its current support catalogue lists no Camel product.

How the providers differ

Red Hat

Red Hat is the strongest choice for Camel 4 when you can follow its release stream. Its build of Apache Camel 4 now has one life cycle across Spring Boot and Quarkus, with full support until 30 October 2028. Red Hat aims for a new minor about every six months, usually aligned to an upstream LTS: the Spring Boot variant shipped 4.18.4 on 24 September 2026, and the Quarkus variant ships on Camel 4.18.3. That window is far longer than Apache's one year, as long as you keep moving to Red Hat's latest release. Red Hat's Camel 3 products, Camel for Spring Boot 3.14 to 3.20 and Camel K 1.x, have all ended, and Fuse 7 on Camel 2 is in paid extended life phases until June 2027.

Perforce OpenLogic

OpenLogic lists Apache Camel among more than 400 supported technologies at all three support levels and runs a Camel training course. Its long-term support product, which supplies patched builds after end of life, does not include Camel. Our OSSeva vs OpenLogic comparison covers the wider overlap.

meshIQ

meshIQ sells Camel 4.x support together with ActiveMQ and Artemis, which suits estates where the routes and the brokers are one system. It does not publish Camel 2 or 3 coverage.

OSSeva

OSSeva for Apache Camel backports security fixes onto the LTS line your routes were written against, so a Camel 3 estate is not forced into the javax to jakarta rewrite by a security deadline. Patching covers the components in use, including the third-party libraries they bundle, and the swap is a BOM change with component coordinates unchanged. Camel Spring Boot pins a Spring Boot line, and OSSeva covers both sides under the same engagement. Assure adds a route and component inventory, a Jakarta migration impact assessment and a staged upgrade plan; Operate adds 24/7 route monitoring, a 15-minute P1 response and migration execution. Pricing is per application estate, not per route.

How to choose

Camel 3 to 4 changes every javax import and raises the Java baseline to 17. Our Camel 3 to 4 migration guide covers the steps, and Camel 3 Jakarta migration covers running the move alongside extended support.

Where OSSeva fits

OSSeva covers the Camel lines Apache has retired, 2.25, 3.14, 3.20, 4.4 and 4.8, and will cover 4.18 when it leaves upstream support, with signed artifacts through your repository manager. It can also cover the Spring Boot and ActiveMQ releases those routes depend on. See the extended support vendor roundup for how OSSeva compares across other technologies.

Frequently asked questions

Who provides extended support for Apache Camel 3?

OSSeva publishes patched builds for the Camel 3.14 and 3.20 LTS lines. Apache ended Camel 3 at the end of 2024, and Red Hat's Camel 3 products have also ended, the last on 30 September 2024. OpenLogic sells general Camel support, but Camel is not on its patched long-term support list.

Who supports Camel 4 LTS for longer than a year?

Red Hat, for its own build of Apache Camel 4, with full support to 30 October 2028 and maintenance to 30 October 2029, provided you stay on its latest release. OSSeva patches Camel 4 LTS lines after Apache retires them, today 4.4 and 4.8, and 4.18 from February 2027.

Is Camel 3 still supported?

Not by Apache. The Camel team declared Camel 3 end of life at the end of 2024, and 3.22.4 in March 2025 was the last release. Only Camel 4.22 and 4.18 LTS are supported upstream.

Does Red Hat still support Camel 3 or Fuse?

Not Camel 3: Red Hat's Camel for Spring Boot 3.20 ended on 30 September 2024 and Camel K 1.10 on 30 June 2025. Fuse 7 left maintenance on 30 June 2024, and its paid extended life phases run to 30 June 2027.

Does HeroDevs cover Apache Camel?

Its current support catalogue does not list Camel. Ask HeroDevs directly if you were quoted Camel coverage before.

Should we upgrade to Camel 4 or buy extended support for Camel 3?

Upgrade the applications whose routes, Spring Boot version and tests can move to Jakarta now. Buy extended support for the rest, with a migration date recorded for each, so the security exposure does not set the migration schedule.