Serverless Valkey
The Linux Foundation fork of Redis, with the same wire protocol and none of the licensing complications. Free tier, TLS by default, cloud or self-host.
Keys
- session:847STR
- user:1247HASH
- cart:1247LIST
- leaderboardZSET
Where to run it
Cloud, desktop, or self-host
One database, three places it can live. Pick the speed you want and move between them when you outgrow it.
What you get
Production features, free tier included
Every Valkey database ships with the same primitives: TLS, web console, hibernation, and a real dashboard. No tiered features hidden behind a sales call.
Web IDE
Query console in the dashboard, no extra client to install.
TLS by default
All connections encrypted. No setup required.
Always-on connections
Pin a database to your always-on pool to prevent hibernation.
Scale to zero
Hibernates when idle. Wakes on the next connection.
Connection pooling
Pooled endpoint for serverless and edge workloads.
Direct connections
Bypass the pooler for migrations and replication.
Native HTTPS endpoint
Engines whose own wire protocol speaks HTTPS. Every database, including this one, is also queryable over the platform's HTTPS query API and web console.
Serverless driver
Drop-in HTTP driver for edge runtimes (Upstash REST, PlanetScale, or the engine-native client).
IP whitelisting
Restrict access to specific IPs or CIDR ranges.
Automatic backups
Scheduled dumps and volume snapshots with one-click restore on paid plans. Free tier includes a manual backup slot.
Quick start
Connect with any Valkey client
New projects that want Redis semantics without the BSL/SSPL license restrictions; caches, queues, rate limiters, session stores, pub/sub.
- Replace upstream Redis in a project that needs a permissive license
- Cache layer in front of your primary database, redeployed across clouds without license review
- Edge-friendly key-value store accessed via the REST driver from Cloudflare Workers
- Per-tenant session storage that hibernates between bursts
- Background job queue or scheduled HTTP webhook delivery via the built-in vqueue surface (works with the `@upstash/qstash` client library, no extra provisioning)
- Self-host on your own hardware with SpinDB
redis-cli -u "rediss://default:password@your-host.cloud.layerbase.dev:6379" pingSibling engine
Need the upstream Redis version specifically?
If your app or third-party tool requires a specific Redis upstream feature or version, Layerbase also runs an OSS-licensed Redis version unchanged. Most apps work on either.
Questions
Common Valkey questions
Is Valkey a drop-in replacement for Redis?+
Yes. Valkey forked from the last open-source Redis version and tracks the same wire protocol. redis-cli, ioredis, redis-py, and other Redis clients connect to Valkey without code changes.
Who maintains Valkey?+
Valkey is a Linux Foundation project with maintainers from AWS, Google, Oracle, Ericsson, and others. Released under BSD-3-Clause so redistribution and commercial use are unrestricted.
When should I pick Valkey over Redis?+
For new projects: Valkey is the safer long-term bet on licensing. For existing apps already running on a specific Redis version: stay with Redis. Both run on Layerbase Cloud, so you can change later.
Does the REST API work?+
Yes. Valkey supports the same Upstash REST API as Redis on Layerbase, useful for serverless and edge runtimes.
Can I run Valkey locally?+
Yes. SpinDB and Layerbase Desktop both ship Valkey alongside Redis, with the same install-and-run workflow.
Do you support scheduled HTTP webhooks / a job queue on top of Valkey?+
Yes, via vqueue. Every Layerbase Valkey database exposes a free, built-in HTTP queue surface compatible with the `@upstash/qstash` npm client library. Copy VQUEUE_URL, VQUEUE_TOKEN, and VQUEUE_CURRENT_SIGNING_KEY from the dashboard and pass them to `new Client({ baseUrl, token })` and `new Receiver({ currentSigningKey })` in your app. v1 covers immediate fire-and-forget webhook delivery; scheduled delays, retries, and DLQ are on the roadmap. No separate signup, no separate billing.