---
title: "Managed Valkey, compatible with Redis, in one click, from €9.99/mo · Pethost"
description: "Valkey 9 beside your apps, at no extra cost: Redis clients connect as they are, every key is in the browser, the slowest commands are named, and a backup is made every night."
---

Valkey 9 · in every plan

# Managed Valkey in one click, at no extra cost.

A cache, a session store and a queue that Redis clients speak to, on your machine beside your apps. Link an app, see every key in the browser, and get a backup every night.

From €9.99 a month for the machine and all your projects, with no fee per database.

[Create a Valkey](https://console.pethost.dev/) [Compare prices](https://pethost.dev/valkey/#compare)

![A Valkey database in the panel, on its Overview: its memory, CPU, disk and connections, the apps that use it and how to connect.](https://pethost.dev/shots/valkey-overview.webp)

valkey-cli: a page cached for five minutes, a session's user read back, and the page's time to live counting down.

## What your app keeps at hand.

What a request should not wait for: in memory, on the same machine as your app.

### A cache in front of the database

Pages and answers kept for minutes: a visit reads memory instead of running a query.

### Sessions that outlive a deploy

Visitors stay signed in while your app restarts or rolls out a new version.

### Queues for background jobs

Emails, thumbnails and imports wait for a worker, in the Redis job library your framework uses.

### Rate limits and counters

Count each visitor's requests and forget them a minute later, with INCR and EXPIRE.

### Rankings that stay sorted

A sorted set keeps the top list in order as the scores change.

### Streams and pub/sub

Events for your other services to follow as they happen.

## Your Redis client connects as it is.

Link an app, and it reaches Valkey by its name. Put one line in its .env, or let your agent do it.

**Link from the panel**Every app on your machine, with Link beside it and the REDIS_URL line its .env needs.

**Code to copy**The host, the user and the password, and the URL as node-redis, redis-py and go-redis read it.

**From your laptop**One command puts it on localhost for valkey-cli or any Redis tool, over SSH.

![Connect, on Apps: the machine's projects, the shop linked, and the REDIS_URL line to put in each app's .env.](https://pethost.dev/shots/valkey-connect.webp) ![Connect with its details open on Node: the code that reads REDIS_URL.](https://pethost.dev/shots/valkey-connect-code.webp) ![Connect, on Laptop: the pethost tunnel command, then the URL that works on the laptop while it runs.](https://pethost.dev/shots/valkey-connect-laptop.webp)

## Kept in memory, and on disk.

Pick Valkey in New project, give it a name and a size. The machine writes its files, starts it and watches it.

- **Room for its keys**From 256 MB up to two thirds of your machine's memory. 70% of it holds keys, and the rest leaves room to save them.
- **No key dropped to make room**When it is full, a write is refused and every key stays. For a pure cache, let it evict old keys in its compose.yaml.
- **On disk every second**Each write goes to an append-only file, so a restart or a crash loses a second of writes at most.

![New database with Valkey picked: its name, its size of 256 MB, and the apps that will use it.](https://pethost.dev/shots/valkey-new.webp)

## Every key in the browser.

Keys, values and commands, as in a desktop tool, with nothing to install and no port to open.

**Find a key, edit it in place**By pattern and type, each with its size and time to live. Change a field, set a TTL or delete the key.

**Run commands in tabs**Replies as valkey-cli prints them, read only until you allow changes.

**valkey-cli in a click**A console in the browser, signed in.

![The keys of db0 on the left; on the right the hash cart:1042, its three fields and its time to live, with Set TTL, Remove TTL and Delete key.](https://pethost.dev/shots/valkey-keys.webp) ![A command's tab: HGETALL of a session, and its fields and values in the reply.](https://pethost.dev/shots/valkey-command.webp) ![The console: valkey-cli open in the browser, with the number of keys, a key's time to live and the week's three best-selling candles.](https://pethost.dev/shots/valkey-console.webp)

## See what it is busy with.

Minute by minute for 7 days and hour by hour for 90, with nothing to set up.

**The numbers that matter**Commands per second, key hits, memory against its limit, connections and keys.

**The busiest commands**Each command's calls, its total and mean time, and how many failed.

**The slow ones, by name**Each command over 10 ms lately, with its key and the app that sent it.

![The same database over the last hour: commands per second, mean time, key hits and peak memory, with commands rising towards now.](https://pethost.dev/shots/valkey-monitoring.webp) ![The commands of the last hour, each a read or a write, with its calls, total time, mean time and failures.](https://pethost.dev/shots/valkey-commands.webp) ![The slow log: four commands over 10 ms, each with its time, how long it took, its key and the client that sent it.](https://pethost.dev/shots/valkey-slow.webp)

## Back to last night in a click.

A backup every night, encrypted and stored off the machine, kept for 14 days. Take one more before a risky change.

**Restore in place**Back to the second of the backup. What it holds now is backed up first.

**Or as a new database**Last night's keys beside these, with a password of their own, while this one keeps running.

**Download an .rdb file**Its keys as Valkey saves them, for any Valkey 9 to load: your data is never locked in.

![The database's backups: one for each night of the last two weeks and one from this afternoon, each to restore in place or as a new database.](https://pethost.dev/shots/valkey-backups.webp) ![Restore as a new database: the backup's time, and the new database's name.](https://pethost.dev/shots/valkey-restore-new.webp) ![Download a dump: an .rdb file, which Valkey 9 reads.](https://pethost.dev/shots/valkey-dump.webp)

## Your agent sets it up for you.

Pethost's MCP server and skill let it add a Valkey, link your app and look inside with valkey-cli.

You say

“Add a cache to the shop.”

“Why do people get logged out?”

“Back up the cache before the release.”

your agent

- CreateDatabase valkey, linked to shop
- GetProject valkey: how to sign in
- DeployProject shop, with REDIS_URL in its .env
- GetOperation succeeded

Done: the shop keeps its cache in valkey now, and both are in the nightly backup.

- QueryContainerLogs web: OOM command not allowed
- RunServiceCommand valkey-cli: INFO memory

valkey is full: its keys take 179 MB of 179 MB, so new sessions are refused. Shall I give it 512 MB?

- RunProjectAction back_up
- GetOperation succeeded

Backed up. If the release goes wrong, I can restore this one.

## A managed Valkey alone costs more elsewhere.

What a Valkey or Redis of 1 GB costs a month at seven providers, beside all of Starter here.

- **Pethost** Starter · this Valkey and all your apps **€9.99**
- **DigitalOcean** Managed Valkey · 1 GB **$15.00** ×1.3
- **AWS** ElastiCache cache.t4g.small · 1.37 GB **$18.80** ×1.7
- **Render** Key Value 1g · 1 GB **$20.00** ×1.8
- **Upstash** Redis Fixed 1GB · 1 GB **$20.00** ×1.8
- **Redis Cloud** Essentials · 1 GB **$20.00** ×1.8
- **Azure** Managed Redis B1 · 1 GB **$23.36** ×2.1
- **Google Cloud** Memorystore shared-core-nano · 1.4 GB **$23.77** ×2.1

A year at the others costs more by **€41 – €135**

Billed on top of theirs: the traffic out past an allowance at AWS and Render, and between zones at AWS and Google Cloud; a public IPv4 address at AWS. At Azure, keeping the data on disk takes a second node, which is billed too.

Each price is the provider's own, read on 24 October 2026: its least plan with 1 GB of memory or more, a single node, on demand, before tax, in its lowest-priced region (N. Virginia at AWS and Redis Cloud, East US at Azure, Iowa at Google Cloud), with the persistence it sells: a snapshot at AWS, the append-only file at Google Cloud, none on one node at Azure. An hourly price is counted for 730 hours. Euros and dollars are compared at the European Central Bank's rate, €1 = $1.1193.

## Questions about Valkey on Pethost

**Does a database cost extra?**

No. Make as many as fit in your machine's memory: the plan's price stays the same every month.

**Is it the same as Redis?**

Valkey is the open-source fork of Redis 7.2, kept by the Linux Foundation: the same commands and the same protocol, so Redis's clients and libraries work with it. This one is Valkey 9, on the official valkey/valkey image.

**How big can it be?**

Its memory is your pick, from 256 MB up to two thirds of your machine's: 2 GB on Starter, 4 GB on Grow, 20 GB on Scale. 70% of it holds keys, and the rest leaves room to save them to disk.

**What happens when it is full?**

A write that needs more memory is refused with an error, and no key is dropped, so no session or job is lost to make room. For a cache whose old keys may go, add `--maxmemory-policy allkeys-lru` to its command in compose.yaml and deploy it.

**Does it keep its keys when it restarts?**

Yes. Each write goes to an append-only file on the machine's disk within a second, and Valkey reads the file back when it starts. Every night a backup also goes off the machine, kept for 14 days.

**Can I reach it from the internet?**

Not unless you open it: your apps on the machine and your laptop reach it without that. To open it, publish its port in its compose.yaml, and Connect shows its address.

**Can I use valkey-cli or redis-cli from my laptop?**

Yes. `pethost tunnel -p valkey` puts it on localhost:6379 over SSH, and Connect shows the URL to paste.

**Does it refuse any command?**

Only those that would change its users, make it a replica or stop it, such as ACL, REPLICAOF, MODULE, DEBUG and SHUTDOWN: the machine looks after those. Everything else works, Lua scripts and transactions included.

## Your Valkey is one click away.

[Start for €9.99/mo](https://console.pethost.dev/)

Pethost · Stephan Gomer · NIP 1133096755

Pethost

- [Templates](https://pethost.dev/templates/)
- [About](https://pethost.dev/about/)
- [Docs](https://pethost.dev/docs/)
- [Blog](https://pethost.dev/blog/)
- [API](https://pethost.dev/docs/api/)
- [CLI](https://pethost.dev/docs/cli/)
- [Plugin](https://github.com/pethost-dev/plugin)
- [Terms](https://pethost.dev/terms/)
- [Privacy](https://pethost.dev/privacy/)
- [Refunds](https://pethost.dev/refunds/)
- [support@pethost.dev](mailto:support@pethost.dev)

Databases

- [Postgres](https://pethost.dev/postgres/)
- [Valkey](https://pethost.dev/valkey/)

Comparisons

- [Coolify vs Dokploy vs CapRover vs Dokku](https://pethost.dev/blog/coolify-vs-dokploy-vs-caprover-vs-dokku/)
- [Coolify Cloud vs Dokploy Cloud](https://pethost.dev/blog/coolify-cloud-vs-dokploy-cloud/)
- [Railway vs Render vs Fly.io pricing](https://pethost.dev/blog/railway-vs-render-vs-fly-io-pricing/)
- [Managed Docker Compose hosting](https://pethost.dev/blog/managed-docker-compose-hosting/)

Alternatives

- [Railway alternatives](https://pethost.dev/blog/railway-alternatives/)
- [Heroku alternatives](https://pethost.dev/blog/heroku-alternatives/)
- [Dokploy alternatives](https://pethost.dev/blog/dokploy-alternatives/)
- [Coolify alternatives](https://pethost.dev/blog/coolify-alternatives/)
- [Render alternatives](https://pethost.dev/blog/render-alternatives/)
- [Sliplane alternatives](https://pethost.dev/blog/sliplane-alternatives/)