KeyDB
Coolify deploys KeyDB as a standalone Redis-compatible datastore on the selected server and destination. A new resource gets a generated password, a persistent volume at /data, an internal connection URL, and a health check.
KeyDB is a Redis-compatible datastore with multithreading and support for Redis commands and clients.
Create a KeyDB database
Open New Resource
Open the project and environment where the database should live, then select New Resource.
Select KeyDB
Under Databases, select KeyDB. You can also search for KeyDB by name.
Select a server
Select the server that should run KeyDB. Build servers cannot be selected because they do not host running database resources.
Select a destination
Select the Docker network destination that KeyDB should join.
Review the generated configuration
Coolify creates the resource and opens General. Review the image, generated password, SSL settings, and connection URLs. Keep the default private networking unless an external client requires access.
Start KeyDB
Select Start and follow the startup output. Wait until KeyDB is running and healthy, then copy the KeyDB URL (internal) into applications on the same destination network.
Default configuration
| Setting | Default or behavior |
|---|---|
| Internal port | 6379; TLS uses 6380 |
| Default image | eqalpha/keydb:latest |
| Authentication | Generated password |
| Data mount | /data |
| Scheduled database backups | Not supported by Coolify |
| SSL | Supported with SSL |
KeyDB uses the Redis protocol and does not expose a username field in the Coolify database form.
Connect to KeyDB
Use the KeyDB URL (internal) for an application on the same Coolify destination network:
redis://:<password>@<database-container>:6379/0With SSL enabled, use the generated rediss URL and TLS port 6380. When Public access > Access is Public through TCP proxy, use the generated KeyDB URL (public).
Configure KeyDB
Open General to change the image, password, Port mappings, public proxy, Custom KeyDB configuration, and supported custom Docker options. Open Persistent Storage to manage the /data volume.
Custom KeyDB configuration is written as the configuration file used to start KeyDB. When it is set, Coolify uses that file and adds the password only when the file does not already define requirepass. Include persistence and other required settings in the file.
Backups and persistence
Coolify does not create scheduled database backups for KeyDB. Keep the /data persistent volume and configure KeyDB's supported persistence or replication features when you need recovery copies. Test restores independently.
SSL and health checks
KeyDB exposes SSL without an SSL mode selector. See Database SSL for the CA certificate mount and TLS connection workflow.
Configure the Docker health check under Healthcheck and restart KeyDB after saving.
Official KeyDB resources
Password environment variable
For a new database, REDIS_PASSWORD controls the server password and connection URLs. Databases created before this release keep their stored password unless the variable references a secret manager. After changing a remote secret, restart the database and verify connections.