Serverless Redis

Yes, and it is a plan rather than a trial: Free is $0/mo, asks for no card, and has no expiry date. It covers 2 databases, 5 GB of storage, and up to 20 concurrent connections, with TLS on by default, snapshot persistence to disk, 1 manual backup slot you take and restore from the dashboard, a web key-value console, and the Upstash-compatible REST endpoint for edge runtimes. What Free does not include is an always-on pool: a free Redis database hibernates after 15 minutes with no connections, so the first request after an idle spell pays the wake, roughly 1 to 5 seconds, as long as your client sends the TLS servername. Solo at $5/mo and Pro at $15/mo lift the connection cap, add scheduled snapshots, and let you pin a database always-on.

Redis is an in-memory data store addressed through a small command set over keys and values, with sorted sets, lists, and pub/sub on top. It is the usual pick for caches, session stores, rate limiters, queues, and leaderboards rather than for primary application data. Layerbase runs it as a managed endpoint with TLS, a web key-value console, and an Upstash-compatible REST endpoint for runtimes that cannot hold a TCP socket.

Layerbase Cloud runs a Redis version from before the BSL/SSPL license transition, so existing Redis clients work unchanged. For new projects we recommend Valkey (a Linux Foundation fork) for cleaner licensing: same wire protocol, same drivers.

Redis's license change put the upstream project under a source-available license that restricts redistribution. Valkey is the Linux Foundation's BSD-licensed fork of the last truly-open Redis version. For greenfield projects, Valkey is the safer long-term bet; for existing apps that depend on the upstream version, Redis on Layerbase still works.

Yes. The endpoint speaks the standard Redis wire protocol on the allocated TLS port. redis-cli, ioredis, redis-py, go-redis, Jedis: anything that talks Redis works. The connection string format matches what you would point at a self-hosted Redis.

Yes. Redis-family databases on Layerbase also speak the Upstash REST API, picked via the hostname suffix. That makes it usable from Cloudflare Workers and other edge runtimes that cannot hold a TCP connection.

Every Redis database snapshots to disk on the stock RDB save schedule, Free included, and hibernation shuts the server down with a final save, so a sleep and wake cycle does not cost you keys. AOF is off, which is the same trade a default Redis makes. Free also gets 1 manual backup slot, taken and restored from the dashboard; what the paid plans add on top is scheduled snapshots (7d or 30d retention) with one-click restore.

It hibernates after 15 minutes idle, keeping its hostname, port, and data. If it stays hibernated for 14 days (7 days if you never connected to it) it is archived: the address is released and an explicit Restore, about 10 to 30 seconds, brings it back. Data and backups are kept. After 90 continuous days archived the live resources are reclaimed and the most recent backup is kept and still restorable. Paid plans are never auto-archived.

For a low-traffic side project, yes. For anything that cannot absorb a cold start, no: Free has no always-on pool, so an idle database sleeps and the first request after that pays the wake. Free also caps concurrent connections at 20 and gives you 1 manual backup slot rather than scheduled snapshots. Solo at $5/mo and Pro at $15/mo lift all three.