Redis support

Independent Redis Support Services for Open-Source Redis, Valkey and Redis Enterprise

Last reviewed by Tyler Eastridge

AceMQ provides independent Redis support services, 24/7 across Americas, EMEA and APAC, for self-managed Redis, Valkey, ElastiCache, Azure and Redis Enterprise, with response targets from 15 minutes, by plan. The same engineers cover open-source Redis, Valkey and Redis Enterprise, so your support stays the same if you move between them. Most calls start with one of three problems: latency spikes with no traffic cause, memory climbing toward maxmemory, or a failover that left clients writing to the old primary.

24/7 support for open-source Redis, Valkey, Redis Enterprise, ElastiCache and Azure, with response targets from 15 minutes, by plan. Senior engineers handle latency spikes, eviction storms and failed failovers, and every ticket reaches a named engineer. Quote requests get a reply within 1 hour.

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

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

One support desk

One support desk for every Redis you run, 24/7 across Americas, EMEA and APAC

AceMQ supports open-source Redis, Valkey, Redis Enterprise and the managed services (Amazon ElastiCache, Azure and Google Cloud Memorystore) under one contract, 24/7 across Americas, EMEA and APAC. Response targets start at 15 minutes, by plan, and quote requests get a reply within 1 hour.

  • Open-source Redis and Valkey

    Self-managed on VMs, bare metal or Kubernetes, standalone, Sentinel or Cluster, on the version you run.

  • Redis Enterprise

    Operations, tuning and failover for Redis Enterprise deployments. Product defects in the commercial distribution still go to the vendor, and we work that escalation alongside you.

  • Managed Redis services

    ElastiCache, MemoryDB, Azure Cache for Redis, Azure Managed Redis and Memorystore, worked from parameter groups, event logs and engine metrics where there is no shell access.

Which option fits depends on where Redis runs and whether you need a vendor licence or an engineer. Redis Enterprise support vs community support

Incident Triage

Redis problems we fix every week

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

Common Redis production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Latency spikes every few hours, correlating with nothing in app trafficSynchronous fork stalls from RDB snapshots or AOF rewrite, whether appendfsync is set to always and fighting disk fsync latency, and transparent huge pages — THP being enabled is the classic hidden cause and shows up as multi-hundred-millisecond pauses.
Redis using far more memory than the sum of key sizes suggestsused_memory against used_memory_rss for fragmentation, then the encoding of your large collections. A hash that crosses hash-max-listpack-entries converts to a full hashtable and can multiply its footprint several times over with no application change.
Commands intermittently timing out under normal loadSLOWLOG for O(N) commands on the single-threaded command loop. One KEYS, one unbounded SMEMBERS on a large set, or a Lua script iterating a big collection blocks every other client for its full duration.
Keys disappearing before their TTL, cache hit rate collapsingmaxmemory-policy against actual working set. Under allkeys-lru Redis evicts to stay under maxmemory using approximate sampling, so hot keys can be evicted while cold ones survive if maxmemory-samples is left at the default.
Replica falls out of sync and triggers a full resync repeatedlyrepl-backlog-size against replication lag during peak write volume, plus client-output-buffer-limit for the replica class. A replica disconnected longer than the backlog holds cannot do a partial resync and forces a full RDB transfer, which causes the next stall.
Sentinel promoted a new primary but the application kept writing to the old oneWhether the client library is Sentinel-aware or holds a cached direct connection, and whether min-replicas-to-write is set. Without it the demoted primary keeps accepting writes until it is reconfigured, and those writes are lost on reconnection.
Cluster returning CLUSTERDOWN or MOVED loops after a reshardingSlot coverage across the shard map and any slots left in migrating or importing state from an interrupted reshard. A single uncovered slot takes the whole cluster down by default under cluster-require-full-coverage.
ElastiCache node degraded during a maintenance window or scaling eventEngine CPU rather than host CPU, SwapUsage, and whether the reserved-memory-percent leaves enough headroom for a fork. ElastiCache exposes no direct shell access, so we work from the parameter group, the event log, and the metrics that actually reflect the command loop.

Every P1 closes with a written root-cause analysis.

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

Contact Us

Coverage

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

AceMQ supports the Redis you run, on the version you run, wherever it runs. The table shows what we cover, what the platform or product vendor covers, and what neither of us covers. One contract can span several rows.

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Self-managed open-source Redis (VMs, bare metal, Sentinel or Cluster)24/7 incident response, written root cause analysis on P1s, memory, eviction and latency work, persistence and replication, failover design, CVE advice for your version, upgrade planningNo vendor contract comes with the open-source build; community channels have no response commitment. Redis support packages attach to Redis Software licences (Redis Software Support Policy, updated 1 November 2026)Your application code and data model decisions are reviewed, not rewritten; hardware and OS faults outside the agreed scope
Valkey (7.2, 8.x and later)Same scope as open-source Redis, including where Valkey behaviour has diverged from Redis, and Redis-to-Valkey migration planningValkey is a Linux Foundation project under BSD-3-Clause; it has no vendor support contract (valkey.io, as checked 26 October 2026)Features that exist only in a cloud vendor's Valkey build
Amazon ElastiCache and MemoryDBThe Redis layer on the service: parameter groups, eviction policy, key design, client timeouts, memory headroom, upgrade and engine-change planning. We work from the event log, parameter groups and engine metrics because there is no shellAWS runs and supports the service itself: provisioning, node replacement, maintenance and the engine versions it offers (ElastiCache engine versions page, read 17 November 2026)AWS platform faults; engine builds only AWS ships; limits set by the service
Azure Cache for Redis and Azure Managed RedisThe Redis layer: memory, eviction, client behaviour, connection handling, and migration planning between Azure Cache for Redis, Azure Managed Redis and Redis or Valkey you run in your own subscriptionMicrosoft supports the Azure services and owns their roadmap and retirement dates (Microsoft Learn retirement FAQ, updated 18 August 2026)Azure platform faults; features Azure Managed Redis does not offer
Redis Enterprise Software (self-hosted)Incident response alongside your team, configuration and capacity review, upgrade planning, and the escalation to Redis when the cause is in the productRedis supports Redis Software under its package terms, including product defects and fixes (Redis Software Support Policy, updated 1 November 2026)A third party cannot ship a patched Redis Enterprise binary; product defects stay with Redis and we work that escalation with you
Redis on Kubernetes (operators, StatefulSets, OpenShift)Pod and storage behaviour as it affects Redis: persistence on PVCs, failover and client reconnects when pods move, resource limits against fork and memory overhead, upgrade orderingThe Kubernetes distribution vendor supports the platform; Redis Enterprise for Kubernetes has its own support lifecycle set by Redis (Redis Software product lifecycle page, read 17 November 2026)Cluster control-plane faults; operators that are not supported by their maintainers

Sources, read 17 November 2026 unless dated: redis.io/legal/software-support-policy/, redis.io product lifecycle, valkey.io, docs.aws.amazon.com (ElastiCache engine versions), learn.microsoft.com (Azure Cache for Redis retirement FAQ).

Your options

Who provides enterprise support for Redis? Redis Inc. and independent support compared

Redis Inc. sells support packages for Redis Software, its commercial product. Open-source Redis and Valkey have no vendor contract, so enterprise support for them comes from an independent provider or your own team. The right choice follows what you run, not who owns the roadmap.

Redis Inc. support (Redis Software)
AceMQ independent support
What it coversRedis Software, the commercial product licensed from Redis Inc. The package is set by total annual Software fees
What it coversOpen-source Redis, Valkey, and Redis Enterprise deployments, plus the Redis layer on ElastiCache, MemoryDB and Azure
PackagesBasic, Developer, Business, Enterprise, Premium Enterprise
PackagesOne contract; plan set by SLA, scope and deployment
HoursBasic and Developer: business hours. Business, Enterprise, Premium Enterprise: 24x7 technical and phone support
Hours24/7 across Americas, EMEA and APAC
P1 first responseBusiness 1 hour; Enterprise 30 minutes; Premium Enterprise 15 minutes. Response times apply to production databases only
P1 first responseResponse targets from 15 minutes, by plan
Technical account managerEnterprise: one, only if annual Support Services spend is at least $20,000 USD. Premium Enterprise: one, plus a second at $150,000 USD or more
Technical account managerSenior engineers assigned to your account
Root cause analysisP1 and P2 tickets, Enterprise package and above
Root cause analysisWritten root cause analysis on every P1
PriceSet by licence fees and package; see the Redis pricing page
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour
Product defectsRedis Inc. can fix and ship its own binary
Product defectsWe diagnose, work the escalation with Redis, and cannot ship a patched Redis Enterprise binary
Open-source Redis and ValkeyNot part of a Redis Software package
Open-source Redis and ValkeyCovered

Sources: Redis Software Support Policy (redis.io/legal/software-support-policy/), last updated 1 November 2026; Redis pricing (redis.io/pricing/). Both read 17 November 2026. If you need Redis Enterprise features such as active-active geo-distribution, buy the licence from Redis Inc.; a support contract for the build you run is a separate decision, and many estates do both.

Something changed?

Three changes are moving Redis estates

Each guide says what changed, who it affects and what to decide first. Tell us what you run and we reply to quote requests within 1 hour.

What's Included

Redis support services

Redis support services from AceMQ are a 24/7 contract for production Redis and Valkey: incident response, a written root cause analysis on every P1, latency and memory work, failover review, security advice and upgrade planning, with no per-ticket charges.

  • 01

    Emergency Incident Response

    Redis unresponsive, a failover that stranded clients, or a cluster with uncovered slots. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis & Health Checks

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the specific configuration, data model, or Redis client change that prevents recurrence. Scheduled health checks assess the same surface before it becomes an incident.

  • 03

    Redis Performance Tuning

    maxmemory policy selection, fragmentation and encoding thresholds, THP and kernel settings, persistence strategy, and Redis client connection pool sizing tuned against your actual command mix and throughput.

  • 04

    Data Model Review

    Key design, collection sizing, TTL strategy, and where a Sorted Set, Stream, or Hash is the wrong structure for the access pattern. Most Redis performance problems are data model problems wearing a config costume.

  • 05

    Security & CVE Advisory

    ACL design, TLS configuration, protected-mode and bind auditing, Lua sandbox exposure review, and proactive alerts for CVEs affecting your exact Redis or Valkey version with tested upgrade paths.

  • 06

    High Availability, Upgrades & Cluster Deployment

    Sentinel and Cluster topology design, resharding without downtime, major version upgrades, and migration between self-managed, ElastiCache, Azure Cache, and Redis Enterprise with verified key parity.

Want AceMQ to take this off your team's plate? Tell us about your Redis 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 key patterns, your persistence choice, and your failover topology — so a P1 call starts with diagnosis instead of you describing your setup while latency climbs.

  • No First-Line Triage Layer

    You reach a senior Redis 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 SLOWLOG and a LATENCY DOCTOR report.

  • Data Model, Not Just Config

    Vendors tune parameters. A large share of Redis incidents trace to a single unbounded collection, a missing TTL, or an O(N) command on the hot path — and no amount of maxmemory tuning fixes those. We review the access pattern, not just redis.conf.

  • 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 health checks covering memory headroom, fragmentation trend, big-key growth, and eviction rate — so you resize before an eviction storm rather than after one takes your cache hit rate to the floor.

  • Managed Redis, Fully Covered

    ElastiCache, MemoryDB, Azure Cache, and Memorystore remove node management but leave you every problem that causes real incidents. We support managed Redis as a first-class environment, working from parameter groups and metrics when shell access does not exist.

We support Redis 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 ElastiCache for Redis
  • Amazon MemoryDB
  • Azure Cache for Redis
  • Azure Managed Redis
  • Google Cloud Memorystore
  • Redis Enterprise & Redis Cloud
  • Valkey deployments
  • Kubernetes & OpenShift operators
  • Redis Sentinel topologies
  • Redis Cluster (sharded)
  • Bare metal & on-premise
  • Air-gapped / no outbound access

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

Contact Us

Version coverage

Redis versions we support

Redis Open Source has two release types. Extended releases get security updates and critical bug fixes for five years after release; standard releases get them for six months after the next minor version ships.

Redis versions we support
Redis versionRelease typeUpstream end of lifeAceMQ coverage
Redis 8.4 to 8.10StandardNot yet set24/7 support
Redis 8.2Extended1 September 203024/7 support
Redis 8.0Standard1 December 202624/7 support and upgrade planning
Redis 7.4Extended1 December 202924/7 support
Redis 7.2Extended1 December 202924/7 support, plus CVE fixes backported through OSSeva
Redis 7.0Not listedPast end of life24/7 support, plus CVE fixes backported through OSSeva
Redis 6.2Extended1 April 202724/7 support, plus CVE fixes backported through OSSeva
Redis 6.0 and earlierNot listedPast end of lifeSupport and upgrade planning

Source: the Redis Open Source version management page, checked 6 October 2026. Valkey 7.2 and 8.x are supported the same way, including OSSeva CVE backports.

Who supports Redis

Commercial and third-party Redis support

Commercial Redis support comes from three places: Redis, the vendor, for its paid Redis Software and Redis Cloud; your cloud provider, for its managed service; and an independent third party such as AceMQ, for open-source Redis and Valkey on any infrastructure.

  • From the vendor

    Redis's software support policy covers paid versions of Redis Software, in support packages from business hours to 24x7. It does not cover open-source Redis that you run yourself.

  • From your cloud provider

    ElastiCache, Azure Cache for Redis, Azure Managed Redis and Memorystore are supported by their providers as services, up to the service boundary. Your application's use of Redis, and any cluster outside that platform, sit outside it.

  • From an independent third party

    Open-source Redis and Valkey have no vendor support contract attached. A third party such as AceMQ covers them on any infrastructure, with a named engineer and a written root cause analysis, for $24,000 to $72,000 a year (USD) by scope.

Source for the vendor package: Redis software support policy, read 17 November 2026. Providers compared side by side, with their published response times: Redis and Valkey support providers compared

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

Contact Us

Two dated changes

Redis license change and Azure Cache for Redis retirement: what changes for support

Two dated changes are moving Redis estates. Redis changed its license: Redis 7.4 moved to RSALv2 and SSPLv1, and Redis 8 added AGPLv3 as an option. Microsoft is retiring Azure Cache for Redis: the Enterprise tiers on 31 March 2027, Basic, Standard and Premium on 30 September 2028. AceMQ supports Redis and Valkey through either move.

  • Redis license change

    Redis 7.2 and earlier are BSD. Redis 7.4 is available only under RSALv2 or SSPLv1, and Redis 8 and later add AGPLv3 as a third option. It affects teams that must clear the license with legal before they pick a version. The decision is to stay on a Redis version you can license, or move to Valkey, the BSD-licensed Linux Foundation fork. AceMQ supports both.

  • Azure Cache for Redis Enterprise: 31 March 2027

    Microsoft retires the Enterprise and Enterprise Flash tiers on 31 March 2027, and migrates instances to Azure Managed Redis from 1 April 2027. It affects Azure teams on those tiers. The decision is Azure Managed Redis, or Redis or Valkey that you run yourself. AceMQ supports either, including in your own Azure subscription.

  • Azure Cache for Redis Basic, Standard and Premium: 30 September 2028

    Microsoft retires these tiers on 30 September 2028 and disables remaining instances from 1 October 2028. It affects every team still on them. The decision is the same two routes. Azure Managed Redis list prices by tier, and how to size one, are in our Azure Managed Redis pricing guide.

Dates are from Microsoft's Azure Cache for Redis retirement guidance, read 14 November 2026. Licenses are from redis.io/legal/licenses. Full terms and the licensing options: Redis licensing explained

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

Contact Us

Pricing in USD

What Redis support costs, in US dollars

AceMQ's Redis and Valkey 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 Redis, Amazon ElastiCache, Azure Cache and Redis Enterprise, with response targets from 15 minutes, by plan. Quote requests get a reply within 1 hour.

  • Redis or Valkey version

    Which Redis version, or Valkey 7.2 or 8.x, you run. It sets the upgrade and patch path the contract covers.

  • Where it runs

    Self-managed on VMs or Kubernetes, Amazon ElastiCache, Azure Cache, or Redis Enterprise.

  • Standalone, Sentinel or Cluster

    The topology, how many nodes, and which environments need cover.

  • Memory size and persistence

    Dataset size in memory, and whether you rely on RDB snapshots, AOF or neither.

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

Support is an annual contract, not priced per incident or per ticket. A quote needs the six things above: send them and the reply comes within 1 hour. AceMQ is a Leading Global Redis Partner, listed in the Redis partner directory. AceMQ in the Redis partner directory

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

Contact Us

Upgrades

Upgrading Redis: who can help us upgrade our Redis cluster?

AceMQ plans, rehearses and supports Redis upgrades, either alongside your team or as a scoped engagement where we do the work. We start from the version you run and the licence you can accept, then choose the shortest path that can be rolled back at every step.

An upgrade engagement covers a version and client inventory; a licence decision (Redis or Valkey); a staging rehearsal against your real command mix; replicas upgraded first, then a controlled failover; a rollback plan per step; and a written post-upgrade check of memory, latency and replication.

Redis upgrade paths AceMQ plans, with the dated vendor fact for each
You run todayMove toPath we planWhat we check firstDated vendor fact
Redis 6.2 (open source)Redis 7.2, then 8.x, or Valkey 7.2 or 8.xRehearsed step through 7.2 (BSD), then the targetClient library versions, ACL and command changes, persistence file compatibilityRedis lists security fixes for 6.2 until 1 April 2027 (redis.io version management, read 17 Nov 2026)
Redis 7.0 or 7.2Redis 8.x or Valkey 8.xDirect to the target after a staging rehearsalLicence choice, module use, client behaviour on the new majorRedis lists security fixes for 7.2 until 1 December 2029 (same page). Valkey continues from Redis 7.2.4 (Redis licensing explained)
Redis 7.4Redis 8.x (AGPLv3 option) or ValkeyIn-place to 8.x, or a migration to ValkeyWhether RSALv2 or SSPLv1 terms were reviewed; search and JSON module memoryRedis 7.4 is available under RSALv2 or SSPLv1 only (redis.io/legal/licenses/)
Redis 8.0Redis 8.2 or laterMinor upgrade on the same majorFork overhead and memory headroom on the newer buildRedis lists security fixes for 8.0 until 1 December 2026 and for 8.2 until 1 September 2030 (same page)
ElastiCache Redis OSS 4, 5 or 6ElastiCache for Valkey, or a newer engineEngine change planned per cluster, with a client reconnect testParameter group differences, replication group topology, maintenance windowAWS lists 31 Jan 2026 for Redis OSS v4 and v5 and 31 Jan 2027 for v6 as the last date of standard support, with an additional AWS charge after that (ElastiCache engine versions page, read 17 Nov 2026)
Azure Cache for Redis (Basic, Standard, Premium)Azure Managed Redis, or Redis or Valkey in your subscriptionMigration plan with key parity checkClustered-by-default behaviour, cross-slot commands, endpoint and credential changesRetires 30 Sep 2028; instances disabled from 1 Oct 2028 (Microsoft Learn FAQ, updated 18 Aug 2026)
Azure Cache for Redis Enterprise or Enterprise FlashAzure Managed Redis, or Redis or Valkey in your subscriptionMigration plan with key parity checkPort and endpoint changes, client cluster supportRetires 31 Mar 2027; instances disabled from 1 Apr 2027 (same FAQ)
Redis Software 6.2.x to 7.x or 8.xRedis Software 7.2 or later, then 8.xFollow Redis's supported upgrade matrix, with the intermediate stop it requiresDatabase versions bundled with the cluster versionRedis documents direct upgrades from 6.4.x to 8.0.2 to 8.0.10, and from 7.2.x to 8.2.x; 6.2.x and 6.0.x need an intermediate version (Redis Software product lifecycle page, read 17 Nov 2026)

Not sure which row you are in? Start with a Redis health check: it ends with an upgrade-readiness view and a ranked plan. If the question is Redis or Valkey, see Redis to Valkey migration.

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

Contact Us

Scope

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

A Redis support contract normally covers availability across standalone, Sentinel and Cluster, memory and eviction, replication and failover, persistence, client diagnosis and escalation with a response commitment. It usually excludes your application's use of Redis and the infrastructure beneath it, and the most disputed boundary is whether Redis is a cache or a datastore.

The full checklist, with the grey areas to settle before you sign, is in Redis Contract Checklist: What Is In, Out and Grey.

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

Contact Us

Incident response

Your first hour of a Redis outage

The first job is classification, because Redis is very often the symptom rather than the cause: is the instance reachable, is it memory pressure, did a failover complete, is replication healthy, or is the server fine and the client timing out. Getting that right in the first few minutes decides whether the next hour is productive.

The order of those checks, and what to set up before 3am, is in Redis Outage Response: The First 15 Minutes.

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

Contact Us

Escalation Path

Your first hour of a Redis outage

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

  1. From 15 min (by plan)first responseEmergencyProduction down: primary down, cluster failover failed, OOM eviction storm
  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 Redis, Valkey, ElastiCache 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 Redis, that is the engineer who already knows your Sentinel or Cluster 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 Redis? Get a quote or send us a message.

Contact Us

Pricing

What does AceMQ Redis support cost?

AceMQ Redis 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 ElastiCache, Azure Cache or Kubernetes).

What does AceMQ Redis 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

Redis problems we've already solved

Redis support and consulting work from AceMQ. Each card links to the full write-up: the Redis estate, what AceMQ diagnosed or changed, and the result.

1 / 6 case studies

All use cases

Support options

Four tiers of Redis support.

AceMQ offers Redis support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for Redis your team runs, proactive monitoring that finds memory, persistence and failover gaps first, managed Redis and Valkey on your own infrastructure, and fully managed Redis and Valkey on AceMQ infrastructure. Redis 6.2 to 8.x are covered, and CVE fixes for 6.2, 7.0 and 7.2 are backported through OSSeva.

  • Tier 1

    Redis 24/7 Support & Incident Management

    You run it, we back you up

    • Fork stalls, THP and fsync latency traced with LATENCY and SLOWLOG
    • Sentinel and Cluster failover problems fixed on the server and the client
    • ElastiCache, Azure and Memorystore incidents worked from parameter groups and metrics

    Best for: Teams that run Redis, Sentinel or Redis Cluster themselves, or on a managed service, and need senior cover at 3am.

  • Tier 2

    Redis 24/7 Support with Proactive Monitoring

    You run it, we watch it with you

    • Memory headroom, fragmentation, big keys and eviction rate reviewed against real traffic
    • Failover tested with real clients attached, on Sentinel or Cluster
    • RDB and AOF restores tested on real data, not just backup job status

    Best for: Estates where an unrestored backup or an untested failover is an outage with a date still to be set.

  • Tier 3

    Managed Redis on Your Infrastructure

    We run it in your cloud or data centre

    • Memory, eviction, replication and fork-time monitoring with paging
    • Sentinel and Cluster failover tested after every change
    • Patching and upgrades replica-first, rehearsed before production

    Best for: Regulated teams that must keep Redis inside their own boundary but do not want it on their own rota.

  • Tier 4

    Fully Managed Redis on AceMQ Infrastructure

    We host it and run it, as a service

    • Topology sized from your keyspace, throughput and durability need
    • Backups restored and timed, not only taken
    • Version and licence changes handled as planned work

    Best for: Teams that want Redis to stop being their problem.

Who does what in each AceMQ Redis 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 Redis 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 Redis

Everything else AceMQ does for Redis.

Support is one part of what AceMQ does for Redis. 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

Redis support questions

Still have questions about Redis? Email an Expert

Can a third party support Redis, or does it have to be Redis Ltd?

A third party can support it. Open-source Redis and Valkey have no vendor support contract attached, so production support comes from an independent provider or your own team. AceMQ supports open-source Redis, Valkey, Redis Enterprise deployments and the managed services (ElastiCache, Azure Cache for Redis, Memorystore) under one contract. What a third party cannot do is ship a patched Redis Enterprise binary; product defects in the commercial distribution still go to Redis Ltd, and we work that escalation alongside you.

What does a Redis support contract cover?

A Redis support contract with AceMQ covers 24/7 incident response with response targets from 15 minutes, by plan, named senior engineers rather than a ticket queue, written root cause analysis on every P1, latency and memory investigation, Cluster and Sentinel failover problems, persistence and backup review, security and CVE advisory, and upgrade or Valkey migration planning. It covers the Redis you run, on the version you run, wherever it is hosted.

Which companies offer Redis support?

Redis Ltd supports Redis Enterprise and Redis Cloud under its own subscriptions. The cloud platforms support their managed offerings — ElastiCache, Azure Cache for Redis, Memorystore — inside those platforms. Independent firms such as AceMQ support open-source Redis, Redis Stack and Valkey on any infrastructure: 24/7 cover, response targets from 15 minutes, by plan, and a named senior engineer for latency, memory, replication and failover problems. Which one fits depends on where Redis runs and whether you need a vendor licence or an engineer.

What is Redis used for, and where does it break in production?

Redis is an in-memory data store used for caching, session storage, rate limiting, queues, leaderboards, real-time data and increasingly as a vector store for AI retrieval. Its data structure primitives — strings, hashes, sorted sets, streams — are what let a single instance serve sub-millisecond reads at very high throughput. What breaks is rarely Redis itself: it is an eviction policy that does not match the access pattern, a key design that turns an O(1) lookup into an O(N) scan, a fork stall during snapshotting, or a failover the client library never noticed. Those are the failures a Redis support contract exists to cover.

Is Redis still open source, and what changed with the license?

It is again, with a caveat. Redis moved off the permissive BSD license in version 7.4 to a dual source-available model (RSALv2 and SSPLv1), which is what prompted the Valkey fork under the Linux Foundation. From Redis 8, Redis Open Source added the OSI-approved AGPLv3 as a third option, so Redis 8 and later are available under RSALv2, SSPLv1 or AGPLv3. Redis 7.2 and earlier remain BSD, and Valkey stays BSD. For teams running Redis internally, none of these licenses restricts use; the differences matter mainly to vendors embedding or offering Redis as a service. For most teams operating Redis internally the practical question is not the license but who patches your version when something is found in it. AceMQ supports both Redis and Valkey and will tell you plainly whether a migration is worth doing for your workload rather than assuming it is.

Why do Redis connection errors and timeouts happen when the server looks healthy?

Because the server usually is healthy. Connection errors on an otherwise idle Redis almost always trace to the client side: a connection pool sized below peak concurrency, a client library that has not refreshed topology after a failover and is still writing to a demoted primary, an idle timeout closing pooled connections underneath the application, or TLS handshake cost under connection churn. Diagnosing it means correlating client-side pool metrics against server-side connected_clients and rejected_connections rather than restarting the node and hoping.

What does a Redis health check include?

A Redis health check is an assessment of the running deployment rather than a checklist against documentation. It covers memory headroom and eviction behaviour under real traffic, key and data structure design, persistence configuration against your actual durability requirement, high availability topology and failover validation, client library and connection pooling configuration, security posture and CVE exposure for your version, and performance tuning opportunities visible in latency percentiles. You get written findings with severity, not a dashboard screenshot.

Can AceMQ support Redis for vector search and AI workloads?

Yes. Redis is widely used as a vector database for retrieval-augmented generation, where sub-millisecond similarity search sits on the critical path of every request. The operational profile is different from caching: index build cost, memory footprint per vector, and query latency under concurrent writes all become the constraint, and Redis Search behaviour under high-frequency writes is a failure mode we have diagnosed in production. The same support contract covers it.

What does AceMQ Redis support include?

Redis support covers 24/7 emergency incident response with response targets from 15 minutes, by plan, written root cause analysis on every P1, latency and memory tuning, data model review, security and CVE advisory, HA topology design, 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 ElastiCache and other managed Redis services?

Yes. We support Amazon ElastiCache and MemoryDB, Azure Cache for Redis and Azure Managed Redis, Google Cloud Memorystore, and Redis Enterprise alongside self-managed deployments. Managed Redis removes node provisioning but not the failure modes that cause incidents — eviction policy, key design, O(N) commands, fork stalls, and client-side failover handling all remain yours. We work from parameter groups, event logs, and engine-level metrics where shell access is not available.

How fast do you respond to a Redis production outage?

P1 emergencies — Redis unresponsive, a cluster with uncovered slots, a failover that stranded your clients — 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.

Our Redis latency spikes with no obvious cause. Can you find it?

Yes, this is one of the most common reasons teams call us. Unexplained latency in Redis is nearly always one of four things: a fork stall during RDB save or AOF rewrite, transparent huge pages inflating that fork's copy-on-write cost, an O(N) command blocking the single-threaded command loop, or disk fsync latency under appendfsync always. We isolate which using LATENCY, SLOWLOG, and kernel-level evidence rather than changing settings and watching.

Do you support Redis Cluster and Sentinel, or only standalone?

All three topologies. Cluster brings slot management, resharding, and cross-slot command constraints. Sentinel brings quorum sizing and the client-side awareness problem that causes split-brain writes to a demoted primary. Standalone with a replica has its own resync behavior. Each fails differently, and the right topology for you depends on your write volume and consistency requirements, not on which is newest.

Do you support Valkey and the post-fork Redis versions?

Yes. We support Valkey as well as Redis across licensing changes, including advising on whether a migration is worth doing for your workload. The operational failure modes are largely shared today, so the same diagnostic depth applies. Where behavior has genuinely diverged between forks, we will tell you specifically where rather than treating them as interchangeable.

Do you handle Redis backup, and can you actually restore from it?

Both, and the second half is the one that catches teams out. RDB snapshots and AOF each fail differently under load — RDB forks and can double memory on a write-heavy instance, AOF grows until rewrite and can leave you restoring hours of commands. We review which persistence mode fits your durability requirement, size the headroom the chosen mode actually needs, and test a restore against real data rather than assuming the file is good. Most estates we inherit have backups running and have never restored one; that is the gap worth closing before an incident finds it for you.

What does Redis disaster recovery look like, and how is it different from HA?

High availability keeps you running when a node fails: Sentinel or Cluster failover, replica placement, and how clients behave during the election. Disaster recovery is what happens when the whole environment is gone — cross-region replication, a documented recovery procedure, and an RPO and RTO you have measured rather than assumed. They are separate designs and a sound HA setup tells you nothing about recovery time. Support covers reviewing both, including the failover behaviour your client libraries actually exhibit, which is frequently where the real recovery time hides.

Do you audit Redis security and monitor it in production?

Yes to both. A security review covers ACLs and user separation, TLS configuration, whether the instance is reachable from anywhere it should not be, dangerous commands left enabled, and the protected-mode and bind settings that account for most exposed Redis in the wild. On monitoring, the signals that predict incidents are memory fragmentation ratio, eviction and expiry rates, replication lag, blocked clients and connection churn — not just whether the process is up. We define what to alert on and review what you already collect; on managed engagements we run it. Findings come as a written report with severity and remediation.

How do you fix Redis memory that keeps growing, or a suspected memory leak?

Start by separating real growth from fragmentation and from keys that never expire. We compare used_memory with used_memory_rss, check the fragmentation ratio, sample the keyspace for large keys and keys without a TTL, and look at client output buffers and replication backlog, which are common hidden consumers. True leaks in the Redis software are rare. The usual findings are an eviction policy that does not match the workload, a developer pattern that writes without expiry, or a big key that grew unnoticed. The fix is then a configuration change, an application change, or both, and we tell you which.

Can you help with Redis data migration, automation and upgrades?

Yes. Data migration between deployments, whether that is self-managed to a managed service, Redis to Valkey, or open source to Redis Software, is done with replication-based cutover so the application sees seconds of interruption, not a maintenance window. We also help teams automate the estate: Terraform and Helm for provisioning, a pipeline for configuration changes, and continuous checks on persistence, replication and memory headroom so problems surface before they page anyone. Version upgrades follow the same replica-first method and are rehearsed before production.

Do you support end-of-life Redis versions?

Yes. In Redis Open Source, version 7.0 and everything before 6.2 are past end of life, 6.2 is supported until 1 April 2027, and 7.2 and 7.4 until 1 December 2029. AceMQ supports the version you actually run and plans the upgrade. Where you need security patches on a version you cannot yet leave, AceMQ's OSSeva platform backports CVE fixes to Redis 6.2.x and 7.0.x, which stay BSD licensed.

What is the difference between Redis support and managed Redis services?

Support is an SLA over Redis your team runs: you hold the pager and call us when something breaks. Managed Redis services means AceMQ runs Redis or Valkey on your infrastructure or on AceMQ infrastructure, owning monitoring, patching, upgrades, failover, capacity and on-call. Teams that want to keep ownership choose support; teams that want Redis to stop being their problem choose managed services.

Who provides enterprise support for Redis?

Three groups do. Redis Inc. supports Redis Software and Redis Cloud under its own packages. AWS and Microsoft support their managed services (ElastiCache, MemoryDB, Azure Cache for Redis, Azure Managed Redis) inside their own platforms. Independent providers such as AceMQ support open-source Redis, Valkey and Redis Enterprise estates on any infrastructure, 24/7, with response targets from 15 minutes, by plan. Which one you need follows where Redis runs and whether you need a licence or an engineer.

What does 24/7 Redis support cover with AceMQ?

It covers incident response around the clock across Americas, EMEA and APAC, with response targets from 15 minutes, by plan. A senior engineer joins a live bridge for P1s such as a primary down, a failed cluster failover or an OOM eviction storm. Every P1 closes with a written root cause analysis. Tuning, security advice, failover design and upgrade planning sit under the same contract.

Redis Enterprise vs community support: which do we need?

Choose Redis Enterprise support if you run Redis Software and want the vendor to own product defects. Choose an independent contract if you run open-source Redis, Redis Stack or Valkey, because the vendor packages do not attach to those builds. Community channels carry no response commitment and nobody accountable at 3am. Estates running both usually keep the licence and add independent cover for the rest.

We need help upgrading our Redis cluster: who can do that?

AceMQ can, either alongside your team or as a scoped engagement. We inventory versions and clients, settle the licence question, rehearse in staging, upgrade replicas first, fail over under control and keep a rollback at every step. The version path table above shows the usual routes from Redis 6.2, 7.x and 8.0, from ElastiCache and Azure, and between Redis and Valkey.

Who supports Valkey, and can one contract cover Redis and Valkey?

Valkey has no vendor support contract, so support comes from independent providers. AceMQ covers Redis and Valkey under one contract, which matters when you are mid-migration and run both. The operational failure modes are largely shared today. Where behaviour has diverged we say so specifically rather than treating the two as interchangeable.

Who fixes an ElastiCache or Azure Redis problem: AWS, Microsoft or an independent provider?

The cloud provider fixes platform faults on its own service. An independent provider such as AceMQ works the Redis layer on top: eviction policy, big keys, O(N) commands, client pool sizing, failover handling and memory headroom. Most incidents on cloud-managed Redis sit in that layer. We work from parameter groups, event logs and engine metrics because shell access does not exist.

What happens to our Redis support when Azure Cache for Redis retires?

Your instances keep running until the retirement date for their tier: 31 March 2027 for Enterprise and Enterprise Flash, 30 September 2028 for Basic, Standard and Premium. Support continues through the move. We plan the migration to Azure Managed Redis, or to Redis or Valkey in your own subscription, and check key parity and client behaviour before cutover.

Does Redis support include Redis on Kubernetes?

Yes. We support Redis and Valkey on Kubernetes and OpenShift, including operator-managed and StatefulSet deployments. The work is the interaction between Redis and the platform: persistence on volumes, failover and client reconnects when pods move, resource limits against fork memory, and upgrade order. Cluster control-plane faults stay with your platform vendor.

What should a Redis support contract say about response times?

It should say what starts the clock, which severities get 24/7 cover and who answers. Redis Inc. publishes P1 first-response targets of 1 hour (Business), 30 minutes (Enterprise) and 15 minutes (Premium Enterprise), for production databases only. AceMQ targets start at 15 minutes, by plan. Ask whether a staging outage counts as a P1, because many contracts treat it as business-hours work.

Can we work with AceMQ on Redis without a long contract?

Yes. AceMQ works on Redis 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 Redis support or consulting cost?

Every AceMQ proposal is tailored to your requirements: your Redis 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 Redis is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.

Let's talk

A Cache Outage Shouldn't Take Your Application With It

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

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

Production incident right now?Email a Redis Architect

Get in Touch

Talk to a Redis 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.