Valkey Consulting & Support

Valkey Consulting for Upgrades, Clusters and Redis Migrations

Valkey consulting from AceMQ covers upgrades from 7.2 to 8.x and 9.x, Valkey Cluster and Sentinel design, Redis to Valkey migration and memory and latency tuning, led by senior engineers who also staff the 24/7 Valkey support rota. We also consult on Tanzu Valkey. Engagements are quoted per engagement.

A senior engineer, not an SDR. No sales sequence attached.

Fastest response target, by plan
15 min
On-call cover
24/7
AceMQ customers
160+
Years in business
10+

Without a rewrite of every client that talks to RedisFor production incident cover, see AceMQ Valkey 24/7 support.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

The Problem

Why teams call us about Valkey

Eight Valkey problems an AceMQ review starts from, from latency spikes to a migration nobody has tested. If one describes your week, that is where the review starts.

  1. 01

    Latency spikes that do not follow traffic

  2. 02

    Replicas keep doing full resyncs and each one forks the primary

  3. 03

    Memory is not full but the cluster is out of room

  4. 04

    A cluster resharding stalls with slots open on two nodes

  5. 05

    Clients exhaust connections after a failover

  6. 06

    Persistence stalls the primary during snapshots or rewrites

  7. 07

    A move from Redis to Valkey is planned and nobody has tested it

  8. 08

    Valkey 7.2 or 8.x estates need an upgrade path that has not been written down

A good fit if Valkey sits in front of a production database and you want one team that plans the upgrade, tests the failover and answers at night.

Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy Valkey.

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

Contact Us

How it breaks, and the fix

What happens to writes when Valkey reaches its memory limit?

Valkey keeps its dataset in memory, up to maxmemory. What it does at the limit is set by the eviction policy. With noeviction, writes are refused with an error and reads continue. With an eviction policy, keys are removed, and the choice of policy decides which ones, which may include keys the application needs.

One memory limit, one eviction policy

The application, Valkey memory, hot keys and the database

Illustrative
  1. Memory sits well below maxmemory, hot keys are served from memory and the database sees only misses.

  2. Memory reaches maxmemory. Writes are refused or useful keys are evicted, hot keys stop being served and every request falls through to the database.

  3. The limit is sized from measured data and fork headroom, the eviction policy matches how keys are used, and the hot keys stay in memory.

INFO memory shows it: used_memory against maxmemory, mem_fragmentation_ratio, and evicted_keys in INFO stats. A ratio far above 1 with an idle workload points at fragmentation and a ratio below 1 at swapping. valkey-cli --bigkeys and --memkeys find the single keys that dominate. The fix is rarely a bigger instance: it is a policy and expiry that match how the data is used, and headroom for the fork that snapshots and replication need.

Our Services

Valkey Consulting & Services

AceMQ runs five Valkey service lines: health check, upgrade planning, cluster and failover design, Redis to Valkey migration, and Tanzu Valkey. A senior engineer leads each one, and any of them can roll into 24/7 support.

  • 01

    Valkey Health Check

    The fixed-scope entry engagement: a written report on how your Valkey is configured and where it is exposed, which your team can act on with or without AceMQ.

    • Memory, fragmentation and eviction policy
    • Slow commands and big keys
    • Replication, backlog and persistence timing
    • ACL and TLS inventory
  • 02

    Upgrade Planning

    A written upgrade path across Valkey 7.2, 8.x and 9.x, planned per release notes and rehearsed against your command mix.

    • Version path per cluster
    • Replicas first, then a controlled failover
    • I/O thread and client behavior checks
    • Rollback at each step
  • 03

    Cluster and Failover Design

    Slot layout, shard and replica placement and failover that is tested with clients connected.

    • Cluster or Sentinel chosen from your workload
    • Resharding, including atomic slot migration on 9.0
    • cluster-node-timeout set from your network
    • Failover drill and runbook
  • 04

    Redis to Valkey Migration

    A stay-or-move review, then a migration with key-level validation and a rehearsed rollback.

    • Commands, Lua scripts, modules and clients inventoried
    • Snapshot compatibility tested before it is relied on
    • Replication cutover rehearsed
    • A plain answer when staying on Redis is the better call
  • 05

    Tanzu Valkey

    Architecture and licensing questions for Broadcom's Tanzu build of Valkey, where licensing through Broadcom is available in North America only.

    • Open-source or Tanzu build chosen from your support needs
    • Core and node sizing against the licence
    • Operations and upgrade paths
    • See the Tanzu Valkey pages for detail
  • Response targets from 15 minutes, by plan

    24/7 Valkey Support

    Named senior engineers on your account — response targets from 15 minutes, by plan, no ticket routing.

    • Response targets from 15 minutes, by plan
    • Named engineer, zero cold-start
    • Proactive CVE & health monitoring
    • Quarterly deployment reviews

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

Contact Us

24/7 Support

Valkey Support When It Matters Most

AceMQ Valkey support gives you an AceMQ engineer and response targets from 15 minutes, by plan, when writes are failing, 24/7, for Valkey and Redis estates.

  1. From 15 min (by plan)first responseEmergencyProduction down, messages not flowing, queue manager failure
  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 RabbitMQ, Kafka, Redis, PostgreSQL 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 RabbitMQ, the path runs to the core team.

    If needed
  4. After

    Written root-cause analysis

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

    Every P1

How Our Support Actually Works

Beyond SLAs — the model behind senior-only, zero-cold-start expert access.

  • Named Engineers on Your Account

    Every ticket is handled by a senior SME assigned to your account — not a pool of anonymous agents. Zero cold-start. No re-explaining your environment.

  • Live Escalation on Any Ticket

    Any ticket can be escalated to a live session with your named engineer via calendar booking. No gatekeeping, no approval required — direct access, always.

  • Proactive Risk Mitigation

    Quarterly health checks on your deployment plus shared intelligence from our support customers — we surface risks before they reach production.

  • Critical Bug & CVE Intelligence

    Proactive alerts on critical bugs and CVEs affecting your exact version, with version compliance monitoring so you're never caught off guard.

  • Commercial EOL Versions

    Commercial support for end-of-life Valkey versions, with security fixes backported through OSSeva, so the upgrade happens on your schedule rather than the community's.

How It Works

What actually happens next

An AceMQ Valkey engagement runs in four stages: a scoping call with a quote within 1 hour, a review, a written plan, then the work or a handover. Each stage ends in writing.

Quote within 1 hour

Scoping call and quote

A senior AceMQ engineer asks what you run: the Valkey version, standalone, Sentinel or Cluster, self-managed, Kubernetes or a cloud service, whether a Redis estate sits beside it, and what has prompted the question. A quote request is answered within 1 hour.

Scoped per estate

Review

Memory and fragmentation, slow commands and big keys, replication and backlog sizing, cluster slot health, persistence timing, client connections, ACL and TLS inventory, read from INFO output and your real workload. Findings are written down and your team keeps them.

Scoped per estate

Written plan

A recommendation in writing: the upgrade path per cluster in release-note order, the migration method per cluster where Redis is involved, and a rehearsal with key-level validation and a rollback.

Ongoing or fixed scope

Run the work or hand over

Changes staged replicas first, with a controlled failover and a rollback at each step. The work ends with runbooks for failover, eviction and persistence. You can stop there, add 24/7 Valkey support, or have AceMQ run the estate.

  • Written findings before any change
  • Changes staged and reversible, with a rollback plan
  • Your engineers in the room
  • Ad hoc engagements or an annual partnership

A senior engineer, not an SDR. No sales sequence attached.

Customer Success

Real Valkey Results

Typical Valkey engagements, described as scopes. Each card links to the full write-up.

1 / 6 case studies

  • Consulting

    Valkey 8 to 9 Upgrade Plan with a Replica-First Order

    Platform Engineering Team

    A typical consulting engagement for a team on Valkey 8.0 clusters: a written upgrade path to 9.x in replica-first order, rehearsed against the real command mix, with a rollback at each step.

    ValkeyKubernetesPrometheus
  • Consulting

    Valkey Session Cache Memory Sizing and Eviction Review

    Platform Engineering Team

    A typical consulting engagement for a Valkey session cache that refuses writes or evicts live sessions near its memory limit: a review of maxmemory, eviction policy, big keys and fork headroom.

    ValkeyLinuxPrometheus
  • Remediation

    Redis to Valkey Migration Under Memory Pressure

    Digital Collaboration Platform

    A production Redis cluster was crashing under memory growth traced to its full-text index rather than to the workload. AceMQ diagnosed the leak, stabilized the cluster, and mapped the Valkey migration path.

    ValkeyRedisKubernetes
  • Support

    Valkey Cluster Resharding Stuck Mid-Migration

    Regional Payments Processor

    A Valkey Cluster resharding ahead of a seasonal peak stalled with slots left in migrating and importing states. AceMQ resolved the slots on both nodes, finished the move in controlled batches and set up support for the next one.

    ValkeyKubernetesPrometheus
  • CVE Patching

    Valkey 7.2 Security Patching Without a Forced Upgrade

    Benefits Administration Provider

    A regulated provider could not move its on-premises Valkey 7.2 clusters for another year. AceMQ assessed each security advisory against its configuration and backported the fixes through OSSeva.

    ValkeyLinuxRedis Sentinel
  • Assessment

    Redis to Valkey Compatibility Assessment Across 41 Instances

    European Telecom Operator

    A telecom operator wanted to move its Redis estate to Valkey but did not know which instances could move cleanly. AceMQ assessed commands, scripts, modules and clients instance by instance and ordered the migration.

    ValkeyRedisKubernetes
All use cases

Solutions

Every way AceMQ works with Valkey.

AceMQ covers Valkey end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed Valkey on your infrastructure and fully managed Valkey on AceMQ infrastructure, plus end-of-life versions.

Projects

Build, fix or move Valkey

Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.

Side by side

Valkey consulting, project community help, cloud support or AceMQ support: what changes?

The Valkey project offers community help and releases. Cloud providers support their managed services. AceMQ consults on and supports the Valkey you run. Each row answers one question about the choice.

Valkey project, cloud provider and AceMQ compared on what is covered, response, fixes and how each is bought
QuestionValkey projectCloud provider (ElastiCache, Memorystore)AceMQ consulting and support
What is covered?Releases and community help.The managed service.Valkey you run, plus the application layer on cloud Valkey: key design, eviction, client behavior and sizing.
Is there a response commitment?No.Per your cloud support plan.Support: response targets from 15 minutes, by plan, 24/7. Consulting: a defined scope.
Who plans upgrades and migrations?Release notes only.The provider offers engine versions on its schedule.AceMQ engineers plan and rehearse them against your workload.
How is it bought?Free.Usage-based.Consulting quoted per engagement; support $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.

See Valkey support providers compared for the longer version.

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

Contact Us

One partner, not five

We Support Your Entire Tech Stack

Valkey rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.

See all the technologies we supportShow fewer

What is included

What a Valkey consulting engagement includes, and what it does not

Each row names one area of work. The right column is what stays outside the engagement.

Valkey consulting scope: what is included and what is not, by area
AreaIncludedNot included
ReviewMemory and fragmentation, slow commands and big keys, replication and backlog sizing, cluster slot health, persistence timing, clients, ACL and TLS inventory, and a ranked fix listRewriting your application's data model
UpgradesA path across 7.2, 8.x and 9.x in release-note order, replicas first, rehearsed against your command mix, with a rollbackValkey 9.2 release candidates for production
Redis migrationCompatibility review of commands, Lua scripts, modules and clients, key-level validation and a rehearsed cutoverRedis licensing advice
Cloud ValkeyKey design, eviction, client behavior and sizing on ElastiCache and MemorystoreFaults in the cloud provider's service
Tanzu ValkeyConsulting on the Broadcom build; licensing through Broadcom is North America onlyBroadcom licence terms and contracts

Pricing

How Valkey consulting is priced

Valkey consulting is quoted per engagement. A health check is a fixed scope; upgrade, migration and design work is scoped after the review so the quote matches the estate. A quote request is answered within 1 hour.

If you want 24/7 cover as well, the published range for AceMQ support is $24,000 to $72,000 a year (USD), set by SLA, scope and deployment. See Valkey support.

Fit

Who Valkey consulting from AceMQ is not for

  • You want a vendor to take over a fully managed cache service you do not operate.
  • You are outside North America and want Tanzu Valkey licensing through Broadcom; that is available in North America only.
  • You run a small cache whose loss costs nothing; the Valkey documentation is enough.

FAQs

Valkey Questions Answered

Answers on Valkey consulting from AceMQ: what is included, how an in-place upgrade is ordered, whether to leave Redis and how Tanzu Valkey fits.

Still have questions about Valkey? Email an Expert

What does Valkey consulting include?

A health check of memory, replication, persistence, cluster health and clients, upgrade planning across 7.2, 8.x and 9.x, cluster and failover design, and Redis to Valkey migration, each with written findings and a rollback plan.

Who offers Valkey consulting and professional services?

The Valkey project does not sell services. Cloud providers support their managed Valkey services, Broadcom supports its Tanzu build, and independent firms such as AceMQ consult on the Valkey you run yourself, with the same engineers who work the 24/7 support rota.

Is it safe to upgrade a Valkey cluster in place?

Yes with the right order: replicas first, a controlled failover, then the former primary, with a rollback plan at each step and no long period on mixed minors. We rehearse it against your command mix.

Should we move from Redis to Valkey?

It depends on the commands, Lua scripts, modules and clients you use and on your licensing position. We run a compatibility review first and tell you plainly when staying on Redis is the better call.

Why does INFO still say Redis 7.2.4?

Valkey keeps redis_version compatible so existing clients and tools work. Use valkey_version in INFO to read the real version.

Do you consult on Tanzu Valkey?

Yes. See the Tanzu Valkey page for the Broadcom build and its licensing, which is available in North America only, and the Valkey support page for 24/7 cover of open-source Valkey.

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

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

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

Let's talk

Test the Failover Before It Tests You

Tell us your Valkey version, cluster layout and what changed last. We reply to quote requests within 1 hour.

A senior AceMQ engineer, not a sales queueAbout your Valkey estate, not a pitch deckQuote requests answered within 1 hour

Production incident right now?Email a Valkey Architect

Get in Touch

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