Vendor support failing you — sound familiar?
- ▸ Valkey new — no commercial support shop yet — Valkey forked from Redis in 2024; vendor support ecosystem is still forming. AWS supports it on ElastiCache, but self-managed Valkey has no clear vendor.
- ▸ OSS-only incident response — production Valkey outage; you're posting in GitHub issues and hoping a Linux Foundation maintainer responds before you have to fail back to ElastiCache.
- ▸ Module compatibility regression at peak — RediSearch / RedisJSON modules don't all work cleanly on Valkey; an upgrade broke a module dependency at the worst possible time.
JusDB support: 15-minute Sev-1 response, named on-call engineer, no callback queues. Book a support scoping call →
Reactive incident response — not continuous ops
Valkey 24/7 Support
In short: Valkey support is reactive 24/7 emergency incident response — engine-level firefighting for OOM and memory crises, replication breakdown, cluster split-brain, Sentinel quorum loss, and latency cliffs — with a 15-minute P1 acknowledgment SLA, billed pay-per-incident or via an hourly retainer rather than continuous managed ops.
15-minute response SLA on production-down incidents, 24/7/365. Pay-per-incident or hourly retainer. If you need continuous managed ops instead, see Remote DBA; for one-shot architecture or migration decisions rather than reactive firefighting, see Consulting.
Incident Coverage
Incident types we handle
OOM & Memory Crises
Valkey OOM under traffic spike, eviction storms, RSS bloat exceeding limits — immediate stabilization plus root-cause analysis.
Replication Breakdown
Master-replica desync after network event, replica-link drops, replication backlog overflow, snapshot-stream failures.
Cluster Split-Brain
Partition-induced dual-primary scenarios, slot ownership conflicts, gossip-protocol degradation, post-AZ-outage convergence.
Latency Cliffs
Sudden p99 latency multiplication under no obvious cause, GC pressure, NIC saturation, kernel-level fragmentation.
Sentinel Quorum Loss
Multiple sentinel outages, quorum-disagreement scenarios, failed automatic failover, manual primary promotion under outage.
Post-Failover Stabilization
Client reconnect storms, cache-warming under load, replica-promotion validation, write-buffer reconciliation.
The SLA
SLA & engagement model
P1 — production down
P2 — production degraded
P3 — non-blocking
FAQ
Support FAQ
Production on fire?
Pre-negotiate a small support retainer NOW (not during the incident). Cold-start onboarding adds 60-90 minutes to first response — you don't want that on the clock during an outage.
Related Valkey Services
Explore more ways our Valkey experts can help with your database infrastructure.