Camunda 7 end of maintenance per version: Community Edition ended, Enterprise to April 2030

Camunda 7 keeps running. For the Enterprise Edition, maintenance of version 7.24 LTS ends in April 2030. After that, Camunda offers extended support until April 2032, for an additional fee and on request through your assigned Customer Success Manager. For the Community Edition, it ended in October 2025. Its final release, 7.24, came out on 14 October 2025, the day Camunda had announced for it and the day Maven Central’s version index for the engine was last updated, and Camunda has published no Community Edition release since, security patches included.

The difference between the two editions is the whole point, and most of the confusion comes from leaving it out. Camunda’s own migration page puts it this way: “Camunda 7 Enterprise Edition remains supported through April 2030, but we recommend all new projects be developed on Camunda 8.” (camunda.com/platform-7/migrate, checked 19 October 2026.)

Camunda 7 Community Edition and Enterprise Edition: which one has reached end of life?

The Community Edition has. The Enterprise Edition has a published date in April 2030. Anyone who says Camunda 7 has reached end of life without naming the edition can be refuted in one click.

On 28 February 2025 Camunda announced that it was extending the end of life of the Camunda 7 Enterprise Edition (Camunda blog). In its own words: “To give our customers greater flexibility in migrating to Camunda 8, we are extending the Camunda 7 Enterprise Edition EoL from April 2027 to April 2030.” Nothing changed for the Community Edition that day. The same post says: “The EoL date for Camunda 7 Community Edition has not changed.”

In practice that means two things. With a paid Enterprise subscription on 7.24 LTS, you have maintenance until April 2030 and a paid option on request after that. On the Community Edition, you have received nothing since 14 October 2025: no bug fix and no security patch. The Community Edition repository on GitHub is archived (checked 19 October 2026), and the artefact org.camunda.bpm:camunda-engine:7.24.0 on Maven Central carries the note: “7.24.0 is the last community edition release published on Maven Central. This library will not receive any new versions or releases.” The Maven Central version list for that artefact still ends at 7.24.0.

A dated example. On 9 October 2026 Camunda published Security Notice 171 for Camunda 7, covering CVE-2026-76183 and CVE-2026-77226. Under “How to determine if the installation is affected” it says: “You use the following Camunda 7 versions or lower: 7.24.15.” As the release that contains the fix it names “Camunda 7: 7.24.16.”, an Enterprise patch release. The notice states no severity. In the US National Vulnerability Database (NVD), both records read “Awaiting Analysis”, and the only CVSS 3.1 scores come from scorers NVD lists as secondary: 9.8 (CRITICAL) from CISA-ADP for CVE-2026-76183, and 8.1 (HIGH) from VulnCheck for CVE-2026-77226, which VulnCheck also scores 9.2 (CRITICAL) under CVSS 4.0, again as secondary.

The fix ships in a patch release, and Camunda’s Release Policy says patch releases are available to Enterprise customers only. From the notice’s version line, the Release Policy and Maven Central, where the Community Edition stops at 7.24.0, we draw a conclusion Camunda itself never states: a Community Edition installation on 7.24.0 falls inside the notice’s version line, and Camunda delivers no fix to it. The security notices page says in general: “Fixes are available as patches to the enterprise platform and alpha or minor releases of the community platform.” No Community Edition release of any kind has appeared after 7.24.0 (all checked 19 October 2026).

The software itself keeps running through all of this. Camunda defines end of maintenance narrowly, and its definition mentions no licence expiry. If someone tells you your processes will stop on a set date, they are wrong.

When does each Camunda 7 version reach end of maintenance?

This is what Camunda’s Support Announcements page says (docs.camunda.org/enterprise/announcement). The release dates there are worded as “scheduled for”, so Camunda gives the planned date and the page does not confirm that the release happened that day. The end of maintenance lines carry no such qualifier.

An Enterprise contract does not extend the individual minor versions. Only 7.24 LTS runs to 2030, and only on the Enterprise Edition. Every older 7.x line has its own date under Camunda’s standard support period (“The announced end of maintenance dates are based on our standard support period of 18 months.”), and 7.24 LTS is the one exception to that rule. A subscriber on 7.23 or 7.22 receives no further Enterprise patches for that version after its end of maintenance date. The route back into maintenance that Camunda provides is a version upgrade to 7.24 LTS within Camunda 7. Your support contract stays in place: Camunda writes that support is included in the subscription until April 2030.

What exactly does “end of maintenance” mean at Camunda?

Camunda defines it on the same page: “End of maintenance means that Camunda will not perform any maintenance or release any bug fixes and patch releases related to the mentioned version after the specified date.”

That is the entire definition, and what it leaves out matters most in this whole topic. It covers maintenance, bug fixes and Enterprise patch releases for the named version. It says nothing about Camunda 7 ceasing to work, licences expiring, binaries being withdrawn or documentation going offline.

So the question an end of maintenance date puts to you is a security and operations question: who delivers fixes for your installation once Camunda stops delivering them for your version.

What did Camunda announce, and when?

Camunda’s announcements run from March 2024 to October 2026, and several of the original posts were revised later while their visible date stayed the same. Here is the sequence, citing each source as it reads today.

Two traps sit in this list. First, the 2024 forum post still shows its original date, yet it was revised in July 2025, so the text you read there today is a later text. Second, the second forum thread dates from the same day as the blog post. The May date the page displays belongs to the automatic closing notice. Anyone who turns that into “Camunda confirmed it again months later” is quoting a system message.

Why do so many pages still show an end date in 2027?

Because it was correct once. Until 28 February 2025 the Enterprise Edition had an earlier date, and Camunda replaced it that day. The sentence that replaced it is quoted above, and it names both dates in one breath, the old and the new.

A page written before that day and left untouched since still carries the old date. We name none of them here. An outdated date on a consultancy page takes one line to fix, and it is usually an honest oversight.

A second source of confusion sits on Camunda’s own page. Cawemo On-Premises, a different product, has its own date listed there in the same year. Skim the page and it is easy to take away the wrong one.

The reliable check is quick: open docs.camunda.org/enterprise/announcement, find the heading for your version and read its “End of Maintenance” line. What it says there is what holds. Everything else, this article included, is a restatement.

Why does Camunda name two different days in April 2030?

Because Camunda’s two sources disagree, and we say so here and pick neither. For Camunda 7.24 LTS the documentation gives “End of Maintenance: 13th of April 2030 (Extended Support until April 2032)”. The blog post of 28 February 2025 gives the Enterprise Edition end of life as “New EoL Date: April 9, 2030.”

They may describe two different things: an end of life for the whole edition, and the end of maintenance for one minor version. Camunda has never related the two figures to each other. The gap does not change any plan. So we write “April 2030” everywhere, with no day, and a day appears only inside Camunda’s own words.

Extended support also needs a careful reading. Camunda says it costs extra and runs from April 2030 to April 2032, and the documentation adds: “If you require Camunda Extended Support, contact your assigned Customer Success Manager.” No source promises it to any given customer, and Camunda publishes no price for it.

Where can you migrate, and what speaks against each option?

Five targets hold up against the sources. For each there is either a documented Camunda 7 path or a documented reason why there is none. The column that matters is the last one.

The sentence that changes most project plans is in Camunda’s own migration guide (Camunda 7 to Camunda 8 migration guide): “It is important to understand that Camunda 8 is not a drop-in replacement for Camunda 7.” And on the architecture, on the next page of the guide (Conceptual differences): “the workflow engine in Camunda 8, Zeebe, is always a remote resource for your application, while the embedded engine mode is not supported.” If your application embeds the engine as a Java library and shares a transaction with it, the move means rebuilding part of your application.

Camunda also wrote this, and it is rarely quoted (Migration-ready solutions): “Those hacks are the real showstoppers for migration, as they cannot be migrated to Camunda 8.” The hacks in question are casts to implementation classes, ThreadLocals and Spring beans behind JUEL expressions.

On the tooling, Camunda’s migration tools overview adds a sentence worth keeping next to any plan: “Neither path guarantees lower token use, cost, or migration time.” The Code Conversion page calls Camunda 8 “a complete rewrite of Camunda 7”.

What changed in October 2026?

Two things, on different days. The first is the Environment Update Release for 7.24 LTS, which Camunda had announced with only a month and no day. Its block on the announcements page now reads “Release Date: October 8th, 2026” and “Patch Version: 7.24.16”. Version 7.24.16 is a patch release, and patch releases are available to Enterprise customers only; the Patch Level Update Guide adds that “they are not available in the community edition”. For Enterprise installations, the block lists five end of support lines:

• Java 11 (“End of Support Java 11”)
• Quarkus 3.33 LTS (“End of Support Quarkus 3.33 LTS”)
• Spring 6 (“End of Support Spring 6”)
• Spring Boot 3.5 (“End of Support Spring Boot 3.5”)
• MariaDB 10.6 (“End of Support MariaDB 10.6”)

On 19 October 2026 the 7.24 supported environments page still lists Java 11 and MariaDB 10.6, and Camunda does not reconcile the two pages. If your estate runs on one of the five, read both pages and ask your Camunda support contact which applies to you. On the additions side the block lists Java 25, Spring Boot 4.1, WildFly Application Server 41, JBoss EAP 8.1, Quarkus 3.40 LTS, PostgreSQL 19 and Jackson 3. Several of these reached Enterprise customers by patch before October, according to the Patch Level Update Guide: Java 25 compatibility came with Enterprise patch 7.24.9, Camunda Run and the Camunda Spring Boot Starter moved to Spring Boot 4.1.0 with Enterprise patch 7.24.10, and JBoss EAP 8.1 support came with Enterprise patch 7.24.11. The guide’s section for Enterprise patch 7.24.16 covers support for WildFly 41, the Quarkus extension on Quarkus 3.40.1, and opt-in support for Jackson 3. Under “Support for PostgreSQL 19” the block still carries the sub-item “Delivery might be pushed into November if released too late”, and the supported environments page lists PostgreSQL 15, 16, 17 and 18 (both checked 19 October 2026).

The second is the end of maintenance for Camunda 7.23 in October 2026. Since then, 7.24 LTS is the only Camunda 7 line still in maintenance. The effect is smaller than it sounds: for an Enterprise estate on 7.23, the answer Camunda provides is a version upgrade to 7.24 LTS. The newest section of the Patch Level Update Guide, which covers Enterprise patch releases, is headed “7.24.16 / 7.23.18 Oct/2026”.

What we sell, and why this article argues against it

We sell Camunda 7 migrations. Read what follows with that in mind.

The most honest sentence in this article works against that business: for an Enterprise estate on 7.24 LTS, no date before April 2030 forces a migration. Camunda keeps shipping Enterprise patch releases, keeps certifying new environments for the Enterprise Edition and says itself that Camunda 7 Enterprise Edition remains supported through April 2030. Anyone selling you urgency for that case is selling you a date Camunda has not published.

Two cases look different, and you can establish both from your own estate. First, you run the Community Edition: then you have received no security patches since October 2025. Second, you run a version below 7.24: then Camunda already delivers nothing for your version. Both describe a state that already exists.

We have deliberately given no figure for the effort, duration or cost of a migration in this article. The Camunda sources quoted here give no such figure for a whole migration, and we publish no number we cannot source.

If you are not yet sure which of the two products you run, What is Camunda? tells Camunda 7 and Camunda 8 apart in a few checks.

If you would rather read first on your own: the handbook The Camunda PATH works through the same decision, with five credible paths and thirteen candidates it rules out.