Apache Kafka support

Apache Kafka Support for Self-Managed, MSK and Confluent Clusters

Last reviewed by Tyler Eastridge

AceMQ provides 24/7 Apache Kafka support under written SLAs, with response targets from 15 minutes, by plan, for self-managed clusters, Strimzi on Kubernetes, Amazon MSK and Confluent Platform. No Confluent licence is needed. Every ticket reaches a named senior engineer, and quote requests get a reply within 1 hour.

Most calls start with consumer lag that nobody can explain, brokers with under-replicated partitions, or a ZooKeeper to KRaft move that has not been planned. Senior engineers handle consumer lag, rebalance storms and under-replicated partitions across Americas, EMEA and APAC.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ Apache Kafka consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Independent support

Independent Kafka support with no Confluent licence required, from engineers with 10+ years in production

AceMQ supports Apache Kafka as released by the project, Amazon MSK, Strimzi on Kubernetes and Confluent Platform under one contract, 24/7 across Americas, EMEA and APAC. No Confluent licence is needed, and response targets start at 15 minutes, by plan.

  • Self-managed Apache Kafka

    On VMs, bare metal or Kubernetes, KRaft or ZooKeeper, on the version you run.

  • Amazon MSK

    Topic design, consumers, clients and broker settings, which the provider's own support scope does not cover.

  • Confluent Platform

    The Kafka core is supportable without a Confluent subscription. Confluent-only components, such as Control Center, stay under Confluent's commercial licence.

Who to buy from depends on what you run and who answers at 3am: Confluent support vs independent support

Incident Triage

Apache Kafka problems we fix every week

These are real symptoms from real Apache Kafka production environments — and the first thing our engineers check when one comes in.

Common Apache Kafka production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Consumer lag climbing steadily on one partition onlyPartition leader skew and per-consumer commit latency. One slow member holds the whole group back — and if processing exceeds max.poll.interval.ms the member is evicted mid-batch, triggering a silent rebalance loop that looks like lag.
Consumer group rebalancing constantly, throughput near zerosession.timeout.ms against heartbeat.interval.ms, whether the group is on the eager or cooperative-sticky assignor, and whether pods are being rescheduled. Rolling deploys on the eager assignor stop-the-world on every pod restart.
ISR shrinking and expanding repeatedly, URP alerts flappingreplica.lag.time.max.ms against follower fetch latency, then disk I/O wait and network saturation on the lagging broker. This is almost always a storage or NIC bottleneck on one node, not a Kafka configuration problem.
Producer throwing TimeoutException: Expiring N recordsWhether the batch is aging out in the accumulator (request.timeout.ms, delivery.timeout.ms, linger.ms) or the partition leader is unavailable. With acks=all and min.insync.replicas=2, losing one replica stalls every produce to that partition.
Disk filling on brokers despite short retention settingsWhether log cleanup is actually running: compacted topics with a stuck cleaner thread, open file handles pinning deleted segments, or segment.ms so large that retention.ms never gets a closed segment to delete.
Exactly-once pipeline stalls, consumers block on LSOHanging transactions — an aborted or never-committed producer transaction pins the last stable offset, so read_committed consumers stop. We identify the stuck producer ID and transactional.id.expiration.ms behavior before intervening.
KRaft controller quorum loses leadership, metadata writes failController log directory latency and the quorum voter set. In KRaft mode a slow metadata log disk on any voter causes election churn; on ZooKeeper-based clusters the same symptom traces to ZK session expiry from GC pauses.
Amazon MSK cluster degraded, but CloudWatch metrics look normalBroker-level partition count against instance class limits, MSK storage autoscaling state, and whether the client is pinned to a broker that failed over. MSK hides the broker logs you need — we pull them via the log delivery config first.

Every P1 closes with a written root-cause analysis.

Running Apache Kafka in production? Get a quote from a senior engineer, answered within one hour.

Contact Us

Coverage

Which Kafka deployments does AceMQ support, and who covers what?

AceMQ supports the Kafka you run, on the version you run, in any of the five setups below. One contract can span several. The table shows what we cover, what the vendor or platform covers, and what neither of us covers.

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Self-managed Apache Kafka (VMs, bare metal)24/7 incident response, written root cause analysis on P1s, broker and client tuning, partition and consumer-group problems, security and CVE advice, upgrade planningThe Apache project offers community mailing lists, not a support contractYour producers and consumers are reviewed, not rewritten; hardware and network faults outside the agreed scope
Strimzi and Kafka on KubernetesKafka behaviour on the platform: broker pods and storage, rolling restarts and rebalances, KRaft node pools, resource limits, operator upgrade order, client reconnectsStrimzi is a CNCF incubating project; its site lists vendors such as Red Hat, Axual, Aenix and IBM (strimzi.io, read 17 November 2026). The Kubernetes platform vendor supports the clusterOperator bugs that need an upstream fix; control-plane faults
Amazon MSK (Provisioned, Express, Serverless)The Kafka layer on the service: partition design and counts against broker limits, consumer group behaviour, client configuration, retention, upgrade planning between MSK versionsAWS runs the service and supports it under your AWS Support plan (Business Support+: production system down within 1 hour, business-critical within 30 minutes; Enterprise Support: within 15 minutes; AWS Support plans page, read 17 November 2026)AWS platform faults; features MSK does not expose
Confluent PlatformThe Apache Kafka layer inside Confluent Platform, including Connect and Kafka Streams applications, plus advice on which Confluent-only components you really useConfluent supports every component of Confluent Platform, including its commercial features such as Control Center and role-based access control (Confluent subscription page, read 17 November 2026)Confluent-only components under Confluent's licence; fixes that ship only in Confluent's build
KRaft and ZooKeeper clustersRunning either mode, ZooKeeper to KRaft migration planning, controller quorum design, and the client, Java and tooling inventory a 4.x upgrade depends onApache Kafka 4.0 removed ZooKeeper mode. Confluent Platform 8.0 removed ZooKeeper and requires KRaft (Confluent docs, read 17 November 2026). On MSK, 3.9 is the last version supporting both modes (AWS MSK docs, read 17 November 2026)Third-party tools that still read ZooKeeper must be changed by their owners

Sources, read 17 November 2026: strimzi.io, aws.amazon.com/premiumsupport/plans/, confluent.io/subscription/, docs.confluent.io (versions and interoperability), docs.aws.amazon.com/msk (supported Kafka versions).

Your options

Who provides enterprise support for Kafka? Confluent and independent support compared

Confluent supports Confluent Platform and Confluent Cloud, its own distribution and products. Independent providers support Apache Kafka wherever it runs. You do not need a Confluent subscription to get commercial support for Kafka, and you can keep Confluent for the components that need it.

Confluent support
AceMQ independent support
What it coversConfluent Platform: Apache Kafka (with Connect and Kafka Streams), ZooKeeper, ksqlDB, Schema Registry and REST Proxy. Confluent Cloud under its own plans
What it coversApache Kafka on self-managed, Strimzi, MSK and Confluent Platform clusters
Commercial featuresControl Center, role-based access control, tiered storage and other features in the subscription
Commercial featuresNot provided; we advise whether you use them and what replaces them
Hours and responseConfluent Platform page: "30, 60, or 90 minute response times depending on support plan" and 24/7 support listed. Confluent Cloud: Business and Premier plans have 24x7 coverage, P1 within 60 minutes (Business) or 30 minutes (Premier)
Hours and response24/7 across Americas, EMEA and APAC; response targets from 15 minutes, by plan
Release support windowTwo years is the standard for commercial components; one extra year with Platinum support (Confluent Platform versions page)
Release support windowWe support the version you run and plan the upgrade
Emergency patchesSubscription includes emergency patches not yet in open-source Apache Kafka
Emergency patchesWe diagnose, advise on CVEs for your version and plan the upgrade path
PriceBy subscription; Confluent Cloud lists "Contact us for licensing details" for self-managed components on Business and Premier
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour
OwnershipConfluent became part of IBM on 17 March 2026 and continues as a distinct brand
OwnershipIndependent of Confluent, IBM, AWS and Strimzi vendors

Sources, read 17 November 2026: confluent.io/subscription/, docs.confluent.io (versions and interoperability), confluent.io/confluent-cloud/support/, and the Confluent press release of 17 March 2026 on IBM completing the acquisition. The Confluent pages do not map the 30, 60 and 90 minute targets to plan names, so none is shown. Where Confluent fits better: if you rely on Control Center, role-based access control or tiered storage, Confluent support is the straightforward choice; without those, an independent contract covers the Kafka layer without the platform licence.

Renewal coming up?

Confluent renewal coming up? Check this first

IBM completed its acquisition of Confluent on 17 March 2026, so the next renewal is a negotiation with a new owner. Apache Kafka did not change hands. List the Confluent-only components you actually run, such as Control Center or role-based access control. If the list is empty, get an independent quote for the Kafka layer before you renew. We reply to quote requests within 1 hour.

What's Included

Kafka enterprise support

Kafka enterprise support from AceMQ is a 24/7 contract for production Apache Kafka: incident response, a written root cause analysis on every P1, consumer, broker and replication work, security advice and upgrade or KRaft migration planning, with no per-ticket charges.

  • 01

    Emergency Incident Response

    Brokers down, a consumer group that won't stabilize, or a partition with no leader. With response targets from 15 minutes, by plan, a senior Kafka engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the specific broker setting, client config, or topic design change that prevents recurrence.

  • 03

    Throughput & Latency Tuning

    Partition count, batch size and linger, compression choice, fetch sizing, and replication settings tuned against your actual message sizes and consumer processing time — not against a generic benchmark.

  • 04

    Security & CVE Advisory

    mTLS and SASL/OAUTHBEARER configuration review, ACL auditing, and proactive alerts for CVEs affecting your exact Kafka, Connect, or client library version with tested upgrade paths.

  • 05

    Connect & Schema Registry

    Kafka Connect worker failures, dead-letter queue design, sink connector backpressure, and Schema Registry compatibility breaks during rolling producer deploys — all inside the same contract.

  • 06

    Upgrades & Cluster Migration

    Rolling upgrades with inter.broker.protocol.version staging, ZooKeeper-to-KRaft migration, and cluster moves between self-managed, MSK, and Confluent with mirrored offsets.

Want AceMQ to take this off your team's plate? Tell us about your Apache Kafka estate.

Contact Us

Why AceMQ

What you get that you don't get elsewhere

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your partition layout, your retention policy, and your consumer topology — so a P1 call starts with diagnosis instead of twenty minutes of you describing your cluster.

  • No First-Line Triage Layer

    You reach a senior Kafka engineer directly by phone, email, or Slack. Nobody collects information to pass along, and no escalation approval sits between you and someone who can read a controller log.

  • Clients and Brokers, Both Sides

    Most Kafka incidents are client-side: prefetch, poll loops, commit strategy, or a producer with the wrong acks setting. We debug your Java, Go, Python, or .NET consumers alongside the brokers, because that's where the fault usually is.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

  • Proactive, Not Just Reactive

    Quarterly cluster health checks plus shared intelligence across our support base. When a version-specific broker bug or client library regression surfaces on one cluster, every affected customer hears about it before it reaches their production.

  • Managed Kafka, Fully Covered

    Amazon MSK and Confluent Cloud remove some operational surface but not the ones that cause incidents. We support managed clusters as first-class environments, including the parts the provider's own support scope stops short of.

We support Apache Kafka wherever it's deployed

Cloud, Kubernetes, bare metal, hybrid, and air-gapped — including environments where you can't give us outbound network access.

  • AWS (EC2, ECS, EKS)
  • Amazon MSK & MSK Serverless
  • Confluent Platform & Confluent Cloud
  • Microsoft Azure (AKS, HDInsight)
  • Google Cloud (GKE)
  • Strimzi on Kubernetes
  • Red Hat OpenShift
  • Bare metal & on-premise
  • Hybrid cloud & multi-region
  • Air-gapped / no outbound access
  • KRaft-mode clusters
  • ZooKeeper-based clusters

Not sure which option fits? A senior Apache Kafka engineer will scope it with you.

Contact Us

Version coverage

Apache Kafka versions we support

The Apache project maintains only its three most recent release lines. AceMQ supports the version you run in production, including the ones Apache no longer patches.

Apache Kafka versions we support
Kafka versionLatest releaseApache statusAceMQ coverage
Kafka 4.44.4.0, released 22 October 2026Supported release24/7 support
Kafka 4.34.3.2, released 23 October 2026Supported release24/7 support
Kafka 4.24.2.2, released 29 September 2026Supported release24/7 support
Kafka 4.0 and 4.1ArchivedEnd of life: no further fixes24/7 support and upgrade planning
Kafka 3.8 and 3.9ArchivedEnd of life (3.9 was the last 3.x release)24/7 support and ZooKeeper to KRaft migration
Kafka 2.8 to 3.7ArchivedEnd of life24/7 support, plus CVE fixes backported through OSSeva
Kafka 2.7 and earlierArchivedEnd of lifeSupport and upgrade planning

Source: the Apache Kafka downloads page, checked 28 October 2026. The project aims for three feature releases a year and makes bug-fix releases for supported releases only.

Designing the event-driven systems that run on Kafka, not just supporting the cluster? See our event-driven architecture consulting.

Who supports Kafka

Kafka commercial support

Commercial support for Apache Kafka does not have to come from Confluent. It comes from Confluent for Confluent Platform and Confluent Cloud, from AWS for the Amazon MSK service, or from an independent provider such as AceMQ for open-source Kafka on any infrastructure.

  • From Confluent

    Confluent supports Confluent Platform and Confluent Cloud under its own subscriptions.

  • From AWS

    AWS supports Amazon MSK as a service, which covers the managed infrastructure rather than your topic design, consumers or clients.

  • From an independent provider

    The Apache Kafka project offers community mailing lists, not a support contract. AceMQ covers open-source Kafka on the version you run, with a named engineer, for $24,000 to $72,000 a year (USD) by scope.

A support contract and a Kafka health check are separate purchases, and many teams start with the health check below. Commercial support for open-source Kafka

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Pricing in USD

What Apache Kafka support costs, in US dollars

AceMQ's Apache Kafka support contracts run $24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Cover runs 24/7 across Americas, EMEA and APAC for self-managed Kafka, Amazon MSK and Confluent Platform, with response targets from 15 minutes, by plan. Quote requests get a reply within 1 hour.

  • Kafka version and mode

    Your Apache Kafka version, and whether the cluster runs on ZooKeeper or KRaft. Both shape the upgrade plan the contract covers.

  • Where it runs

    Self-managed on VMs or Kubernetes, Amazon MSK, or Confluent Platform.

  • Clusters, brokers and environments

    How many clusters and brokers you run, and which environments need cover: production, staging, disaster recovery.

  • Connect, Schema Registry and streams apps

    Kafka Connect, Schema Registry and Kafka Streams applications in use, so the contract names what the engineer will be asked about.

  • Cover hours and response target

    Business hours or 24/7, and the response target you need. Targets start at 15 minutes, by plan.

  • Compliance limits

    Any data residency, audit or access rules that limit who may touch the cluster.

The low end of the range covers a small cluster (three to six brokers) on a business-hours SLA. A contractual 24/7 response SLA on a larger estate sits at the high end. A quote needs the six things above: send them and the reply comes within 1 hour. Kafka support cost, self-managed vs commercial

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

IBM and Confluent

IBM now owns Confluent: keep Apache Kafka with independent support

IBM announced the deal on 8 December 2025 ($31 a share in cash, about $11 billion in enterprise value) and completed it on 17 March 2026. Apache Kafka did not change hands: it is still an Apache Software Foundation project, and your cluster is only affected if you run Confluent's commercial products.

  • What changed

    Confluent Platform and Confluent Cloud now belong to IBM, and Confluent has said it continues as a distinct brand inside IBM. Existing contracts run as signed. What changes is who you negotiate the next renewal with.

  • What did not

    Open-source Apache Kafka, Amazon MSK and Strimzi clusters are unaffected, and the Kafka core inside Confluent Platform is supportable without a Confluent subscription. AceMQ supports all of them under one contract.

  • What to check before a renewal

    List which Confluent-only components you actually run, such as Control Center or role-based access control, which sit under Confluent's commercial licence. If the answer is none, get an independent quote for the Kafka layer before you renew.

Source: the IBM newsroom release of 17 March 2026. If your Confluent renewal is coming up, see Confluent pricing and renewals after IBM. Confluent pricing and renewals after IBM

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Entry offer

Start with a Kafka health check

Most Kafka support relationships begin with an engineer-led review of the running cluster, so the contract is scoped on what the estate needs rather than a broker count. A health check takes one to four weeks, depending on complexity. It is not a condition of support.

  • What we review

    Nine areas on every cluster, including KRaft readiness, replication and ISR, partition skew, consumer lag, ACLs and TLS, retention, client configuration, and the monitoring that should have caught your last incident.

  • What you get

    A written report, a ranked fix list and the reasoning behind each finding, walked through with your team by the engineer who did the review.

  • How it leads into support

    The findings become the first runbooks and the starting scope of a support contract, with named senior engineers on your account from day one.

When Kafka is not the right tool, an assessment says so. American National Insurance chose Debezium Server and RabbitMQ over Kafka for SQL Server change data capture, after AceMQ assessed both. See the Kafka health check

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Regulated environments

Kafka support for HIPAA and PCI DSS environments

AceMQ supports Kafka clusters that carry PCI DSS or HIPAA-scoped data: the same 24/7 contract, with access, patching and evidence handled so your compliance team can audit them. We do not certify your environment or give legal advice; your assessor decides scope.

What Kafka support does about each compliance need
Compliance needWhat support does about it
Who can touch the clusterSenior engineers assigned to your account, with access agreed in advance: who connects, how, and with which privileges
Patching on a scheduleAdvisories for CVEs that affect your exact Kafka version, with a tested upgrade path and a written plan for each
Encryption and authentication driftReview of TLS on client, inter-broker and controller listeners, SASL mechanism, ACL coverage and wildcard grants, after changes and on request
Neither product encrypts data at restAdvice on tokenising or encrypting fields before they are produced, and on copies such as MirrorMaker 2 targets and snapshots
Audit evidenceWritten root cause analysis on every P1, and a record of what was changed and why
Logs of accessHelp shipping broker and authorizer logs off the host so they survive an incident

See the PCI DSS and HIPAA checklist for Kafka and Redis (40 checks, each with its requirement number) and Kafka in HIPAA and PCI DSS environments: what support must cover.

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Disaster recovery

Multi-region disaster recovery for Kafka: who can design it?

AceMQ designs, tests and supports multi-region Kafka disaster recovery. It starts with a written recovery point and recovery time objective, because the design follows from them. Asynchronous mirroring with MirrorMaker 2 is the most common pattern, and its recovery point equals the replication lag.

The design checklist:

  1. Write the RPO and RTO per topic class before choosing a pattern.
  2. Choose the pattern: active-passive mirroring, active-active, or a stretch cluster. Zero data loss needs synchronous replication (acks=all with min.insync.replicas on a stretch cluster); async mirroring always carries lag.
  3. Plan consumer offsets: MirrorMaker 2 renames replicated topics with the source cluster alias as a prefix, so failover runbooks must point consumers at the renamed topics and confirm where each critical group resumes.
  4. Replicate topic configuration and ACLs, and keep credentials and certificates valid in the target region.
  5. Size the standby for failover load, not for idle.
  6. Write the client failover procedure and automate what you can.
  7. Test quarterly at minimum, and after any material change; measure the real RTO against the target.

Read more in Kafka disaster recovery: architectures, RPO/RTO and testing.

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Scope

What a Kafka support contract covers (and doesn't)

A Kafka support contract normally covers broker and cluster operations, consumer and producer behaviour, performance diagnosis, upgrade guidance and escalation with a response commitment by severity. It usually excludes your application code, the infrastructure beneath Kafka and third-party tooling, and contracts get argued where a Kafka symptom has a non-Kafka cause.

The questions to settle before you sign are in Kafka Contract Checklist: Scope and Grey Areas.

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Confluent Platform

Confluent Platform support

AceMQ supports Confluent Platform clusters under the same 24/7 contract as Apache Kafka and Amazon MSK, with response targets from 15 minutes, by plan. The Kafka core inside Confluent Platform is supportable without a Confluent subscription. Confluent-only components, such as Control Center, stay under Confluent's commercial licence and Confluent's own support.

We handle brokers, controllers, consumer lag, Connect and Schema Registry behaviour, security review and upgrade planning on the version you run. Defects in Confluent-only components stay with Confluent.

Choosing between the two routes is covered in Confluent support vs independent support. For a move between Confluent and Apache Kafka, see Confluent migration.

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

ZooKeeper

ZooKeeper support

AceMQ supports Kafka clusters that still run on ZooKeeper, and plans and supports the move to KRaft. Cover is the cluster as one system, 24/7, with response targets from 15 minutes, by plan: ZooKeeper session expiry from GC pauses, security review of ZooKeeper exposure, rolling upgrades and migration planning.

Kafka 4.0 removed ZooKeeper mode, so a 3.x cluster has to be migrated to KRaft on a late 3.x release before it can move to 4.x. We inventory your mode, metadata version, controller layout, clients, Java versions and anything that reads ZooKeeper, then plan and support the migration, including the dual-write bridge phase.

A Kafka health check gives you the inventory first. Version paths are on Kafka upgrades.

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Strimzi

Strimzi support

AceMQ supports Kafka on Kubernetes, including Strimzi, 24/7, with response targets from 15 minutes, by plan. Cover includes broker pod and storage behaviour, rolling restarts that trigger rebalances, KRaft node pools, resource limits and operator upgrade order. Operator bugs that need an upstream fix stay with the operator project, and we work those escalations with you.

Strimzi clusters sit under the same contract as self-managed Apache Kafka, Amazon MSK and Confluent Platform, so one engineer owns the incident whichever layer it started in.

If you want AceMQ to run the operator and the clusters for you, see managed Kafka.

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Escalation Path

Your first hour of an Apache Kafka outage

Every tier reaches a senior Apache Kafka engineer. There is no tier-1 triage layer to get through.

  1. From 15 min (by plan)first responseEmergencyProduction down: brokers down, under-replicated partitions, consumer groups stalled
  2. 1 hourfirst responseCriticalSevere degradation, high error rates, approaching capacity
  3. 4 hoursfirst responseHighPerformance issues, configuration problems, non-critical failures
  4. Next Dayfirst responseStandardQuestions, guidance, best practices, non-urgent improvements

Response targets by plan; your contract sets the tier.

P1 escalation path

A replay of one P1, from the first page to the written root-cause analysis

SLA 15:00
T+Elapsed15:00
Engineer on your bridge

Response targets from 15 minutes, by plan; 24/7.
A response time, not a resolution time.

  1. T+00:00

    P1 opened, on-call engineer paged

    Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in Kafka, Kafka Connect, MSK or Kubernetes. No web form, no tier-1 queue.

    Paged
  2. T+15:00

    Senior engineer on your bridge

    A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.

    Live
  3. T+30:00

    Specialists across the stack join

    When an incident crosses components, the engineers who know each one join. For Kafka, that is the engineer who already knows your broker and consumer layout.

    If needed
  4. After

    Written root-cause analysis

    Root cause, the fix applied and the prevention steps, delivered after every P1.

    Every P1

Ready to talk Apache Kafka? Get a quote or send us a message.

Contact Us

Pricing

What does AceMQ Apache Kafka support cost?

AceMQ Apache Kafka support contracts typically run $24,000–72,000 a year, depending on SLA level, scope (number of clusters or nodes, and environments) and deployment (self-managed, Amazon MSK, Confluent Platform or Kubernetes).

What does AceMQ Apache Kafka support cost?
What moves the priceHow it changes the contract
SLA levelBusiness-hours cover costs less than 24/7 cover with response targets from 15 minutes, by plan.
ScopeMore clusters or nodes, and more environments, make a larger contract.
DeploymentSelf-managed, cloud-managed and Kubernetes estates need different amounts of hands-on work.

Covering several technologies under one contract, for example RabbitMQ, Kafka and Redis, earns an aggressive discount.

Support In Practice

Apache Kafka problems we've already solved

Kafka support, remediation and assessment work from AceMQ. Each card links to the full write-up: the cluster, what AceMQ diagnosed or changed, and the result.

1 / 6 case studies

All use cases

Support options

Four tiers of Apache Kafka support.

AceMQ offers Apache Kafka cover in four options, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for clusters your team runs, proactive monitoring that catches lag, ISR and CVE problems first, managed Kafka on your own infrastructure, and fully managed Kafka on a dedicated cluster hosted by AceMQ. Self-managed Kafka, Confluent Platform and Amazon MSK are covered.

  • Tier 1

    Apache Kafka 24/7 Support & Incident Management

    You run it, we back you up

    • Response targets from 15 minutes, by plan; 24/7, by phone, email or Slack
    • Self-managed Kafka, Confluent Platform and Amazon MSK
    • Written root-cause analysis after every P1

    Best for: Teams that run Kafka themselves and need senior cover at 3am.

  • Tier 2

    Apache Kafka 24/7 Support with Proactive Monitoring

    You run it, we watch it with you

    • Scheduled health checks of brokers, topics and consumer groups
    • CVE alerts for your exact Kafka version, with OSSeva backports for 2.8 to 3.7
    • Partition, retention and disk headroom reviews

    Best for: Clusters where a rebalance storm or a shrinking ISR must be caught before users notice.

  • Tier 3

    Managed Apache Kafka on Your Infrastructure

    We run it in your cloud or data centre

    • AceMQ runs day-2 operations and holds the pager
    • Strimzi on Kubernetes, VMs, bare metal or air-gapped sites
    • Kafka Connect, Schema Registry and MirrorMaker 2 under the same service

    Best for: Regulated estates that must keep Kafka brokers inside their own boundary.

  • Tier 4

    Fully Managed Apache Kafka on AceMQ Infrastructure

    We host it and run it, as a service

    • Dedicated cluster hosted and operated by AceMQ
    • Upgrades, partition planning and capacity managed to an agreed plan
    • Runbooks and topology documentation are yours to keep

    Best for: Teams that want Kafka endpoints without a cloud account, Kubernetes or a rota to run.

Who does what in each AceMQ Apache Kafka support option
Who does whatTier 1
24/7 support
Tier 2
Proactive monitoring
Tier 3
Managed, your infrastructure
Tier 4
Fully managed by AceMQ
Who runs Apache Kafka day to day?Your teamYour team, with AceMQ reviewsAceMQAceMQ
Where does it run?Your infrastructureYour infrastructureYour cloud account or data centreAceMQ infrastructure
24/7 incident responseResponse targets from 15 minutes, by planResponse targets from 15 minutes, by planResponse targets from 15 minutes, by planResponse targets from 15 minutes, by plan
Health checks and CVE alertsOn requestScheduledIncludedIncluded
Patching and upgradesYour team, AceMQ advisesPlanned with AceMQDone by AceMQDone by AceMQ
Monitoring and on-callYour teamYour teamAceMQAceMQ
Data, keys and accountsYoursYoursYoursYour data, hosted by AceMQ

Every Tier can start as an ad hoc engagement or an annual partnership, and you can move up or down a Tier as your team changes.

One partner for Apache Kafka

Everything else AceMQ does for Apache Kafka.

Support is one part of what AceMQ does for Apache Kafka. The same engineers deliver consulting, health checks, migrations and end-of-life cover, and support the systems that usually run next to it.

Support for the rest of your stack

See support for every technology we coverShow fewer

FAQ

Apache Kafka support questions

Still have questions about Apache Kafka? Email an Expert

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.

Let's talk

Your Kafka Cluster Shouldn't Wake You Up at 3am

Reactive cover, proactive reviews, or AceMQ running Apache Kafka for you on your infrastructure or ours. A senior engineer scopes it with you, and quote requests are answered within 1 hour.

A senior Apache Kafka engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an Apache Kafka Architect

Get in Touch

Talk to an Apache Kafka Expert

Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.

305-204-2607
info@acemq.com
66 W. Flagler St. 9th Floor
Miami, FL 33130

Prefer to talk now? Call us directly or use the consultation tab to find a time that works.

We respond within 1 hour.

Pick a time that works — no pressure, no pitch. Just 30 minutes with an expert.

We respond within 1 hour.