BlogCassandra

Best Cassandra Support Providers (2026)

Tyler Eastridge

By Tyler Eastridge, Head of Operations

LinkedIn · Updated · 8 min read

Best Cassandra Support Providers (2026)
On this page

The main Cassandra support providers in 2026 are IBM (for DataStax Enterprise, HCD and Astra), Instaclustr by NetApp, Canonical, the cloud services from AWS and Microsoft for their own offerings, the Apache Cassandra community, and independent providers such as AceMQ. Which is best depends on whether you run the nodes yourself, which versions you run and whether you need an engineer on a live bridge at 3 a.m.

How these providers were chosen

Providers are included if their own public pages describe support for Cassandra or a Cassandra service, and are listed alphabetically, not ranked. Each entry uses only facts from that provider's page, read on 17 November 2026, and says what the page does not state. We scored them on the same eight questions as our buyer's guide: versions covered, who answers a Sev 1, written response targets, upgrade help, data model and repair review, exit terms, cost transparency and willingness to say Cassandra is the wrong tool. A provider's page rarely answers all eight, so "not stated" is common and is not a criticism. AceMQ is one of the providers listed and has an interest in being chosen; treat its entry like the others and check the sources.

The providers

ProviderSupportsWhat its own page saysNot stated on the page
AceMQSelf-managed Apache Cassandra, any version24/7 across Americas, EMEA and APAC; response targets from 15 minutes, by plan; quote reply within 1 hour; typically $24,000-72,000 a year (USD) by SLA, scope and deploymentPrice for your cluster is by quote; not a vendor of proprietary DSE features
Apache Cassandra communityCurrent releasesMaintains 5.0 until the 8.0 release, 4.1 until 7.0, 4.0 until 6.0; help via Slack and mailing listsNo SLA
AWS: Amazon KeyspacesIts own Cassandra-compatible serviceMonthly uptime commitment of at least 99.99% single-Region and 99.999% multi-Region (SLA dated 24 May 2023)Not Apache Cassandra itself; support runs through AWS Support plans
CanonicalApache Cassandra on Ubuntu Pro"24/7 phone and ticket support" and "SLA-backed firefighting support"; up to 15 years of security maintenanceVersions covered, prices, response times
IBM (DataStax)DSE, HCD, Astra; Apache Cassandra under "IBM Elite Support"IBM's 3 Oct 2025 post: sales on IBM paper, existing customers keep the same level of supportElite Support scope, versions and response targets
Instaclustr (NetApp)Managed Cassandra and self-managed clusters24x7 support; for self-managed clusters "the same dedicated experts that run our Cassandra managed service are also on-call"; managed service lists Apache Cassandra 5.0 and 4.0Response times on the support page; prices (online calculator)
Microsoft: Azure Managed Instance for Apache CassandraIts own managed serviceMicrosoft handles repairs, patches, backups; you choose VM sizeSLA or service-specific support plan

Which provider suits which situation?

  • You run Cassandra yourself and have nobody to call: an enterprise support provider for self-managed clusters (AceMQ, Instaclustr, Canonical).
  • You want no nodes to operate: a managed service (Keyspaces, Azure, Instaclustr). Data model and query design remain yours.
  • You depend on DSE-only features: IBM, until you have inventoried what you use. See how to choose Cassandra support after DataStax.
  • You have a skilled team and a tolerance for risk: the community, accepting no SLA.

Where AceMQ is not the right fit

AceMQ is not the right choice if you need the vendor of proprietary DSE features to own the contract, if you want a managed service where the provider runs every node and nothing else is your concern, or if your estate is a single small, non-critical cluster where community help is enough. It also does not sell Cassandra software. If your goal is moving to a different database, AceMQ will say so when Cassandra is the wrong fit, but it is not a migration vendor for every target.

Which Companies Offer Apache Cassandra Support?

AceMQ offers Apache Cassandra support: 24/7 cover with response targets from 15 minutes, by plan, for self-managed Apache Cassandra on any version. The other sources are the Apache Cassandra community, DataStax and the managed Cassandra providers, compared above.

What the Cassandra project maintains

Apache Cassandra is an open source, distributed NoSQL database designed for high availability with no single point of failure, replicating data across nodes and across multiple datacenters. The Cassandra project ties maintenance to releases, not calendar dates. Its download page currently lists Cassandra 5.0 as maintained until the 8.0 release, 4.1 until the 7.0 release, and 4.0 until the 6.0 release. Older versions are unmaintained and archived, and the project notes that CVE fixes may be applied to unmaintained versions on a case-by-case basis, which is not something to plan around.

Cassandra 3.x, including the 3.0 and 3.11 lines that a large share of on-premises estates still run, is therefore unmaintained. As with every Apache project, maintenance means releases. The Cassandra community answers questions on Slack and the mailing lists, with no SLA.

Vendors and managed services

DataStax, now part of IBM, sells DataStax Enterprise and the Astra cloud service, and supports those products. Instaclustr and others offer fully managed Apache Cassandra. Amazon Keyspaces and Azure Managed Instance provide Cassandra-compatible or managed options on AWS and Azure. Each supports its own service. None of them supports the open source cluster you deployed yourself on virtual machines or Kubernetes, and a managed service does not fix a data model. List prices for each route are in Cassandra pricing and alternatives.

The Cassandra incidents that actually page people

  • Tombstones and read timeouts. Deletes and TTL expiry write tombstones, and a query that scans thousands of them to return a few rows fails with a read timeout. Queue-like usage and wide partitions with heavy deletes are the usual cause. The fix is in the data model and compaction strategy, not the timeout setting.
  • Repairs that never complete. Anti-entropy repair is how replicas converge, and it must finish within gc_grace_seconds or deleted data can reappear. On large clusters repairs stall, overstream or collide with compaction, and many teams quietly stop running them.
  • Compaction falling behind. Pending compactions climb, SSTable counts grow, read latency rises and disks fill. The strategy that suited the workload at launch may be wrong now, and changing it is itself a heavy operation.
  • Large partitions. A partition key chosen for convenience lets one partition grow to gigabytes. Reads of that partition cause garbage collection pauses and heap pressure on every replica that owns it.
  • Garbage collection pauses. Long JVM pauses make a node appear down to its peers, hints pile up, and coordinators time out. Heap sizing, the collector and off-heap settings need to match the workload and the Java version.
  • Node replacement and scaling. Bootstrapping, decommissioning and replacing a dead node all stream large amounts of data. Done in the wrong order, or with inconsistent schema across nodes, they turn a hardware failure into an outage.

Upgrading off Cassandra 3.x

The upgrade is a rolling restart, one node at a time, with no downtime when it is done correctly. The rules are firm. Upgrade from a recent patch release of your current line, run upgradesstables after the binaries change, never run repair or make schema changes while the cluster is on mixed versions, and do not skip major versions beyond what the project documents as supported: 3.x clusters go to 4.0 or 4.1 before 5.0. Drivers need checking because 4.0 changed protocol defaults and removed Thrift, which still matters for very old applications. Cassandra 5.0 brings storage-attached indexes, the unified compaction strategy and support for newer Java versions, all worth having, none of which should be enabled on the day of the upgrade.

Open source or a commercial distribution?

The choice shapes your support options more than any other decision. Apache Cassandra is free, moves at the pace of the project and leaves support to you. DataStax Enterprise adds proprietary features, tooling and a vendor contract, and ties you to that vendor's versions and pricing. A managed service removes node operations and keeps the data model, query design and client behaviour as your responsibility. Many organisations run more than one of these across business units. Whatever the mix, ask any provider the same things: which versions they cover, whether an emergency response is an engineer or an acknowledgement, whether they will carry out the upgrade with you, and whether they will tell you when Cassandra is the wrong database for a workload.

Where independent Cassandra support fits

  • Self-managed open source clusters, on-premises or in the cloud, with nobody to call.
  • Unmaintained 3.x versions, while the upgrade is planned and rehearsed.
  • Troubleshooting and performance tuning: latency, throughput, compaction, repair and JVM configuration for the real workload.
  • Data model and schema reviews, because most Cassandra problems are CQL table design problems discovered at scale.
  • Teams without Cassandra experts. A single administrator who understands the cluster is a single point of failure that the database itself was designed to avoid.

AceMQ provides 24/7 Cassandra support for Apache Cassandra on any version, with response targets from 15 minutes, by plan, and named senior engineers. Examples: a tombstone and read timeout remediation and repair and compaction support. For how Cassandra's support window compares with other technologies, see support windows compared.

AceMQ Apache Cassandra support: first response by severityResponse targets by plan; your contract sets the tier.
SeverityFirst responseTypical issue
P1 — EmergencyFrom 15 min (by plan)Production down, data not flowing, cluster or node failure
P2 — Critical1 hourSevere degradation, rising error rates, approaching capacity limits
P3 — High4 hoursPerformance issues, configuration problems, non-critical failures
P4 — StandardNext dayQuestions, guidance, best practices, non-urgent improvements

Sources

  • Apache Cassandra download page, cassandra.apache.org/_/download.html
  • IBM Community post, 3 Oct 2025, community.ibm.com/community/user/blogs/datastax-pm-team-datastax-pm-team/2025/10/02/ibm-datastax
  • Instaclustr, instaclustr.com/support/ and instaclustr.com/platform/managed-apache-cassandra/
  • Canonical, canonical.com/data/cassandra
  • Amazon Keyspaces SLA, aws.amazon.com/keyspaces/sla/ (dated 24 May 2023)
  • Microsoft Azure, azure.microsoft.com/en-us/products/managed-instance-apache-cassandra

Frequently Asked Questions

Who has the best Cassandra support?

It depends on who runs the nodes and what you need written down. Use the eight-question scorecard in the buyer's guide, and ask each provider for versions, response targets and exit terms in writing.

Which companies offer Apache Cassandra support?

The Apache Cassandra community maintains current versions with no SLA. DataStax, now part of IBM, supports DataStax Enterprise and Astra, and managed providers support their own services. Independent providers such as AceMQ support self-managed Apache Cassandra on any version.

Which Cassandra versions are supported?

The project currently lists Cassandra 5.0 as maintained until the 8.0 release, 4.1 until 7.0, and 4.0 until 6.0. Older versions, including 3.0 and 3.11, are unmaintained.

Is Cassandra 3.11 still supported?

Not by the project. Cassandra 3.x is unmaintained. Independent providers support 3.x clusters while the upgrade to 4.x and 5.0 is planned.

Is Cassandra still used?

Yes. Apache Cassandra remains widely used for high-volume, always-on workloads, and the project shipped Cassandra 5.0 with new indexing and compaction features.

Can I upgrade Cassandra without downtime?

Yes. Upgrades are rolling, one node at a time. The cluster must not run repairs or schema changes while on mixed versions, and SSTables should be upgraded after each node moves.

Tyler Eastridge

Author

Tyler EastridgeHead of Operations

Head of Operations at AceMQ. Writes the commercial coverage here: RabbitMQ and VMware licensing, pricing, renewals and support models.

Talk to an engineer

Need a hand with Cassandra?

Senior engineers who run it in production. Get a quote or a free consultation, no sales pitch.

Free Consultation

Get Expert Eyes on Your Cassandra Environment

Whether you're troubleshooting a production incident, planning a migration, or want a second opinion on your architecture — our team is ready. No pitch, just answers.

Email Us