Managed Redis or Valkey, your choice of engine
Redis or Valkey with persistence, eviction and failover set for how your application uses memory: dedicated clusters in OSStend's cloud, inside your own cloud account, or co-managed in your data center, run 24/7.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ: 160+ customers, 10+ years
- ✓24/7 on-call engineers
An example design file, with illustrative values:
# Managed Redis service: redis-sessions engine: valkey # or redis nodes: 3 target: gcp/dedicated eviction: allkeys-lru monitoring: included on_call: 24/7
Managed Redis or Valkey from OSStend lets you choose the engine and set persistence, eviction and replication for your workload. Engineers run it 24/7 with full configuration access, in OSStend's cloud, your cloud account or your data center, for teams that have outgrown a restricted cache service.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
What OSStend tailors for Redis or Valkey
A Redis or Valkey cluster is designed around how the data is used: as a cache, a session store or a queue, with the persistence, eviction and replication that use needs. You also choose the engine, and the design is signed off before anything is built.
- Metrics to your Prometheus or Datadog
- AceMQ engineers on call 24/7
| Area | Set for your workload |
|---|---|
| Engine | Redis or Valkey, chosen per cluster. Both speak the same protocol, so existing clients connect to either. |
| Size and shape | Memory, node count and shard layout chosen from the dataset and the request rate. A sharded cluster splits the key space into 16,384 hash slots, so the shard count and the key design are settled together. |
| Persistence and eviction | RDB snapshots fork the process, which can pause clients for some milliseconds, or up to a second on a very large dataset. An append-only file with the default fsync every second can lose up to one second of writes. For eviction, maxmemory is unlimited by default on 64-bit systems, and the noeviction policy returns errors on writes once the limit is hit, so a cache usually gets an allkeys-lru policy instead. Replication and AOF buffers are not counted toward maxmemory, so the design leaves RAM free for them. |
| Topology | Replication is asynchronous, so a failover can lose writes the old primary had acknowledged. Outside a sharded cluster, detecting the failure and promoting a replica is Sentinel's job, and it needs at least three instances; a sharded cluster does this itself. The design states how much loss the workload can accept, across zones and over hybrid links. |
| Configuration | Full engine configuration, run by OSStend engineers, including the administrative commands a restricted service blocks. |
| Versions and upgrades | The engine version your clients are validated on. Valkey's download page lists patch releases across the 7.2, 8.0, 8.1, 9.0 and 9.1 series (checked 9 Nov 2026), so the series is a design choice. Upgrades follow your change calendar and are never forced. |
| Where it runs | OSStend's cloud, your cloud account, your data center, Kubernetes or OpenShift, or an air-gapped site. |
| AI workloads | Session memory and a semantic cache that stops repeat questions from reaching the model. See semantic cache. |
There is no fixed menu here: the settings, modules and cluster size your workload needs are written into the design you sign off before anything is built, and that design is what OSStend runs.
Valkey is an open-source fork of Redis 7.2.4, announced by the Linux Foundation on 28 March 2024, kept under the BSD 3-clause licence and compatible with the Redis protocol. Redis is the original engine, with its own roadmap and licence terms. Read the Redis vs Valkey comparison and take your legal team's view before choosing. The OSStend design review recommends an engine for the workload, and the choice stays yours.
Redis 7.2 and earlier are BSD-licensed. From Redis 7.4 Redis is dual-licensed under RSALv2 and SSPLv1 (Redis, 20 Mar 2024), and Redis 8 adds AGPLv3 as a further option (Redis, 1 May 2025), both checked 31 Oct 2026. Valkey stays BSD-licensed. Which engine and version a cluster runs, and the licence that comes with it, is settled in the design review.
Where turnkey Redis and Valkey services stop
Amazon ElastiCache documents its restrictions: several administrative commands are unavailable on clusters running Redis OSS, and engine settings are changed through parameter groups. A workload that needs direct control of persistence, replication or configuration has to look elsewhere.
| Area and managed service | Documented limit | What OSStend does instead | Source |
|---|---|---|---|
| ConfigurationAmazon ElastiCache (Redis OSS) | On clusters running Redis OSS, CONFIG, SAVE, BGSAVE, REPLICAOF, DEBUG and other administrative commands are unavailable. | What OSStend does insteadFull Redis or Valkey configuration, run by OSStend engineers. | AWS docs, checked 9 Nov 2026 ↗ |
Other plan-based services set their own menus of sizes, settings and upgrade timing. The Amazon ElastiCache alternative page compares them with dated sources, as do the Azure Managed Redis and Upstash pages, and the managed service limits index records the ElastiCache limit with its link.
Design. Move. Run. for Redis or Valkey
For Redis or Valkey, an engineer designs the engine, memory and failover behaviour and you sign it off, OSStend plans the move for your source and owns the cutover, and named engineers then run the cluster 24/7.
Design
An engineer reviews how the workload uses the data (cache, sessions, queues, AI memory), the dataset size, the request rate and the recovery needs, then writes the cluster design: engine, size, persistence, eviction and topology. You sign it off before anything is built.
Move
OSStend runs the migration from ElastiCache, Redis Cloud or a self-run server and owns the cutover. The method depends on the source: the AWS docs list REPLICAOF among the commands unavailable on ElastiCache for Redis OSS, so that source needs another route, chosen in the design step. Both sides stay live, clients are repointed in stages and traffic switches only when the new side is verified.
Run
Named engineers run it 24/7: upgrades on your calendar, persistence and eviction tuning, memory headroom for fork and replication buffers, failover handling and incident response, with an SLA written into your contract.
Deployment and service levels
Redis or Valkey runs dedicated in OSStend's cloud or inside your own cloud account, both fully managed, or co-managed in your data center. The engine is your choice in every option.
Dedicated in OSStend's cloud
Single-tenant Redis or Valkey nodes on Google Cloud or AWS, with replicas in separate zones so a failover does not stay in one failure domain.
Fully managedIn your cloud account
Redis or Valkey inside your own VPC, with the memory bill and the network boundary kept in your account. AWS first, then Azure and Google Cloud.
Fully managedIn your data center
Your hosts, Kubernetes or OpenShift clusters, air-gapped sites included, with OSStend engineers running the engine through an operator and supported images.
Co-managed
Fully managed Redis and Valkey clusters carry an uptime commitment, and a data center deployment carries a 24/7 response-time commitment because the hosts are yours. The service levels page sets out the tiers, and deployment shows each option in detail.
Uptime and response figures are set per plan and written into your contract. AceMQ, which operates OSStend, sets its support response targets from 15 minutes, by plan.
Proof from AceMQ's operating record
The persistence, failover and upgrade work for Redis and Valkey is run by AceMQ's engineers. AceMQ operates OSStend with 160+ customers, 10+ years of running open-source infrastructure and engineers on call 24/7, the same facts acemq.com gives.
AceMQ gives customer names only with written consent, so the Redis and Valkey record stays anonymous here. If you want a reference with a similar persistence or failover set-up, raise it in the 45-minute review.
Pricing for managed Redis or Valkey
Managed Redis or Valkey is priced from four drivers: the engine and persistence choice, the memory size, the SLA tier and where it runs. An engineer prices the design after a workload review, with no free tier or card sign-up for Redis or Valkey.
- Engine and persistence
- Redis or Valkey, and whether the cluster keeps an append-only file, snapshots or neither, change the memory and storage that have to be built.
- Cluster size
- memory, node count and shard layout, which follow the dataset and the request rate.
- SLA tier
- the uptime commitment on a fully managed cluster, or the 24/7 response-time commitment on a co-managed one.
- Where it runs
- OSStend's cloud, your cloud account or your data center, which decides who pays for the memory.
Give the dataset size, peak request rate, whether it is a cache or a store and where it must run, and the engineer prices that cluster.
The pricing page explains the model that applies to every engine.
When to contact OSStend, and when not to
Contact OSStend when Redis or Valkey holds data you cannot easily rebuild, or needs settings and a location a cache plan does not give you. If a cache plan covers the workload, use it.
Contact us if
- ✓You need persistence, eviction or configuration that a restricted cache service does not expose.
- ✓You want to choose between Redis and Valkey, and have an engineer design for the one you pick.
- ✓Redis or Valkey has to run in your own cloud account or in your data center.
- ✓You are leaving ElastiCache or Redis Cloud and want the migration run for you.
Not a fit if
- ✕A standard cache plan holds your workload and its settings already, and it costs less than a designed cluster.
- ✕You want a free tier, or to sign up with a card. For Redis or Valkey, OSStend opens with a conversation with an engineer.
- ✕You need a cache in minutes, with no design step.
Questions about Redis hosting, enterprise Redis and Valkey
These are the questions application and platform teams ask most before moving Redis or Valkey to a managed service.
Should I choose Redis or Valkey?
Both engines speak the same protocol, so the choice rests on licence terms, the roadmap and your own policies, not on client compatibility. Valkey is a BSD-licensed fork of Redis 7.2.4 under the Linux Foundation. The Redis vs Valkey comparison sets out the differences, and the OSStend design review recommends an engine for the workload.
Is this an enterprise Redis service?
It is an enterprise-run service for Redis or Valkey, not Redis Enterprise, which is Redis's own commercial product. OSStend designs the cluster around the workload and runs it 24/7 with full configuration access. The Redis Enterprise and Redis Cloud alternatives page compares the two with sources and dates.
What does Redis hosting from OSStend include?
Redis hosting from OSStend is a managed service on dedicated clusters in OSStend's cloud, your cloud account or your data center. Engineers run upgrades on your calendar, persistence and eviction tuning, scaling and failover handling 24/7, for Redis or Valkey as you choose.
Can I lose data when a Redis or Valkey primary fails?
Yes, a little. Replication is asynchronous, so writes the old primary acknowledged can be missing on the promoted replica, and the Redis Sentinel documentation says there is always a window for losing acknowledged writes. The design sets how that window is kept small and whether the application can tolerate it. A cache usually can, and a session or queue store needs more care.
Does Redis persistence stop clients while it writes to disk?
Briefly, in one case. An RDB snapshot forks the process, and Redis's persistence documentation says this can stop it serving clients for some milliseconds, or up to a second on a very large dataset with a slow CPU. An append-only file with fsync every second, the default, loses at most about one second of writes.
Can managed Redis or Valkey use settings that ElastiCache blocks?
Yes. OSStend engineers have full engine configuration, including administrative commands such as CONFIG and SAVE. AWS docs list those commands as unavailable on ElastiCache clusters running Redis OSS (checked 9 Nov 2026).
How does a move from ElastiCache or Redis Cloud work?
The design step picks the method for the source. Both sides stay live, clients are repointed in stages, and traffic switches only after the new side is verified. The Amazon ElastiCache alternative page describes the path, and the Redis to Valkey migration guide covers the documented methods.
Can Redis or Valkey act as a semantic cache for AI?
Yes. Redis and Valkey can hold session memory and a semantic cache that stops repeat questions from reaching the model, with eviction and persistence set for that workload. See semantic cache.
What does managed Redis or Valkey cost?
The price follows memory and node count, whether data is persisted, the SLA tier and where it runs. The pricing page sets out the model, and an engineer prices the specific design after a workload review.
Related pages
- AI data · Fast recallSemantic cache for LLM apps with Redis or ValkeySemantic cache with Redis or Valkey: how a similarity-matched cache cuts repeat model calls, how to set thresholds and eviction, and the cost maths.
- ComparisonValkey vs Redis in 2026: which to runValkey vs Redis: latest releases (Valkey 9.1.3, Redis 8.10.3), licences, compatibility and how a switch works. Read from both projects, checked 15 Nov 2026.
- AlternativeElastiCache pricing and alternatives in 2026Amazon ElastiCache pricing is only part of the picture: admin commands are restricted and it runs on AWS only. See fully configurable Redis or Valkey.
- AlternativeAzure Managed Redis alternatives (2026)Azure Managed Redis alternatives for enterprise caching: dedicated Redis or Valkey in Azure, another cloud or your data center, with dated Azure list prices.
- AlternativeUpstash pricing and alternatives (2026)Upstash pricing from its published plans, where per-request billing gets expensive at steady load, and dedicated Redis or Valkey alternatives.
- Research · Original dataManaged service limits index, checked 9 Nov 2026A managed service limits index: 13 documented limits of Amazon MQ, MSK, ElastiCache, Neon, Supabase and Instaclustr, each with its source link and date.
Talk to an engineer about your Redis or Valkey workload
45 minutes with an engineer: bring your dataset size, your peak request rate and how you use Redis today, and the engineer sketches the design.
- ✓A design sketch for your workload, not a plan menu
- ✓A zero-downtime cutover path for what you run today
- ✓A price for that design, after the review