DataStax Enterprise End of Support: Your Options Before 31 December 2027

IBM lists end of support for DataStax Enterprise (DSE) 6.x as 31 December 2027, when it moves to Extended Support, which runs to 31 December 2031. You have three options: stay on DSE inside that window, move to DataStax's Hyper-Converged Database (HCD), or move to Apache Cassandra. Which one fits depends mostly on whether anything in your estate uses DSE Search, Analytics or Graph. The dates below were checked on 4 November 2026.

DSE is IBM's product now, and the calendar is IBM's. If you run a Cassandra ring on DSE and want the operating picture across all three paths, AceMQ's Apache Cassandra consulting and support covers DSE as well as open source Cassandra.

One operational change already happened. From January 2026, DataStax's public repositories no longer carry DSE tarballs or packages. They come from IBM Fix Central, which needs an IBMid with multi-factor authentication, and package installs need a local mirror of what you downloaded. If your build or node replacement process pulls from a public repository, it has already broken or will on the next rebuild.

Nothing changes in the application, and IBM's dates give you until the end of 2027 for standard support and four more years of Extended Support. The costs are quieter ones: no new DSE orders, a package mirror to maintain, and a decision postponed to a year when more of your team has moved on. Staying is a reasonable answer for a ring that is stable and whose application is itself due to be retired. It is a poor answer if the plan is simply to hope.

DataStax's migration page for HCD 1.2 recommends a cross-cluster migration with its ZDM tools, which allow blue-green deployments and rollback, and offers an in-place upgrade only if ZDM cannot be used. The same page lists what HCD does not support, and each item is work to finish before you move:

• DSE Search, DSE Analytics and DSE Graph, which must be migrated off first or you risk data loss and application failures.
• COMPACT STORAGE tables, which stop HCD 1.2 from starting until they are converted to standard CQL tables.
• DSE Management Services, which must be disabled.
• Kerberos-only authentication, which needs another scheme added first.
• DSE-only drivers, which are end of life and need replacing.

We did not find HCD's own support dates in the pages we checked, so ask for them in writing before you treat HCD as the long-term answer.

Apache Cassandra is Apache 2.0 licensed. The project's download page lists 5.0.9 as the latest GA release, 4.1.12 as the previous stable and 4.0.21 as the older stable, all three released on 7 August 2026. The project ties maintenance to future majors (5.0 until 8.0, 4.1 until 7.0, 4.0 until 6.0) and publishes no calendar end-of-life dates, so you plan from release notes, not a date.

The catch is the same list as above. Apache Cassandra ships none of the DSE-only workloads, so a table that feeds DSE Search or a Spark job on DSE Analytics needs a replacement before the data moves. For plain CQL tables the usual path is a rehearsed cross-cluster move to 4.1 or 5.0: a new ring, dual writes or a bulk copy, validation, and a cutover with a rollback. A platform change and a version change should not share one production window, so a DSE ring on an old release is upgraded first or moved in a separate step.

1. Does any keyspace feed DSE Search, DSE Analytics or DSE Graph?
2. Do any tables use COMPACT STORAGE?
3. Do you authenticate with Kerberos only, or use a DSE-only driver?
4. Which DSE release and fix level do you run today?
5. How long will the application live? If it retires before 2031, staying may be the cheapest path.
6. Who operates the ring, and what happens to that rota during a migration?

Answering them takes an inventory of keyspaces, tables, drivers and workloads, which is where a written assessment starts. AceMQ is an independent provider: it is not a partner or reseller of IBM or DataStax and gives no licensing advice. What AceMQ can do is operate the ring through the move with managed Cassandra on your infrastructure or ours, or cover it with 24/7 Cassandra support while your team does the migration. For how support providers compare, see Cassandra support options.

• IBM Support, IBM DataStax Enterprise 6.x lifecycle page (ibm.com/support/pages/ibm-datastax-enterprise6x), page updated 13 February 2026, read 4 November 2026.
• DataStax documentation, DSE 6.9 downloads and migration notice (docs.datastax.com/en/dse/6.9/installing/downloads-migration.html), read 4 November 2026.
• DataStax documentation, Hyper-Converged Database 1.2, migrate from DSE 6.8 (docs.datastax.com/en/hyper-converged-database/1.2/migrate/dse-68-to-hcd-12.html), read 4 November 2026.
• Apache Cassandra download page (cassandra.apache.org/_/download.html) and the project's LICENSE file, read 4 November 2026.