Enzonic Databases
Free Redis-compatible hosting with Valkey
Managed Valkey 8, the open source Redis fork. Use your Redis client over TLS.
Overview
Valkey is the open source, Redis-compatible key-value store. Use it for caching, sessions, rate limits and queues with any Redis client, over TLS, on the Free plan or with always-on paid plans.
- Valkey 8, compatible with Redis clients and commands
- TLS on every connection (rediss://)
- A REDIS_URL ready for your app
- Connect it to an Enzonic Deploy project in two clicks
- Version
- Valkey 8
- Port
- 6379
- Connection variable
- REDIS_URL
- Free plan
- Included
- Storage on Free
- 3 GB each, 10 GB total
- Compute on Free
- Up to 0.25 vCPU / 512 MB, scales to zero after 5 min idle
Good for
- Caching and session storage
- Rate limiting and counters
- Job queues such as BullMQ
Connect from your code
The console shows the full connection string with your password. Every connection uses TLS.
Node.js (redis)
import { createClient } from 'redis';
// The gateway routes by TLS SNI, so pass the host as servername.
const client = await createClient({ url: process.env.REDIS_URL, socket: { servername: '<name>.db.enzonic.com' } }).connect();Python (redis-py)
import os, redis
r = redis.from_url(os.environ['REDIS_URL'])Go (go-redis)
opt, _ := redis.ParseURL(os.Getenv("REDIS_URL"))
rdb := redis.NewClient(opt)Deploy guides with a Valkey example: Eleventy, Python functions
Limits per plan
| Feature | Free free | Starter $5/mo | Pro $10/mo | Growth $19/mo | Business $29/mo |
|---|---|---|---|---|---|
| Enzonic Databases | |||||
| Databases | 10 (any engines) | 25 | 50 | 100 | 200 |
| Storage | 3 GB each, 10 GB total | 20 GB total | 40 GB total | 75 GB total | 100 GB total |
| Compute | Up to 0.25 vCPU / 512 MB, scales to zero after 5 min idle | Up to 1 vCPU / 2 GB, always-on option | Up to 2 vCPU / 4 GB, always-on option | Up to 4 vCPU / 8 GB, always-on option | Up to 8 vCPU / 16 GB, always-on option |
| Branches | 10 per database | 15 per database | 25 per database | 50 per database | 100 per database |
| Backups | Daily, 1 day kept | Daily, 7 days kept + PITR (Postgres) 7 days | Daily, 7 days kept + PITR (Postgres) 7 days | Daily, 14 days kept + PITR (Postgres) 14 days | Daily, 30 days kept + PITR (Postgres) 30 days |
| Connections (pooled) | 1,000 | 2,500 | 5,000 | 10,000 | 10,000 |
| Read replicas | Not included | Not included | 1 | 2 | 3 |
| Custom hostnames | Not included | Included | Included | Included | Included |
| Engines | Postgres, MySQL, MariaDB, Valkey, FerretDB, libSQL, PocketBase, Supabase (1) | Postgres, MySQL, MariaDB, Valkey, FerretDB, libSQL, PocketBase, Supabase (2) | All, including ClickHouse and Supabase | All, including ClickHouse and Supabase | All, including ClickHouse and Supabase |
Questions
Does my Redis client work with Valkey?
Yes. Valkey speaks the Redis protocol, so node-redis, ioredis, redis-py, go-redis and the others connect with a rediss:// URL.
Why does node-redis need the servername option?
Connections are routed by the TLS server name. Most clients send it automatically; node-redis needs socket.servername set to the database host.
Create your Valkey database
A connection string in a few seconds. Free plan, no card.