ArangoDB End of Life (EOL) Dates and End of Support (EOS) Dates
ArangoDB end of life (EOL) and end of support (EOS) dates: 13 ArangoDB versions have reached EOL, including ArangoDB 3.11 (EOL date: May 30, 2025) — no longer receiving security updates or patches. ArangoDB 3.12.14 is the current supported release. Also see MariaDB EOSL information for related end-of-life information.
Currently Supported ArangoDB Releases - Active EOS/EOSL Support (1)
| Release | Released | Security Support | Latest |
|---|---|---|---|
| 3.12 | (2 years and 8 months ago) | Active | 3.12.14 (2 days ago) |
ArangoDB End of Life (EOL) Releases - No Longer Supported (13)
| Release | Released | Security Support | Latest |
|---|---|---|---|
| 3.11 | (3 years and 5 months ago) | (1 year and 5 months ago) | 3.11.14.6 (1 month and 3 weeks ago) |
| 3.10 | (4 years and 1 month ago) | (2 years and 7 months ago) | 3.10.14 (2 years and 7 months ago) |
| 3.9 | (4 years and 9 months ago) | (3 years and 2 months ago) | 3.9.12 (3 years and 2 months ago) |
| 3.8 | (5 years and 4 months ago) | (3 years and 6 months ago) | 3.8.9 (3 years and 7 months ago) |
| 3.7 | (6 years and 7 months ago) | (4 years and 5 months ago) | 3.7.18 (4 years and 6 months ago) |
| 3.6 | (6 years and 10 months ago) | (5 years and 2 months ago) | 3.6.16 (5 years and 2 months ago) |
| 3.5 | (7 years and 3 months ago) | (5 years and 10 months ago) | 3.5.7 (5 years and 10 months ago) |
| 3.4 | (7 years and 11 months ago) | (6 years and 5 months ago) | 3.4.11 (6 years and 2 months ago) |
| 3.3 | (8 years and 11 months ago) | (6 years and 8 months ago) | 3.3.25 (6 years and 9 months ago) |
| 3.2 | (9 years and 4 months ago) | (7 years and 7 months ago) | 3.2.18 (7 years and 9 months ago) |
| 3.1 | (10 years ago) | — | 3.1.29 (8 years and 4 months ago) |
| 3.0 | (10 years and 4 months ago) | — | 3.0.12 (9 years and 11 months ago) |
| 2.8 | (10 years and 9 months ago) | (8 years and 5 months ago) | 2.8.11 (10 years and 4 months ago) |
Running an old build? ArangoDB end of life arrives one release at a time: once a version leaves its support window, you get no patches, even for security flaws. The current 3.12 line is supported, while 3.11 reached its end-of-life on May 30, 2025. Whether this graph database is your multimodel database for a side project or for customers, this guide shows what support each release still gets, what the policy says and how to move to the latest release before general availability dates start working against you.
ArangoDB EOL Dates by Supported Release
The table below lists each release line, when it was released for general availability, and the day its support ended. Any supported release still receives fixes, so your first check is whether your line is the one marked as supported.
| Release | Released | Support ended |
|---|---|---|
| 3.12 | March 21, 2024 | Still supported |
| 3.11 | May 30, 2023 | May 30, 2025 |
| 3.10 | October 4, 2022 | April 15, 2024 |
| 3.9 | February 15, 2022 | September 15, 2023 |
| 3.8 | July 29, 2021 | April 30, 2023 |
| 3.7 | September 16, 2020 | May 31, 2022 |
Anything older than 3.7 passed its EOL long ago, so treat those installs as unsupported and plan a full migration rather than a quick patch.
General availability to support end
Each line follows the same rhythm: general availability, then roughly one to two years of coverage, then an EOL notice. Major releases are covered for at least 18 months, and minor releases for at least 12 months from their general availability, so a minor build you installed late in its cycle can lose coverage sooner than you expect.
End-of-Life Announcements and Product Support Policy
Arango publishes every end-of-life announcements entry on its support page, usually months ahead. The notice for 3.7 even carried an advanced notice while 3.6 was still winding down, so the cutoff for the next line was announced well before it landed. The same product support policy covers only the stable release of each line, and each of the major releases follows its own clock.
The page also tracks platforms. When Ubuntu 12.04 reached its own EOL in June 2018, Arango stopped building binaries for it, which shows the rule: support follows what the upstream platform still supports as well as the database release itself. Once a line is past its date:
- You receive no patches and no further updates, including security fixes.
- The build counts as unsupported, so you can't open a support case against it.
- Your risk rises with every newly found flaw, because nobody ships a fix for your line.
ArangoDB 3.11 End-of-Life: What Changes
If you are still on 3.11, your support window closed on May 30, 2025. The database keeps running, but the practical cost shows up in production: no new fixes, and teams that must pass audits lose their footing. Arango's own guidance is blunt that staying put trades a free upgrade today for engineering time later.
Security support and compliance exposure
Without security support, a vulnerability found tomorrow stays open on your cluster. That matters for compliance: an end-of-life build is exactly what auditors working toward SOC 2 or GDPR flag, whatever SSO, encryption and audit logging controls you have around it.
Performance and availability limits
Once 3.11 is past its date, a bug in intelligent sharding, SmartGraphs, active failover or hot backups stays unfixed on your line. As datasets grow, that hurts performance and availability, and the scale you can safely reach on the retired build is capped.
Community Edition vs Enterprise Edition After EOL
Your options after a cutoff depend on which edition you run. Starting with 3.12.5, the Community Edition includes the Enterprise features with no time limit, but it is free only for non-commercial use and data up to 100 GB. A commercial use case, or anything beyond that cap, needs the Enterprise Edition and its license terms.
- Community: right for learning, testing and personal projects; the license limits embedding and combining it with enterprise code.
- Enterprise: covered by a paid agreement, with support and the production features above.
- SaaS: the managed cloud offering, where Arango runs the clusters; the SaaS terms differ from the on-premises product, which you run yourself.
Check the Enterprise license before the cutoff to decide whether a SaaS move suits you better than upgrading the on-premises product in place.
Upgrade Before ArangoDB End of Life
The safest move is to upgrade one release line at a time and rehearse on a copy of your data first. Your queries are written in AQL, the unified query language that spans JSON documents, graphs and key/value access, so most application code carries over unchanged, but read the incompatible-changes notes for each line you cross.
- Back up the data and note your current release.
- Read the release notes for every line between yours and the target.
- Restore the backup on a staging cluster and run your real AQL workload.
- Switch production once results match, then keep the backup for a rollback window.
If you want a second opinion, ask Arango for a readiness check: they review your setup and flag quick wins before you commit to a plan.
Moving to the latest release
Target the latest release, currently the 3.12 line, rather than hopping to the next older one, because each hop restarts the support clock. Put the cutoff for whichever line you land on in your calendar, so the next ArangoDB end-of-life notice never catches you off guard.