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.
Branch Valkey in seconds
Fork a running Valkey into a full, isolated copy with its own connection string. Copy-on-write makes it near-instant, not a dump and restore. Point a preview deploy at it, test a migration, then throw it away. Layerbase branches 9 engines, not just Postgres.
See how branching worksWhat 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" ping
Already have data? Migrate it from Upstash, Vercel KV Any connection string works too.
Sibling 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.
More on Valkey
All articles- July 3, 2026
Migrating from Vercel KV to Layerbase
Vercel KV is Redis with Upstash underneath, so the move is a data copy and a one-line client swap. Paste the KV_URL you already have and copy every key, type, and TTL into flat-priced managed Redis or Valkey.
Read - June 23, 2026
Migrating from Upstash to Layerbase
Upstash bills per request, which is great at zero traffic and surprising at scale. Here is how to move to flat-priced managed Valkey on Layerbase: copy every key with one API key, and swap the REST client for a standard Redis driver.
Read - June 23, 2026
Vercel KV alternatives: own your Redis in 2026
Vercel KV was first-party Redis built on Upstash, and Vercel has moved its storage to the Marketplace. If you want a Redis you own at flat pricing, here is how to move to managed Valkey with the KV_URL you already have.
Read - June 22, 2026
Should you use Cloud Clusters Redis hosting (rclusters)?
A fair review of Cloud Clusters Redis hosting (rclusters.com) and an honest comparison with Layerbase Cloud, which also offers Valkey and the VQueue queue platform: free tier, Redis version, branching, and local tooling.
Read - June 20, 2026
Run Postgres, Valkey, and Qdrant in one Lovable app
Most real Lovable apps end up needing more than one database. Here is how to provision Postgres plus a cache plus vector storage together and wire them all into the same project.
Read
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. Deliveries are signed and support scheduled delays; failed deliveries are retried automatically and land in a DLQ you can inspect and re-enqueue from the dashboard. No separate signup, no separate billing.