VMware Valkey — Consulting, Support & Licensing

VMware Tanzu Valkey Consulting, Licensing, & Support

As Broadcom's #1 VMware Partner in the Americas, AceMQ delivers Redis-to-Valkey migrations, architecture consulting, and 24/7 production support with a 15-minute emergency SLA. We also manage your VMware Tanzu Valkey licensing from procurement to renewal.

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

Senior Cache/Data SMEs
11+
Emergency SLA
<15min
Enterprise Customers
130+
Countries Served
26+

Without an unplanned rewrite of every client that still 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 that teams bring to AceMQ, from a Redis licence decision nobody had time to plan and client libraries never tested on Valkey to keys without expiry, failovers that lose writes and one large key that blocks the single thread. If one describes your week, that is where the review starts.

  1. 01

    The Redis licence change forced a decision about Valkey that nobody has had time to plan properly

  2. 02

    The Broadcom renewal prices Tanzu Valkey per core and the node sizing was chosen back when it was Redis

  3. 03

    Client libraries are pinned to Redis-specific versions and none of them have been tested against Valkey

  4. 04

    Keys were created without expiry and the dataset has grown past what the eviction policy can clear cleanly

  5. 05

    A failover promoted a replica that was behind, and writes accepted just before the switch were lost

  6. 06

    The sentinel or cluster topology was set up once and has never been tested against a real node loss

  7. 07

    Both RDB and AOF persistence are enabled and the fork pauses show up as latency spikes on the application side

  8. 08

    One large key or a keyspace scan blocks the single thread and every other command queues behind it

A good fit if you run Valkey, or are leaving Redis, in production and want senior engineers who know its failure modes and can also size a VMware Tanzu subscription for US customers.

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 when Valkey hits maxmemory and nothing can be evicted?

With a volatile eviction policy, Valkey only evicts keys that carry a TTL. If most keys were written without one, nothing is eligible at maxmemory, so writes fail with an out-of-memory error and the application sends its load to the database.

One memory ceiling, no evictable keys

One application, one Valkey instance, one database

Illustrative

  1. Session keys are written with a TTL and expire on their own. Memory sits near 55 percent of maxmemory, and the database sees only genuine misses.

  2. Most keys were written without a TTL, and the policy is volatile-lru, so no key is eligible. At maxmemory every write is refused with an OOM error, session keys cannot be refreshed, and the database takes the load.

  3. Each key namespace gets a TTL standard, the policy matches the data, and headroom covers the fork and replica buffers. Writes succeed again and the database load drops.

Writes rejected with an OOM error while the instance looks like it should be evicting is a common Valkey call to AceMQ. The first checks are INFO memory, maxmemory-policy and the share of keys that carry a TTL, because volatile policies skip keys without one. The fix is a TTL standard per key namespace, a policy that matches the data (allkeys-lru for a pure cache), headroom for the fork and replica buffers, and big-key cleanup. On Valkey 9.0, hash field expiration lets individual fields age out, which helps where the data model allows it.

Our Services

Valkey Consulting & Services

AceMQ runs five Valkey service lines: architecture and production implementation, Redis to Valkey migration, performance tuning, high availability and cluster operations, and VMware Tanzu licensing for US customers. A senior engineer leads each one, and any of them can roll into 24/7 support with a 15-minute emergency SLA.

  • 01

    Valkey Architecture & Production Implementation

    We design and implement Valkey deployments purpose-built for your workload — caching, session storage, pub/sub pipelines, and rate limiting. Every deployment includes security hardening, observability, and production-ready cluster topology.

    • Data structure selection and persistence strategy: RDB vs. AOF vs. no persistence
    • Valkey Cluster topology: shard count, replication factor, hash slot distribution
    • TLS/mTLS, ACL user configuration, connection pooling, and pipeline batching
    • Kubernetes StatefulSet deployment with PVC sizing and Prometheus metrics exporter
  • 02

    Redis to Valkey Migration

    We plan and execute Redis-to-Valkey migrations with zero data loss, full API compatibility validation, and minimal application changes. Our process includes parallel-run validation before any cutover.

    • Redis 7.x compatibility assessment: command-set and protocol analysis
    • Data migration: RDB dump analysis, RESTORE procedure, and key validation
    • Client SDK compatibility verification across all application services
    • Cutover planning with traffic shadowing, canary release, and rollback procedures
  • 03

    Valkey Performance Tuning & Optimization

    Sub-millisecond latency requires expert tuning across memory, network, and persistence layers. We profile your deployment end-to-end and implement targeted fixes.

    • Latency profiling: SLOWLOG, LATENCY HISTORY, and CLIENT LIST analysis
    • Hot key detection and access pattern redistribution across cluster shards
    • Memory fragmentation analysis and kernel parameter tuning
    • Connection multiplexing and client-side caching with RESP3 tracking mode
  • 04

    Valkey High Availability & Cluster Operations

    We build and operate Valkey Cluster and Sentinel deployments that stay available through node failures, network partitions, and rolling upgrades. Chaos testing is included to validate failover timing before go-live.

    • Valkey Cluster setup: shard assignment, replica promotion, and resharding
    • Sentinel quorum configuration for automatic failover with minimal downtime
    • Cross-region replication for disaster recovery and geographic distribution
    • Zero-downtime scaling: adding and removing nodes with live data rebalancing
  • 05

    Valkey Licensing & Subscription Management

    AceMQ manages your VMware Tanzu Valkey subscription from initial procurement through compliance audits and renewal negotiations. We deliver licensing quotes within 24 hours.

    • VMware Tanzu Valkey commercial licensing procurement and entitlement management
    • License compliance audit: reconcile deployed node count with purchased entitlements
    • Renewal negotiation and multi-year contract cost optimization
    • L3 commercial support access and SLA tier guidance for uptime requirements
  • 15 MIN SLA

    24/7 Valkey Support

    Named senior engineers on your account — 15-minute emergency response, no ticket routing, no junior triage.

    • 15-minute emergency response SLA
    • Named engineer, zero cold-start
    • Proactive CVE & health monitoring
    • Quarterly deployment reviews
    Compare the four Valkey support stages

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 named senior engineers and a 15-minute first response when production is down, 24/7. Lower severities get 1-hour, 4-hour and next-day responses. The same tiers apply to open source Valkey and to Tanzu for Valkey.

  1. 15 minfirst 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

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

15-minute P1 response, 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 50+ 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.

  • Direct Product Roadmap Access

    As the only vendor directly connected to the core engineering teams, AceMQ delivers exclusive early insights, strategic upgrade planning, and curated release summaries — tailored to your environment.

Compare Valkey support plans

How It Works

What actually happens next

An AceMQ Valkey engagement runs in four stages: an assessment of 1 to 2 weeks, written findings within a week, changes made with your engineers by replicating alongside the existing instance, then a handover with runbooks. Each stage ends in writing, so every cutover is a client change you can reverse.

1–2 weeks

Cache and licensing assessment

We review keyspace size and expiry, memory and eviction policy, persistence settings, cluster or sentinel topology and failover behaviour, client library versions — and how your node and core count maps to the Tanzu licence.

Within a week

Written findings and plan

Prioritised findings covering the Redis-to-Valkey path, availability and licence position, with the reasoning attached so the migration can be scheduled rather than forced on you by a renewal date.

Scoped per engagement

Implementation alongside your team

We carry out the Valkey migration and topology changes with your engineers rather than around them, replicating alongside the existing instance so cutover is a client change you can reverse.

Ongoing

Handover and optional cover

Runbooks for failover, eviction and persistence behaviour written against your keyspace and topology, plus 24/7 support with a 15-minute emergency SLA if you want it.

  • Written findings before any change
  • Every cutover reversible, with replication running alongside
  • Your engineers in the room
  • You keep the runbooks
  • Ad hoc engagements or an annual partnership

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

Customer Success

Real Valkey Results

Valkey work from AceMQ: a Redis to Valkey migration under memory pressure, a stuck cluster reshard, security patching of Valkey 7.2 and a 41-instance compatibility assessment. Each card links to the full write-up: the environment, what AceMQ changed, and the result.

1 / 4 case studies

  • 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
    Read case study : Redis to Valkey Migration Under Memory Pressure
  • 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
    Read case study : Valkey Cluster Resharding Stuck Mid-Migration
  • 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
    Read case study : Valkey 7.2 Security Patching Without a Forced Upgrade
  • 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
    Read case study : Redis to Valkey Compatibility Assessment Across 41 Instances
All use cases

Solutions

Every way AceMQ works with Valkey.

AceMQ covers Valkey end to end: consulting and Redis to Valkey migrations, 24/7 support and incident management, proactive monitoring, managed Valkey on your infrastructure or on AceMQ's, OSSeva patches for Valkey 7.2, and a fixed-price health check.

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.

Support and managed services

Keep Valkey running

Four stages of ongoing cover once you are live. Each stage hands more of the day-to-day work to AceMQ, from a 15-minute emergency SLA to AceMQ hosting and running Valkey for you.

Compare the four Valkey support stages

Side by side

Open source Valkey or a Tanzu for Valkey subscription: what changes?

Open source Valkey and Tanzu for Valkey run the same engine. The subscription adds vendor support for the Valkey binaries and the Tanzu packaging, and a per-core licence. AceMQ adds 24/7 engineering support on either one. Each row below answers one question.

Open source Valkey compared with a Tanzu for Valkey subscription and with AceMQ support on support scope, packaging, licensing, security fixes and migration from Redis
QuestionOpen source Valkey, self-runTanzu for Valkey subscriptionAceMQ alongside either
Who supports it?Valkey is a Linux Foundation project with community channels and no support contract.The subscription adds vendor support for the Valkey binaries and the Tanzu-distributed pieces, such as the tile or the operator.24/7 engineering support from named senior engineers, with a 15-minute first response on P1 incidents.
What stays with your team?Everything: key design, eviction policy, client settings, topology and the pager.Custom application code and load testing sit outside the subscription's support scope, and key design and client choices stay with you.AceMQ reviews eviction against TTL coverage, big keys, client pooling and failover handling, or runs it for you.
How is it packaged and deployed?You deploy it on VMs, Kubernetes or bare metal with your own automation or an operator.It installs as a tile on Tanzu Platform or through an operator on Kubernetes.AceMQ designs and runs Cluster and Sentinel topologies on either one.
How is it licensed?BSD licensed, with no licence fee.A per-core subscription. Through AceMQ it is sold in the US only, with a 72-core minimum.AceMQ sizes the subscription against the cores your Valkey nodes use and handles renewal.
How do security fixes arrive?From the Valkey project: three years of fixes per minor version, and five years of security fixes for the last minor of each major line.As new builds of the supported lines through the subscription's release channel.CVE alerts for your exact version, and OSSeva backports for Valkey 7.2.
What if we are still on Redis?Valkey keeps the Redis protocol, so most clients connect unchanged. Modules, newer commands and version-string checks are where problems appear.The same applies: the move is a compatibility question, not a data question.AceMQ reviews commands, Lua scripts, modules and clients first, then cuts over by replication with a rehearsed rollback.

To see who supports Valkey on each platform, read who offers Valkey support. For the engine-level differences, see Valkey vs Redis compared.

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.

Messaging & Streaming

Databases & Caching

Search & Analytics

Lakehouse & Compute

Observability & Monitoring

Data Integration

Cloud & Containers

API Management

VMware Tanzu

See all 51 technologies we supportShow fewer

Guides, articles and comparisons

Go deeper on Valkey.

Guides from AceMQ engineers on who supports Valkey, how Valkey compares with Redis, and how to move between them, plus the AceMQ services for the databases and platforms that usually run next to it.

Related services

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

Contact Us

FAQs

Valkey Questions Answered

Eight answers on Valkey from AceMQ: moving from Redis, supported and end-of-life versions, client compatibility, migrating without downtime, open source against Tanzu for Valkey, licensing, who answers at night, and managed Valkey.

Still have questions about Valkey? Email an Expert

Should we move from Redis to Valkey?

Move if the Redis licence terms or the cloud service roadmap are a problem for you, and stay if they are not. Valkey is BSD licensed and speaks the same protocol, so the move is usually a client and compatibility question, not a data question. AceMQ reviews commands, scripts, modules and clients first, then says plainly whether a move pays off.

Which Valkey versions does AceMQ support, including end-of-life ones?

AceMQ supports Valkey 7.2, 8.0, 8.1, 9.0 and 9.1 around the clock. For Valkey 7.2 estates that cannot upgrade yet, CVE fixes are backported through OSSeva. The project gives each minor version three years of fixes, and AceMQ plans upgrades against those dates and against your client library versions.

Will our Redis clients and commands work on Valkey?

Most will. Valkey keeps the Redis protocol and the Redis 7.2 command set, and it still reports a Redis 7.2.4 compatible version in INFO so existing tools keep working. Problems show up in modules, in commands added to Redis after the fork, and in tools that act on the version string. AceMQ tests your exact client and tool versions against a replica before cutover.

How does AceMQ migrate from Redis to Valkey without downtime?

AceMQ replicates from the Redis primary into Valkey, validates keys on both sides, shadows reads, and then moves clients in stages with a rollback that stays open until the old instance is retired. The risky part is rarely the data. It is Lua scripts, modules and client versions, which the compatibility review finds before the cutover does.

What is the difference between open source Valkey and Tanzu for Valkey?

Open source Valkey is BSD licensed with community support only. A Tanzu for Valkey subscription adds vendor support for the Valkey binaries and the Tanzu-distributed pieces, which install as a tile or an operator. Custom application code and key design stay with you, and AceMQ covers those with 24/7 engineering support on either one.

How does Tanzu Valkey licensing work through AceMQ?

VMware Tanzu licensing through AceMQ is available to US customers only, with a 72-core minimum. AceMQ sizes the subscription against the cores your Valkey nodes use, reconciles it with what you already own, and handles renewal. Quote requests are answered within 1 hour.

Who answers when Valkey fails at night?

A named senior AceMQ engineer, 24/7, with a 15-minute first response on P1 incidents and a written root-cause analysis afterwards. There is no tier-1 triage layer. Lower severities get 1-hour, 4-hour and next-business-day responses, and you reach the engineer by phone, email or Slack.

Can AceMQ run Valkey for us?

Yes. AceMQ operates Valkey on your infrastructure or on AceMQ's, including monitoring, patching, replica-first upgrades, failover tests and on-call. It is part of the managed Redis and Valkey service. You choose between keeping the data in your own cloud account and having AceMQ host it.

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. We do not send generic quotes or publish a price list, because two estates of the same size rarely need the same thing. Request a quote and AceMQ replies within 1 hour.

Let's talk

Ready to Future-Proof Your Key-Value Infrastructure with Valkey?

AceMQ provides architecture, 24/7 support, Redis-to-Valkey migration, and Tanzu licensing — backed by a 15-minute emergency SLA and Broadcom's #1 partner standing. Contact us and get a licensing quote within 24 hours.

A senior Valkey engineer, not a sales queueAbout your clusters, 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 one business day — 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 business day.

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

We respond within 1 business day.