EOL.Wiki EOL.Wiki
← ← Back to all products

ScyllaDB

Active
Databases Latest Version: 2026.1.4 Latest Release: May 26, 2026

ScyllaDB is a high-performance, low-latency NoSQL database compatible with Apache Cassandra and Amazon DynamoDB APIs.

Versions

8

Latest Version

2026.1.4

Active Support

3

EOL

5

Lifecycle Timeline

Today
2026.1
2026.1
2025.4
2025.4
2025.3
2025.3
2025.2
2025.2
2025.1
2025.1
2024.2
2024.2
2024.1
2024.1
2023.1
2023.1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2026.1Mar 17, 2026YesNo2026.1.4
Yes
Active
2025.4Dec 22, 2025YesNo2025.4.9No
Active
2025.3Sep 1, 2025NoMar 31, 20262025.3.8No
EOL
2025.2Jul 1, 2025NoDec 31, 20252025.2.0No
EOL
2025.1Apr 7, 2025YesNo2025.1.12
Yes
Active
2024.2Nov 1, 2024NoJul 31, 20252024.2.0No
EOL
2024.1Feb 1, 2024NoMar 31, 20262024.1.0
Yes
EOL
2023.1Aug 1, 2023NoApr 1, 20252023.1.0
Yes
EOL

Frequently Asked Questions

Which versions of ScyllaDB have reached end of life?
The following ScyllaDB versions have reached end of life and no longer receive security updates: 2025.3, 2025.2, 2024.2, 2024.1, 2023.1. It is recommended to upgrade to a supported version.
Is it safe to continue using ScyllaDB 2025.3?
ScyllaDB 2025.3 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of ScyllaDB?
The latest version of ScyllaDB is 2026.1.4, released in the 2026.1 release cycle.
How many versions of ScyllaDB are currently supported?
ScyllaDB currently has 3 actively supported version(s): 2026.1, 2025.4, 2025.1.
When does ScyllaDB 2026.1 reach end of life?
ScyllaDB 2026.1 does not have a specific end-of-life date announced yet.
What should I do when ScyllaDB reaches end of life?
When a ScyllaDB version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.