The fast layer, without the operations.
Fully managed Valkey for caching, sessions, queues, and rate limiting — a drop-in for any Redis client. Each database is isolated and TLS-only, with durability you choose per workload, on hardware we run ourselves.
- $3 a month, from
- 6 persistence modes
- TLS required
- ~2 min to provision
# TLS is not optional$ redis-cli -u rediss://my-cache.valkey.cosmoner.com:6379$ SET session:8f2c … EX 3600OK$ INFO keyspacedb0:keys=48211,expires=48211
- PlanValkey · 1 GB
- PersistenceAOF_EVERY_1_SECOND
- Clientany Redis client
ENGINE
Valkey 8
Redis-compatible, RESP2 and RESP3
DURABILITY
6modes
Included in the plan price
STORAGE
Persistent
A volume per database, included
ACCESS
TLS only
Isolated instance per database
Three choices, then a connection string
Sized for the workload, not the default
A key-value store is used for very different jobs, and a cache and a queue do not want the same guarantees. The three decisions below are the ones that actually differ between them.
- 01
Pick a size
Plans are priced by how much data they hold, from 250 MB upwards. Size on the dataset you expect to keep in memory — every tier gets the same CPU and the same features.
- 02
Choose durability
Pick one of six persistence modes — the price does not change with it — and see the prorated charge before the database is created.
- 03
Connect over TLS
Provisioning usually finishes within a couple of minutes. You get a host, a port, and a password — connect with a rediss:// URL from any Redis client. Valkey speaks the same protocol, so nothing in your application changes.
What a database includes
Managed, and still yours to tune
Cosmoner runs the instance. Capacity, durability, the engine, and where it lives stay decisions you make per database.
Redis-compatible, by design
Valkey is the BSD-licensed fork of Redis 7.2, wire- and command-compatible with it. Your existing client, your connection string and your code work unchanged — there is nothing to port and nothing to learn.
Valkey 8 · RESP2 and RESP3
Isolated and TLS-only
Each database is its own instance, reachable only over TLS. The password for the default user is returned when you read the database, never in a list response.
rediss://
Six persistence modes
From nothing on disk to every write persisted before it is acknowledged, with one-second flushes and hourly snapshots in between. Persistence is included in the plan price.
AOF · SNAPSHOT · NONE
Reserved CPU, no throttling
Every tier reserves the same CPU, because Valkey executes commands on one thread and a bigger dataset does not run faster. Nothing caps operations per second, so there is no rating to size against.
0.25 vCPU
Rolled back if it fails
A database starts as creating and becomes active once provisioning finishes. If provisioning fails, the charge is rolled back — you are never billed for a database that did not come up.
CREATING → ACTIVE
Persistence
Decide what a restart is allowed to cost
Persistence is what survives a restart, and it is included in the plan price rather than sold as an add-on. The modes range from nothing on disk to every write persisted before it is acknowledged.
- A pure cache in front of a database promises nothing about a restart, and that is the right choice for one.
- A queue or session store usually wants one-second flushes, losing at most a second.
- Snapshots every 1, 6, or 12 hours suit data you could rebuild but would rather not.
- Every plan includes a persistent volume whichever mode you pick, so the choice changes durability and not the price.
{ "name": "my-cache", "planSlug": "valkey-1gb", "region": "se-sto", "dataPersistence": "AOF_EVERY_1_SECOND"}
# active in a couple of minutesrediss://my-cache….valkey.cosmoner.com:6379
The trade-off, spelled out
Four points on the durability scale
Stronger durability asks more of every write. Weaker durability asks you to be able to rebuild. Pick per database, not per project.
Every write, before the ack
Nothing is acknowledged until it is on disk. The strongest durability on offer, and the right choice when losing a write is not acceptable.
AOF_EVERY_WRITE
Flushed once a second
At most one second of writes is lost. The usual middle ground for a queue or a session store you would rather not rebuild.
AOF_EVERY_1_SECOND
Hourly point-in-time copy
Also available every 6 or 12 hours. Enough for a cache you can warm again, where the copy is a convenience rather than a guarantee.
SNAPSHOT_EVERY_1_HOUR
Nothing on disk
Everything is lost on restart, which is exactly right for a pure cache in front of a database that already holds the truth.
NONE
High availability
One instance, and we say so
Automatic failover needs something watching the primary and moving traffic when it goes. Nothing in our cluster does that yet, so it is not sold — rather than sold and not delivered.
- Each database is a single Valkey instance with a persistent volume behind it.
- A restart replays the volume, so what survives is set by the persistence mode you picked.
- Asking for replication is rejected with a clear error rather than silently ignored.
- The plan list reports supportsReplication per tier, so a client can check rather than assume.
{ "slug": "valkey-1gb", "memoryMb": 1024, "cpuMilli": 250, "supportsPersistence": true, "supportsReplication": false}
Where it runs
In Stockholm, on hardware we run
We sell where we own capacity, which today is one region in Sweden — your data stays in the EU. Apps on Cosmoner reach it over the cluster network, so the round trip is as short as it gets.
- se-stoStockholm, Sweden
The regions endpoint is the source of truth, and lists new regions as capacity is added.
One project
What it plugs into
The database is billed on the project's subscription alongside the apps that read from it, behind the same roles and the same API keys.
What it costs
Priced by the plan, not by the request
You buy a plan with a fixed dataset size. Commands, connections, and bandwidth are not metered on top of it.
- Valkey plans
- from USD 3 / month
- The whole dataset is held in memory, on our own infrastructure. Priced by dataset size, from 250 MB upwards, with a persistent volume included.
- Persistence
- Included
- Snapshotting to disk is part of every plan — choosing a snapshot interval does not change the price.
Every plan shows its monthly price in the plan picker, alongside its dataset size and the CPU it reserves.
Questions worth answering up front
Plans, persistence modes, and every endpoint are covered in the API reference.
- Why Valkey and not Redis?
- Since version 7.4, the Redis licence does not allow it to be offered as a managed service. Valkey is the open source fork of Redis 7.2 that carried on under the Linux Foundation, with the same protocol and commands, and it is what AWS and Google moved their managed offerings to. You get a Redis-compatible database without the licence risk.
- Is this a drop-in replacement for Redis?
- Yes. Valkey is the Linux Foundation's fork of Redis 7.2 and is compatible with it at the protocol and command level, so your client library, your connection string and your code are unchanged. It is what AWS and Google moved to when the Redis licence changed. Point your existing client at the host we give you.
- Is there high availability?
- Not yet, and we would rather say so than sell it. Automatic failover needs something watching the primary and moving traffic when it goes, and nothing in our cluster does that today. Each database is a single instance with a persistent volume behind it. If losing a few seconds of writes during a restart is not acceptable for your workload, this is the thing to weigh.
- Which persistence mode should I choose?
- Match it to what losing the data costs. A cache in front of a database does not need one. A queue or a session store usually wants one-second flushes. Only pick every-write when a lost write is a real problem, since it is the mode that asks the most of each acknowledgement.
- Do the smaller plans give anything up?
- No. Every tier supports all six persistence modes and includes a persistent volume, and none of them offers replication — the tiers differ in how much data they hold, not in what they can do. The plan list reports what each one supports, so a client can check rather than assume.
- I have a Redis database from before. What happens to it?
- Nothing. The Redis plans are no longer sold, but databases created on them keep running at their original price and can still be managed and deleted from the control panel. To move to Valkey, create a Valkey database and point your client at it — the commands are the same.
- What does it cost?
- Each database is billed monthly on the plan you choose, and the plan list carries the current price for every tier. Before creating one you can preview the prorated amount that will be added to the project's subscription.
- What happens when I delete a database?
- It and everything stored in it are permanently deleted, and the recurring charge stops. This cannot be undone, so take a copy first if the contents matter.