Your best engineers should be building the business, not maintaining the framework under it.
Axon Framework 4 end of life
long-term support (LTS)
Axon Framework 4 (AF4) reached end of support on June 30, 2026. Your systems didn't stop, but the patches did. Keeping AF4 in step with an ecosystem that keeps moving becomes your team's to carry, and it's the kind of work that quietly pulls your most senior people off the roadmap. Long-Term Support puts that maintenance back on the people who build Axon Framework, so your engineers stay on what moves your business.
License
Axon Framework is Apache 2.0. No change
Track record
90M+ downloads, in production since 2009
What actually changed on Axon Framework 4 on June 30, 2026
Decide what's best for your organization, based on the facts.
🤚🏼
What ended for AF4
Security patches
New CVEs affecting AF4 will not be fixed by the maintainers.
Bug fixes
Defects found in AF4 won't be corrected upstream.
Maintenance releases
No further AF4 point releases or dependency bumps.
Ecosystem upkeep
As Spring and other libraries evolve, keeping AF4 compatible is now on your team, not the maintainers.
🥳�🏼
What did not change
The code is still yours
Axon Framework stays open source under Apache 2.0. Nothing was revoked or discontinued.
Your systems keep running
AF4 doesn't stop working; it stops being maintained.
Your options stay open
Your systems keep running. Your exposure doesn't. Every day without LTS, your team owns triage for CVEs we've stopped patching.
Commercial support is available, not required
LTS is one path. The point is that it's your decision.
A framework doesn't wear out, but the world around it is changing.
Unlike hardware, a framework doesn't degrade with use. What changes is everything it depends on; Spring, the JDK, transitive libraries, the CVE feed. Staying on AF4 means someone has to keep it updated. When maintenance ended upstream, that someone became your team.
Maintaining it yourself
Compatibility gaps don't get fixed by junior engineers. They land on the two or three people who know your Axon internals best, the same people you'd rather have shipping features. It rarely looks like a project, it's a steady drip of dependency bumps, security triage, and "why did this break after the Spring upgrade." It's work that's invisible until it isn't, and it competes directly with your roadmap.
Handing it to the people who built it
LTS moves that upkeep to the engineers who maintain Axon Framework. New vulnerabilities get assessed and patched against the version you run; compatibility is kept current for you. Your senior engineers get their time back for the work that actually differentiates your product, and you get depth of knowledge that's hard to keep in-house when one or two people carry it.

Case study
->
Read how we helped accelerate engineering velocity at a major U.S. grocery retailer, freeing the team from maintaining infrastructure so they could focus on building features.
01
Time-to-market slips
As senior engineers get pulled into maintenance instead of features.
02
Ecosystem drift
Library updates that quietly break things and have to be chased.
03
Security triage
For new CVEs, now backported by hand instead of by the maintainers.
04
When it's over, it's over.
When the deep framework knowledge lives with certain engineers.
The car analogy
Most teams could, in principle, maintain the framework themselves. The same way most people could learn to service their own car. Almost nobody does, because the point of a car is to get somewhere quickly, and not to become a mechanic. Your engineers are most valuable working on your business, not maintaining the ecosystem underneath it.

What you're actually buying with long-term support
LTS is the maintenance and expertise that stopped upstream, put back in place by the people who build Axon Framework, for the version you already run in production.
Security patches for AF4
New vulnerabilities assessed and fixed, so you're not hand-backporting CVEs.
Ecosystem compatibility
AF4 kept in step as Spring, the JDK, and dependencies move on.
Critical bug fixes
Defects that threaten correctness or stability, fixed against the version you run.
Access to the experts
A named path to engineers who know the framework internals.
Audit-ready documentation
A documented compensating control you can hand an assessor.
Room to decide
Cover through June 2027, so any future change is planned, not a fire drill.
Talk to the team about AF4 LTS
Tell us where AF4 lives in your stack and we'll walk through what LTS would cover for your environment.