Deploy and Host Dragonfly on Railway

Dragonfly is a modern in-memory data store, fully compatible with the Redis and Memcached protocols, built for much higher throughput on a single node.

About Hosting Dragonfly

This template runs the official docker.dragonflydb.io/dragonflydb/dragonfly image with a persistent volume at /data (snapshots every 30 minutes). Dragonfly serves its status page over HTTP on the same port, which is what the public URL shows (HTTP basic auth: username default, password from REDIS_PASSWORD; /metrics is open for Prometheus). The Redis protocol is protected by the same generated password.

Common Use Cases

Drop-in replacement for Redis as a cache, queue or session store
Use it from other services on the same Railway project via the private address dragonfly.railway.internal:6379
Check memory, keys and connections on the built-in status page

Dependencies for Dragonfly Hosting

One service with a volume; nothing else

Deployment Dependencies

Why Deploy Dragonfly on Railway?

Railway gives you a public HTTPS URL, a persistent volume and automatic restarts with no server to maintain. Connect from your other services with redis://default:${{Dragonfly.REDIS_PASSWORD}}@${{Dragonfly.RAILWAY_PRIVATE_DOMAIN}}:6379 (adjust the service name if you rename it).