Every database administrator and developer faces this question at some point: “How long will my current database version be supported?” This is especially crucial for ArangoDB users, as understanding the end-of-life (EOL) schedule for each version is essential for maintaining system security and stability.
1. What is ArangoDB? – The Power of Multi-Model Architecture
ArangoDB is an innovative multi-model database developed by ArangoDB Inc. in Germany. Its key strength lies in supporting three data models—graphs, JSON documents, and key-value pairs—through a single database core.
ArangoDB uses a unified query language called AQL (ArangoDB Query Language) to handle various data access patterns within a single query. As a NoSQL database, it uses RocksDB as its storage engine and is primarily written in C++ to ensure predictable performance while avoiding garbage collection-related performance degradation.
2. Understanding ArangoDB’s Support Policy – Foundation for Strategic Upgrades
Understanding ArangoDB’s support policy is the first step toward stable system operations. ArangoDB guarantees a minimum support period of 18 months for major releases and 12 months for minor releases.
Core Support Policy Principles
- Major Releases: Minimum 18 months of support
- Minor Releases: Minimum 12 months of support
- Notification Method: Advance notice through the official EOL notice page
- Enterprise Edition: Extended support available through individual agreements
This policy is designed to provide users with sufficient time to migrate to newer versions.
3. Current Support Status – September 2025 Update
As of September 2025, ArangoDB 3.12 is the actively supported latest version. Version 3.12 was released on March 21, 2024, and has been receiving continuous updates and security support for approximately 18 months.
Current Support Situation
✅ ArangoDB 3.12 – Currently Recommended Version
- Released: March 21, 2024
- Current Status: Actively supported
- Latest Patch: 3.12.5.2
- EOL Schedule: Not yet officially announced
❌ ArangoDB 3.11 and Earlier – End of Support
- 3.11: EOL completed on May 30, 2025
- 3.10: EOL completed on April 15, 2024
- Earlier versions: All EOL completed
Latest Patch Version Status (September 2025)
| Major Version | Latest Patch | Status | Recommended Action |
|---|---|---|---|
| 3.12 | 3.12.5.2 | ✅ Supported | Maintain latest version |
| 3.11 | 3.11.14.1 | ❌ EOL Complete | Immediate upgrade to 3.12 |
| 3.10 | 3.10.14 | ❌ EOL Complete | Immediate upgrade to 3.12 |
| 3.9 | 3.9.12 | ❌ EOL Complete | Immediate upgrade to 3.12 |
Recommendations:
- 3.12 users: Continue stable operations by updating to the latest patch version (3.12.5.2)
- 3.11 and earlier users: Immediate upgrade to 3.12 required due to security risks
Current Status Summary (September 2025)
| Status | Version | Latest Patch | EOL Date | Support Status |
|---|---|---|---|---|
| ✅ Supported | 3.12 | 3.12.5.2 | TBA | Active Support |
| ❌ EOL Complete | 3.11 | 3.11.14.1 | May 30, 2025 | Support ended |
| ❌ EOL Complete | 3.10 | 3.10.14 | April 15, 2024 | Support ended |
| ❌ EOL Complete | 3.9 | 3.9.12 | September 15, 2023 | Support ended |
Current Recommendations:
- 3.12 users: You’re using the actively supported latest version—continue normal operations
- 3.11 and earlier users: Security risks exist due to ended support—immediate upgrade to 3.12 required
4. Complete Version Support Schedule – Comprehensive EOL Timeline
Here’s a detailed support schedule for all released ArangoDB versions. This information is based on the official ArangoDB EOL notice page.
Major Version 3.x Series – Complete Support Schedule
| Version | Release Date | EOL Date | Latest Patch | Support Duration | Status |
|---|---|---|---|---|---|
| 3.12 | March 21, 2024 | TBA | 3.12.5.2 | 18+ months | ✅ Currently Supported |
| 3.11 | May 30, 2023 | May 30, 2025 | 3.11.14.1 | 24 months | ❌ Support Ended |
| 3.10 | October 4, 2022 | April 15, 2024 | 3.10.14 | 18 months | ❌ Support ended |
| 3.9 | February 15, 2022 | September 15, 2023 | 3.9.12 | 19 months | ❌ Support ended |
| 3.8 | July 29, 2021 | April 30, 2023 | 3.8.9 | 21 months | ❌ Support ended |
| 3.7 | September 16, 2020 | May 31, 2022 | 3.7.18 | 20 months | ❌ Support ended |
| 3.6 | January 2020 | August 31, 2021 | 3.6.16 | 20 months | ❌ Support ended |
| 3.5 | August 21, 2019 | December 31, 2020 | 3.5.7 | 16 months | ❌ Support ended |
| 3.4 | December 6, 2018 | June 21, 2020 | 3.4.11 | 18 months | ❌ Support ended |
| 3.3 | December 14, 2017 | February 29, 2020 | 3.3.25 | 26 months | ❌ Support ended |
| 3.2 | July 20, 2017 | March 31, 2019 | 3.2.18 | 20 months | ❌ Support ended |
| 3.1 | February 2017 | Mid-2018 | 3.1.29 | ~18 months | ❌ Support ended |
| 3.0 | April 2016 | End of 2017 | 3.0.12 | ~20 months | ❌ Support ended |
Legacy Version 2.x Series
| Version | Release Date | EOL Date | Latest Patch | Support Duration | Status |
|---|---|---|---|---|---|
| 2.8 | January 25, 2016 | June 15, 2018 | 2.8.x | 28 months | ❌ Support ended |
Platform-Specific EOL Information
| Platform | EOL Date | Notes |
|---|---|---|
| Ubuntu 12.04 | June 15, 2018 | Binary builds discontinued due to platform EOL |
Note: Official EOL schedules for versions prior to 2.8 (2.7, 2.6, 2.5, etc.) are not documented and accurate information is unavailable.
5. Key Changes in Version 3.12 – Essential Information Before Upgrading
If you’re considering upgrading to version 3.12, there are several important changes you should be aware of.
Major Changes in Community Edition
Starting with version 3.12.5, the Community Edition shares the same codebase as the Enterprise Edition, making all core Enterprise features available. However, there are the following restrictions:
New Limitations:
- License Restriction: Cannot be used for commercial purposes
- Database Size Limit: 100GB total limit
- Technical Support: No technical support available for Community Edition users
Newly Available Features:
- OneShard (single shard clusters)
- SmartGraphs
- Backup functionality
- All other Enterprise features
Security and Performance Improvements
Version 3.12 includes security enhancements such as improved memory tracking, compression, query logging, and cluster connectivity checks. It also adds Vector Indexes, essential for GenAI applications and AI-powered search.
6. Upgrade Planning Guide – Step-by-Step Migration Strategy
Here’s a step-by-step guide for safe and efficient upgrades.
Step 1: Current Situation Assessment
System Information Check
- Verify current ArangoDB version: Dashboard > System Information in the web interface
- Analyze database size and structure
- Document currently used features
Step 2: Compatibility Review
Critical Checks:
- AQL query compatibility in application code
- Driver version verification
- Cluster configuration review if applicable
Step 3: Backup and Testing
Essential Preparations:
- Create complete database backup
- Simulate upgrade in test environment
- Establish rollback plan
Step 4: Execute Upgrade
Recommended Procedure:
- Enter maintenance mode
- Create final backup
- Stop ArangoDB service
- Install new version and migrate data
- Restart service and verify functionality
7. Risks of Using EOL Versions – Security and Stability Perspective
Continuing to use end-of-life versions exposes you to serious risks.
Security Risks
- No Security Patches: Cannot fix newly discovered vulnerabilities
- Compliance Issues: Many security standards require supported software
- Data Breach Risk: Known vulnerabilities in old versions can be exploited
Operational Risks
- No Technical Support: Difficult to get official help when problems occur
- Performance Degradation: Cannot use latest optimization features
- Compatibility Issues: Increasing difficulty integrating with other systems
8. Conclusion – The Importance of Systematic Version Management
ArangoDB’s established end-of-life policy is designed to provide users with sufficient time to migrate to the latest versions. As of September 2025, ArangoDB 3.12 is operating as the actively supported latest version.
Current Recommendations by Version
| Current Version | Risk Level | Recommended Action |
|---|---|---|
| 3.12 | 🟢 Safe | Maintain latest patch version, regular updates |
| 3.11 and earlier | 🔴 High | Immediate upgrade to 3.12 required |
Key Recommendations
- Current 3.12 users: Maintain latest patch version (3.12.5.2) as you’re receiving stable support
- Current 3.11 and earlier users: Immediate upgrade to 3.12 due to security risks from ended support
- All users: Regular monitoring of the official ArangoDB EOL notice page
- Enterprise users: Consult with technical support team for extended support options if needed
Continuous Management Strategy
ArangoDB maintains a support policy of minimum 18 months for major releases and 12 months for minor releases, allowing sufficient time for upgrade planning. We recommend maintaining a secure and stable environment through regular version checks and planned upgrades.
For detailed upgrade guides, visit the official ArangoDB documentation. Enterprise customers can contact the technical support team for customized migration assistance.