Redpanda support

Redpanda Support for Self-Managed, BYOC and Kubernetes Clusters

Last reviewed by Tyler Eastridge

AceMQ supports Redpanda 24/7 across Americas, EMEA and APAC: self-managed clusters, Redpanda Cloud BYOC and Dedicated, and Kubernetes or bare metal. Most calls start with one of three problems: local disk filling although tiered storage is on, partition leadership flapping between brokers, or a Kafka client that behaves differently against Redpanda after a migration.

AceMQ supports Redpanda in production — brokers running low on disk from tiered storage misconfiguration, Raft group leadership flapping under network instability, and client libraries that assume Kafka-specific broker behavior Redpanda doesn't replicate exactly. Every ticket reaches a named senior engineer who already knows your cluster topology.

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

Planning a build, upgrade or migration instead? See AceMQ Redpanda 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

Incident Triage

Problems we fix every week on Redpanda

Brokers, partitions and clients that behave unexpectedly, listed with the rpk output, Raft state or disk metric our engineers read first.

Common Redpanda production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Local disk fills although tiered storage is enabledTiered storage uploads closed log segments to object storage, but local retention is a separate setting. We check retention.local.target.bytes and retention.local.target.ms against ingest rate, the upload backlog, object store errors (credentials, bucket policy, throttling by the provider), and the size of the local cache set by cloud_storage_cache_size. If uploads lag, the local log grows until the disk alarm fires. We compare redpanda_storage_disk_free_bytes with the upload metrics, fix the upload path, and set sane space-management thresholds. Tiered storage is an Enterprise feature (Redpanda licence page), so we also confirm the licence is loaded.
Partition leadership flaps between brokersFrequent leadership changes show in redpanda_raft_leadership_changes and in producer latency. Causes: a reactor stall on a busy core, a slow disk making heartbeats late, a network path with loss, or noisy neighbours on shared cloud instances. We check the log for "Reactor stalled" messages, run rpk redpanda tune checks and rpk redpanda mode production settings, review CPU pinning and redpanda.smp and memory settings, and test the network with real packet sizes. Where leadership should live on certain brokers (rack or zone), leader pinning is an Enterprise feature.
Consumer group rebalances repeat and throughput collapsesGroup coordinator behaviour is Kafka's protocol, so the usual causes apply: session.timeout.ms and max.poll.interval.ms too tight for the handler, pods restarting, static membership not used, cooperative rebalancing not enabled. We read rpk group describe for member churn and lag, then the client configuration.
A Kafka client works on Kafka and misbehaves on RedpandaRedpanda implements the Kafka protocol, and client libraries mostly work unchanged, but the edge cases are in the details: unsupported or partially supported APIs, transaction and idempotence defaults, acks semantics on a mixed estate, and admin-client calls. We test the client against the cluster, identify the protocol call that differs, and either configure around it or change the client version.
Throughput is far below what the hardware should deliverRedpanda is built to saturate cores and NVMe. When it does not, we look for under-provisioned cores, a disk not in XFS or not tuned, cloud volumes with low IOPS caps, small batches from producers (linger.ms and batch.size), too many partitions per core, and redpanda_cpu_busy_seconds_total skewed to one shard. We run a benchmark with your message size and replication factor before changing anything.
Cluster balance drifts after a broker changeAdding or replacing a broker leaves partitions uneven. Continuous data balancing is an Enterprise feature; without it, balancing is by rpk cluster partitions moves. We plan the moves so they do not saturate the network during peak.
Brokers will not rejoin after a restart or upgradeCheck the seed servers, advertised addresses, TLS certificate rotation and cluster ID file. On Kubernetes, check the Redpanda Operator or Helm chart values, the StatefulSet's volume binding and the node's resource availability. A rolling upgrade should be one broker at a time with rpk cluster health clean between steps.
Migration from Kafka: producers or consumers stop after cutoverOffsets, consumer group state, schema registry IDs, ACLs and quotas do not move on their own. We use a mirroring approach, verify offsets and group commits, and keep a rollback until consumers have processed through the cutover point.

A written analysis follows each P1, naming the broker, topic or client setting involved.

Leaders flapping or a broker disk filling? Request a quote and a Redpanda engineer answers within an hour.

Contact Us

Deployment coverage

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

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Self-managed Redpanda Community EditionIncident response, tuning, upgrade planning, topic and consumer design, capacityThe community edition has no vendor support commitment in the documentation we readFeatures that require an Enterprise licence are not available without one
Self-managed Redpanda Enterprise EditionThe same, including Enterprise features once licensed: tiered storage, continuous data balancing, leader pinning, RBAC and audit loggingRedpanda supports its Enterprise product; its pricing page lists a 24x7 helpdesk with SLAs (page does not say for which deployments)A third party cannot ship a patched Redpanda binary
Redpanda Cloud (BYOC and Dedicated)The Kafka-API layer: topics, consumers, clients, schemas, connectors, capacity adviceRedpanda operates the cloud control and data plane; its pricing page lists a 99.99 percent uptime SLA for BYOC and 99.9 percent for ServerlessPlatform faults in Redpanda's control plane
Redpanda on Kubernetes (Operator, Helm)Operator and chart settings, storage and node behaviour, rolling upgrades, disruption budgetsRedpanda for its operator as a productCluster control-plane faults
Bare metal and on-premisesHardware, NVMe, XFS, kernel and rpk redpanda tune reviewRedpanda for the productHardware faults outside the agreed scope
Tiered storage to S3, GCS or AzureUpload path, cache sizing, retention settings, read-back checksThe object store provider supports the storeProvider outages
Air-gapped and no-outbound clustersSame scope inside your controlsNot applicableAnything needing outbound access
Mixed Kafka and Redpanda estatesBoth engines under one contract, client behaviour differences, migration planningEach vendor for its productNone specific

Support options

Who provides enterprise support for Redpanda? Redpanda and independent support compared

Redpanda Data sells support with its Enterprise Edition and Redpanda Cloud. The Community Edition is under the Redpanda Business Source License and carries no support commitment in the documentation. Independent support from AceMQ covers the Kafka-API behaviour and operations of the cluster on any edition, and one contract also covers the Kafka clusters many Redpanda users still run.

Redpanda Data (Enterprise Edition, Cloud)
AceMQ independent support
What it coversRedpanda product and its cloud service
What it coversRedpanda clusters of any edition, plus Kafka, RabbitMQ and the clients and pipelines around them
HoursPricing page lists "24x7 helpdesk with SLAs"
Hours24/7 across Americas, EMEA and APAC
Response targetsNot stated on the pages we read:
Response targetsResponse targets from 15 minutes, by plan
LicenceCommunity Edition under the Redpanda Business Source License. Enterprise features include tiered storage, continuous data balancing, leader pinning, RBAC, audit logging, Iceberg topics, whole cluster restore and shadowing
LicenceWe support the edition you run and tell you plainly when a feature needs an Enterprise licence
Product defectsRedpanda fixes and ships its own binary
Product defectsWe diagnose, gather evidence and work the escalation with Redpanda; we cannot patch the binary
Root cause analysisPer Redpanda's terms
Root cause analysisWritten root cause analysis on every P1
PriceSet by Redpanda (not on the pages read)
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour
Kafka neutralityRedpanda
Kafka neutralityWe support Kafka at the same depth, so the Kafka versus Redpanda advice is not steered

Dated sources: Redpanda pricing page, redpanda.com/pricing, read 17 November 2026; Redpanda documentation "Redpanda Licenses and Enterprise Features", docs.redpanda.com, read 17 November 2026.

What's Included

Everything in your Redpanda support contract

Core tuning, tiered storage, client compatibility, capacity and Kafka cutovers are covered under one agreement, for self-managed and Cloud clusters.

  • 01

    Emergency Incident Response

    A broker runs low on disk, leadership flaps cluster-wide, or producers stop flowing. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with direct 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 config or code change that prevents recurrence.

  • 03

    Seastar & Core Tuning

    Thread-per-core allocation, partition-to-core alignment, and tiered storage retention tuned against your actual hardware and throughput profile — not generic defaults.

  • 04

    Client Compatibility Advisory

    Testing and guidance on which Kafka client behaviors Redpanda replicates exactly and which need adjustment, before those gaps surface as a production incident.

  • 05

    Capacity & Storage Reviews

    Quarterly reviews of tiered storage upload lag, local disk headroom, and partition growth so you size ahead of demand rather than reacting to a full disk.

  • 06

    Kafka Migration Support

    Migration planning and execution from Kafka to Redpanda, including client compatibility testing, protocol validation, and canary cutover with rollback plans.

Why AceMQ

Why Redpanda users choose AceMQ

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your cluster topology, your partition layout, and which client libraries you run — so a P1 starts with diagnosis, not twenty minutes of explaining your environment.

  • No Tier-1 Triage Layer

    You reach a senior Redpanda engineer directly by phone, email, or Slack. No help desk collecting information to pass along, no escalation approval process standing between you and someone who can fix it.

  • We Know Where Redpanda and Kafka Diverge

    The Kafka-API compatibility is real but not total. We know precisely which broker behaviors, admin API edge cases, and transactional semantics differ, which matters more when your client libraries assume Kafka specifics.

  • Genuine Follow-the-Sun Coverage

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

  • Proactive, Not Just Reactive

    Quarterly health checks on tiered storage lag and core utilization, plus shared intelligence across our support base. When a version-specific issue surfaces on one customer's cluster, every affected customer hears about it before it reaches their production.

  • Honest About the Kafka Comparison

    We won't oversell operational simplicity as a reason to migrate if your actual pain points are elsewhere. We diagnose whether Redpanda genuinely solves your specific Kafka operational burden before recommending a migration.

Where Redpanda runs under our care

Self-managed clusters on bare metal and Kubernetes, Redpanda Cloud, and mixed estates running Kafka and Redpanda together.

  • Redpanda Cloud (BYOC & Dedicated)
  • Self-managed Redpanda clusters
  • AWS (EC2, EKS)
  • Google Cloud (GKE)
  • Microsoft Azure (AKS)
  • Kubernetes & OpenShift
  • Bare metal & on-premise
  • Tiered storage to S3/GCS
  • Air-gapped / no outbound access
  • Mixed Kafka + Redpanda estates

Version coverage

Versions we support

Versions we support
VersionSupported by AceMQ
Redpanda 26.2Yes
Redpanda 26.1Yes
Redpanda 25.3Yes
Redpanda 25.2 and olderAsk at scoping; we plan the move to a current line

Source: Redpanda supported versions page (support.redpanda.com), as used by the existing version checker on the page; read by the previous page build on 19 October 2026. Components: Redpanda broker, Redpanda Console, Redpanda Connect, Redpanda Operator and Helm charts, rpk.

In practice

Sizing questions we ask before a Redpanda cluster goes to production

Because Redpanda gives each core its own shard, sizing mistakes show up as skew, not as a general slowdown. These are the questions we put to a team, and the reason for each.

How many cores per broker, and how many partitions per core? Partitions are spread across cores. Too many partitions per core increases Raft heartbeat and memory overhead and slows leader elections after a restart. Too few leaves cores idle. We compare your partition count with the core count and the target throughput, and suggest the headroom to leave for growth.

What is the disk, and is it tuned? Redpanda is designed for local NVMe with XFS. Network-attached volumes with low IOPS caps or burst credits behave well in a test and badly in a sustained load. We run a disk benchmark with rpk tooling and the tuners (rpk redpanda tune) before sign-off, and record the result.

What replication factor and what acks? A replication factor of 3 is typical for production. acks=all waits for a Raft majority. Mixed settings across producers explain much of the "it was fast in testing" variance. We check the producers against the topic's replication and the cluster's failure domains (rack awareness).

What is the retention plan, local and tiered? Local retention should be sized to the longest consumer outage you want to ride out from local disk. Tiered retention extends history in object storage. Setting the local target too high fills disks; too low forces reads from object storage during recovery. We size both from ingest rate and recovery needs.

How do clients connect, and what do they assume? Advertised addresses matter for clients inside and outside the cluster network. TLS and SASL settings, and the client's metadata refresh interval, decide how it behaves when a broker restarts. We test a rolling restart with real clients.

Who watches the cluster, and what pages them? We help set the first alerts: unavailable partitions, disk free, under-replicated partitions, leadership change rate, consumer lag, and tiered storage upload backlog.

Escalation Path

Your first hour of a Redpanda outage

A cluster losing partition leaders is time-sensitive. The person answering already understands how Redpanda differs from Kafka under load.

  1. From 15 min (by plan)first responseEmergencyProduction outage: a partition group has lost quorum, brokers will not start, or producers cannot write
  2. 1 hourfirst responseCriticalSerious degradation: leadership moving between brokers, repeated consumer group rebalances, local disk close to full
  3. 4 hoursfirst responseHighThroughput well below hardware capability, unbalanced partitions after scaling, clients misbehaving against Redpanda
  4. Next Dayfirst responseStandardTopic and retention design, tiered storage setup, sizing, upgrade steps and Kafka migration planning

Targets scale with your plan, so lost quorum is handled before a tuning question.

Need a named Redpanda engineer who knows your topology? Ask for a quote or send a message.

Contact Us

Pricing

What does AceMQ Redpanda support cost?

Redpanda support usually lands between $24,000 and $72,000 a year. Price depends on the number of brokers and clusters, whether tiered storage and Cloud are used, how much Kafka migration work is planned, and your response plan.

Prices in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. A combined contract with Kafka or other platforms can earn a discount.

Support In Practice

Redpanda streaming problems we have solved

Redpanda 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.

  • Support

    Redpanda Production Support

    Healthcare Analytics Provider

    Named-engineer 24/7 support for Redpanda clusters covering node recovery, consumer lag incidents, upgrades, and client-side failures.

    RedpandaApache KafkaKubernetes
  • Remediation

    Redpanda Broker Latency Remediation

    Online Gaming Platform

    Resolving produce and consume latency spikes traced to Raft leadership imbalance, disk saturation, and partition distribution across brokers.

    RedpandaKubernetesApache Kafka
  • Assessment

    Redpanda Tiered Storage Assessment

    Connected Device Platform Provider

    Designing tiered storage for long retention so historical data lives in object storage without local disk dictating how long you can keep it.

    RedpandaApache KafkaKubernetesApache Spark
All use cases

Support options

Four tiers of Redpanda support.

AceMQ offers Redpanda support in four tiers, 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 disk, leadership and CVE problems first, managed Redpanda on your own infrastructure, and fully managed Redpanda on AceMQ infrastructure. Self-managed clusters and, above the managed layer, Redpanda Cloud are covered in all four.

  • Tier 1

    Redpanda 24/7 Support & Incident Management

    Your platform team runs brokers, we step in

    Best for: Streaming teams that operate Redpanda themselves and want a senior engineer for leadership, disk or client problems.

  • Tier 2

    Redpanda 24/7 Support with Proactive Monitoring

    Scheduled capacity and storage reviews

    Best for: Teams that want disk growth, partition balance and core usage checked before traffic growth exposes limits.

  • Tier 3

    Managed Redpanda on Your Infrastructure

    We operate Redpanda within your own estate

    Best for: Organizations bound to keep brokers on their own hosts or cloud account who still want upkeep handled by AceMQ.

  • Tier 4

    Fully Managed Redpanda on AceMQ Infrastructure

    AceMQ runs your Redpanda cluster as a service

    Best for: Teams that want a Kafka-compatible stream platform without staffing its operation themselves.

FAQ

Redpanda support questions

Still have questions about Redpanda? Email an Expert

Who provides enterprise support for Redpanda?

Redpanda Data supports its Enterprise Edition and Redpanda Cloud. Community Edition users have no vendor support commitment in the documentation. Independent providers such as AceMQ support Redpanda on any edition, 24/7 with response targets from 15 minutes, by plan. A senior engineer joins the bridge, and a written root cause analysis follows every P1.

What does 24/7 Redpanda support cover with AceMQ?

Incident response around the clock, root cause analysis on every P1, and the standing work around it: tiered storage health, leadership and Raft stability, partition balance, client compatibility, upgrade planning and capacity reviews. One contract can span Redpanda, Kafka and RabbitMQ.

Why does a Redpanda broker's disk fill when tiered storage is on?

Local retention is separate from tiered retention, and segments only leave the disk once they have uploaded. If uploads lag or fail, or local retention is set larger than the disk allows, the local log grows. We check the upload backlog, object store errors and retention.local.target.* settings.

What causes leadership flapping on Redpanda?

Late heartbeats, usually from a stalled core, a slow disk or a lossy network. The log shows reactor stalls. We check tuning, core allocation and the network, and review whether instances are sharing noisy hardware.

Can you fix a Kafka client that behaves differently against Redpanda?

Yes. We reproduce the call, identify the protocol feature or default that differs, and either change client configuration or version. Redpanda implements the Kafka API, and edge cases are in transactions, idempotence and admin calls.

What is Redpanda, and how does it differ from Apache Kafka?

Redpanda is a Kafka-API-compatible streaming platform written in C++ on Seastar, with Raft per partition and no JVM or ZooKeeper. The operational profile differs: cores and disk matter more, and tuning is rpk based. Choose by workload and team skills; we support both.

Which Redpanda features need an Enterprise licence?

According to Redpanda's licensing documentation (read 17 November 2026), Enterprise features include tiered storage, continuous data balancing, leader pinning, RBAC, audit logging, remote read replicas, whole cluster restore and shadowing. Check each feature against your licence before relying on it.

We are migrating from Kafka to Redpanda. Can you help?

Yes. We inventory topics, ACLs, quotas and clients, plan mirroring and offset verification, and keep a rollback until consumers have processed through the cutover point. See the existing Redpanda use cases linked below.

Do you support Redpanda Cloud as well as self-managed?

Yes. On Redpanda Cloud we support the Kafka-API layer: topics, consumers, clients, schemas and connectors. Redpanda operates the platform. On self-managed clusters we support the whole stack from rpk tuning to the broker.

Can AceMQ help with Redpanda just for a Kafka migration?

Yes. A migration plan, a cutover weekend or a client compatibility review can be scoped as its own project. Many teams then move to an annual agreement so the engineers who did the cutover stay available around the clock afterward.

How much does Redpanda support depend on cluster size?

Contracts generally run $24,000 to $72,000 a year (USD). Broker and cluster count matter, as do tiered storage, Redpanda Cloud versus self-managed, any Kafka-to-Redpanda migration, and the response plan you pick. Tell us about the cluster and we send a quote within 1 hour.

Let's talk

Your Redpanda Cluster Shouldn't Depend on Nobody Touching It

Tell us your Redpanda edition and where it runs. We reply to quote requests within 1 hour.

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

Production incident right now?Email a Redpanda Architect