Which companies offer Apache Kafka support?
Confluent supports Confluent Platform and Confluent Cloud under its own subscriptions. AWS supports Amazon MSK as a service, which covers the managed infrastructure rather than your topic design, consumers or clients. The Apache Kafka project itself offers community mailing lists, not a support contract. Independent providers such as AceMQ support open-source Apache Kafka, Confluent Platform and MSK estates under one 24/7 contract with response targets from 15 minutes, by plan.
Can I get commercial support for open-source Apache Kafka without buying Confluent?
Yes. Apache Kafka commercial support does not require a Confluent subscription, and a support contract for Apache Kafka can come from an independent provider. AceMQ supports Apache Kafka as released by the project, on the version you run, including clusters still on ZooKeeper, with incident response, root cause analysis, upgrade planning and KRaft migration support.
Do you offer Kafka EOL support for older versions?
Yes. The Apache project maintains only its three most recent releases, which as of October 2026 are Kafka 4.4, 4.3 and 4.2. Every 3.x and 2.x line, and Kafka 4.0 and 4.1, receive no upstream fixes. AceMQ supports the version you are actually running, advises on which CVEs affect it, and plans the upgrade path, including the ZooKeeper to KRaft migration that Kafka 4.0 made mandatory. Where you need security patches on a version you cannot yet leave, AceMQ's OSSeva platform backports CVE fixes to Apache Kafka 2.8.x through 3.7.x.
What does AceMQ Apache Kafka support include?
Kafka support covers 24/7 emergency incident response with response targets from 15 minutes, by plan, written root cause analysis on every P1, throughput and latency tuning, security and CVE advisory, Kafka Connect and Schema Registry coverage, and upgrade or migration support. Every ticket is handled by a named senior engineer assigned to your account. There is no first-line triage layer and no per-incident charge.
Do you support Amazon MSK and Confluent, or only self-managed Kafka?
All three. We support self-managed Kafka, Amazon MSK and MSK Serverless, and Confluent Platform and Confluent Cloud. Managed Kafka removes broker provisioning but leaves you the parts that cause most incidents — partition design, consumer group behavior, client configuration, and topic-level retention. Those are exactly where our diagnostic time goes, and they are outside what provider support typically covers.
How fast do you respond to a Kafka production outage?
P1 emergencies — brokers down, a partition with no leader, a consumer group stuck in perpetual rebalance — get response targets from 15 minutes, by plan, with a senior engineer joining a live bridge. P2 critical issues are 1 hour, P3 high-priority 4 hours, and P4 standard questions next business day. Exact targets are set by plan.
Can you help with consumer lag that we can't explain?
Yes, and it is one of the most common things we are called for. Unexplained lag is usually one of four things: a rebalance loop caused by processing time exceeding max.poll.interval.ms, partition-to-consumer skew from a poor key distribution, a slow downstream dependency inside the poll loop, or a hanging transaction pinning the last stable offset. We instrument the consumer to identify which before changing any configuration.
Do you support the migration from ZooKeeper to KRaft?
Yes. We plan and execute ZooKeeper-to-KRaft migrations, including the dual-write bridge phase, controller quorum sizing, and the version gates that have to be cleared before migration can start. We also do rolling version upgrades with inter.broker.protocol.version staging so clients are never forced into a lockstep deploy.
Can you support Kafka Connect and Schema Registry too?
Yes, both are inside the standard contract. Connect worker rebalances, failed tasks, sink connector backpressure, and dead-letter queue design are common ticket sources. So are Schema Registry compatibility failures during rolling producer deploys, where a schema change is accepted by the registry but breaks consumers still running the previous version.
Do you cover Kafka disaster recovery and multi-region replication?
Yes, and the design question comes before the tooling. MirrorMaker 2 and Cluster Linking replicate differently, and neither gives you an RPO by itself — offsets, consumer group state and topic configuration all have to be part of the plan or a failover leaves consumers reprocessing or skipping. We review the replication topology, what actually fails over versus what has to be rebuilt, and the recovery procedure end to end. Active-active, active-passive and stretch clusters each carry different failure behaviour under partition, and the right answer depends on whether your workload can tolerate duplicate delivery.
What does Kafka backup and retention management involve?
Kafka is not a database and backing it up like one goes wrong. Durability comes from replication factor, min.insync.replicas and acks together — a replication factor of three with min.insync.replicas of one will lose data on a broker failure regardless of your backup. Beyond that, retention and tiered storage decide what is actually recoverable and for how long, and topic-level overrides routinely drift from the cluster default. Support covers reviewing that configuration against the durability you believe you have, plus the offset and schema state you would need to reconstruct a cluster.
Do you audit Kafka security and monitor clusters in production?
Both. A security review covers SASL mechanism and TLS configuration, ACLs and whether the principals map to what teams actually need, ZooKeeper or KRaft controller exposure, and inter-broker encryption. On monitoring, the signals that predict incidents are under-replicated and offline partitions, ISR shrink rate, request handler idle ratio, consumer lag trend by partition rather than aggregate, and controller election frequency. Alerting on broker liveness alone finds out after users do. We define the thresholds and review what you already collect in Prometheus, Grafana, Datadog or whatever is in place.
What are Apache Kafka support services?
Kafka support services are a contract for technical support on a Kafka cluster you run: SLA-backed incident response from Kafka experts, root cause analysis, performance tuning, upgrade planning across the Kafka lifecycle, and reviews that prevent downtime and data loss before they happen. Apache Kafka is a distributed event streaming platform from the Apache Software Foundation, and the project itself offers mailing lists, not a contract. Support covers the brokers and controllers, and in practice also the things around them that fail more often: producers and consumer groups, Kafka Connect, Kafka Streams applications, Schema Registry, and the data pipelines that depend on them. Good support also leaves runbooks behind, so the next incident is shorter.
What changed between Kafka 3.x and Kafka 4.x, and do you support both?
Kafka 4.0 removed ZooKeeper entirely, so every 4.x cluster runs in KRaft mode, and a 3.x cluster has to be migrated to KRaft on a late 3.x release before it can move to 4.x. Kafka 4.0 also dropped support for the oldest client protocol versions, moved to newer Java requirements, and made the new consumer group rebalance protocol generally available. We support both lines. For 3.x clusters, which the project is phasing out, that means incident response and mitigation now, and a rehearsed KRaft migration and upgrade when you are ready.
Why use independent Kafka support instead of a managed Kafka service?
They solve different problems. Managed Kafka services such as Confluent Cloud or Amazon MSK run the brokers for you, which removes infrastructure work and introduces a degree of vendor lock-in and a cost that scales with throughput. They do not operate your producers, consumers or stream processing, which is where most incidents start. Independent support keeps the streaming platform under your control, on premises or in your own cloud account, and adds round-the-clock support from engineers who can see the whole path. Many teams use both: a managed service for the brokers, and a support partner for everything that talks to them.
When does a team need a Kafka support contract?
Usually at one of four moments: an audit or customer contract requires a support agreement for production Kafka; the team has no dedicated Kafka SRE and incidents depend on one person; a Kafka 3.x to 4.x upgrade or ZooKeeper to KRaft migration is coming; or the organisation is leaving Confluent or MSK support and wants cover that does not depend on the platform.
Can we keep Confluent Platform but move our support away from Confluent?
For Apache Kafka and the community components, yes: AceMQ supports Confluent Platform deployments directly. Check one thing first. Confluent Platform's enterprise features, such as Control Center and role-based access control, run under Confluent's commercial licence, so dropping the subscription can mean losing those features rather than just changing who answers the phone. We help map exactly which components you use before you decide.
What is Kafka enterprise support, and who provides it?
Kafka enterprise support is a paid contract with defined response times for a production Kafka estate, as opposed to community help from mailing lists and forums. Confluent (now part of IBM) provides it for Confluent Platform and Confluent Cloud, AWS covers the Amazon MSK service, and independent providers such as AceMQ support open-source Apache Kafka, MSK and Confluent Platform together. Compare them on which versions are covered, whether clients and Connect are in scope, and who answers a P1. Ours: response targets from 15 minutes, by plan; 24/7, from a named senior engineer.
How do I choose a Kafka support provider?
Start with scope, then response. Check which Kafka versions are covered, including ones the Apache project no longer patches, whether clients, Kafka Connect and Schema Registry are in scope, whether Amazon MSK and Confluent Platform clusters are covered, and who answers a P1 and how fast. A Kafka support provider that follows your estate, not one product, can cover a mixed fleet under one contract. Ours: response targets from 15 minutes, by plan; 24/7, from a named senior engineer.
What does IBM's acquisition of Confluent mean for Kafka support?
IBM announced the acquisition on 8 December 2025 and completed it on 17 March 2026. Existing Confluent contracts continue as signed, and renewals are now a conversation with IBM, so many teams are checking whether they need Confluent's platform or only support for Apache Kafka. Apache Kafka itself is unchanged. The options are compared in Confluent alternatives after the IBM acquisition.
Can we start with business-hours Kafka support and move to 24/7 later?
Yes. Coverage runs from business hours through to 24/7 with response targets from 15 minutes, by plan, and you can move up a coverage level when a workload becomes critical without re-onboarding: the engineers already know your clusters.
What is the difference between Kafka support and managed Kafka services?
Support is an SLA over clusters your team runs: you hold the pager and call us when something breaks. Managed Kafka services means AceMQ runs the clusters on your infrastructure or on AceMQ infrastructure, owning monitoring, patching, upgrades, capacity and on-call. Teams with a platform team that wants to keep ownership choose support; teams that want Kafka to stop being their problem choose managed services.
Who provides enterprise support for Kafka?
Confluent supports Confluent Platform and Confluent Cloud. AWS supports Amazon MSK as a service, which covers the managed infrastructure rather than your topic design or clients. The Apache Kafka project has community mailing lists, not a support contract. Independent providers such as AceMQ support Apache Kafka on self-managed, Strimzi, MSK and Confluent Platform clusters under one 24/7 contract with response targets from 15 minutes, by plan.
Can we get enterprise Kafka support without a Confluent subscription?
Yes. Apache Kafka is supportable without Confluent, and a support contract for it can come from an independent provider. AceMQ supports Kafka as released by the Apache project, on the version you run, with incident response, root cause analysis, upgrade planning and KRaft migration support. You lose Confluent's commercial components if you were using them, so check that list first.
What are the alternatives to Confluent support?
Three routes: an independent support contract for the Kafka you run, support through your cloud provider if you run Amazon MSK, or moving some workloads to a different platform after an assessment. AceMQ covers the first and helps you judge the others.
Who supports Kafka for HIPAA or PCI compliant environments?
AceMQ does, under the same 24/7 contract. We agree access in advance, advise on patching and encryption gaps for your Kafka version, and give written root cause analysis on P1s as audit evidence. We do not certify environments or give legal advice. The PCI DSS and HIPAA checklist for Kafka and Redis lists 40 checks to map to your scope.
We need multi-region disaster recovery for Kafka: who can design it?
AceMQ can design, test and support it. We start with written RPO and RTO targets, choose between MirrorMaker 2 mirroring, active-active and a stretch cluster, plan consumer offsets and renamed topics for failover, and rehearse at least quarterly. Asynchronous mirroring carries a recovery point equal to replication lag, so zero data loss needs synchronous replication.
Do you support Amazon MSK as well as self-managed Kafka?
Yes, including MSK Provisioned, Express and Serverless. AWS runs the service and supports it under your AWS Support plan. We work the Kafka layer: partition counts against broker limits, consumer group behaviour, client configuration and retention. Those are the causes of most MSK incidents and sit outside what a cloud provider's support typically covers.
Who offers Confluent Platform support besides Confluent?
Confluent supports Confluent Platform under its own subscriptions. AceMQ supports Confluent Platform clusters independently, 24/7, with response targets from 15 minutes, by plan. The Kafka core is supportable without a Confluent subscription, and Confluent-only components such as Control Center stay with Confluent.
Who offers Strimzi support?
Strimzi is supported by its open-source project community. AceMQ supports Kafka on Kubernetes including Strimzi under a 24/7 contract: broker pods and storage, rolling restarts, KRaft node pools, resource limits and operator upgrade order. Operator bugs needing an upstream fix stay with the project, and we work those escalations with you.
Do you support Strimzi and Kafka on Kubernetes?
Yes. We cover Kafka on Kubernetes including Strimzi: broker pod and storage behaviour, rolling restarts that trigger rebalances, KRaft node pools, resource limits and operator upgrade order. Operator bugs needing an upstream fix and control-plane faults stay with the operator project and your platform vendor, and we work those escalations with you.
Can you help us move from ZooKeeper to KRaft?
Yes. Apache Kafka 4.0 removed ZooKeeper mode, so clusters move to KRaft. We inventory your mode, metadata version, controller layout, clients, Java versions and anything that reads ZooKeeper, then plan and support the migration in order. A Kafka health check gives you the inventory first.
What does Confluent support cover that independent support does not?
Confluent support covers Confluent's commercial components, such as Control Center and role-based access control, and it can ship emergency patches before they reach Apache Kafka. Independent support covers the Kafka layer and the wider estate. If you use those components heavily, keep Confluent for them. If not, you can drop the platform licence and keep the Kafka cover.
Can we work with AceMQ on Apache Kafka without a long contract?
Yes. AceMQ works on Apache Kafka in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.
How much does AceMQ Apache Kafka support or consulting cost?
Every AceMQ proposal is tailored to your requirements: your Apache Kafka environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Apache Kafka is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.