Deploy and Host Blobasaur on Railway

Blobasaur is a high-performance Redis-protocol blob store backed by sharded SQLite. Clients speak standard Redis commands (GET/SET/HGET/HSET, TTL) while data lands on a volume.

About Hosting Blobasaur

This template deploys ghcr.io/iamd3vil/blobasaur:latest with a persistent volume at /app/blob_data, a TCP proxy on Redis port 6379, and an optional Prometheus metrics domain on port 9090. On first boot the start command clears an empty volume so shard databases can be created cleanly. Connect with any Redis client to the TCP proxy endpoint Railway assigns.

Common Use Cases

Simple binary object cache/store with Redis clients
Namespaced blob storage without running a full Redis + object store stack
Sidecar blob backend for apps that already speak Redis protocol

Dependencies for Blobasaur Hosting

Persistent volume — SQLite shards under /app/blob_data
TCP proxy — public Redis access on application port 6379
Optional HTTP domain — metrics on /metrics (port 9090)

Deployment Dependencies

Blobasaur repository
Public image — ghcr.io/iamd3vil/blobasaur:latest

Implementation Details

No user secrets are required for a basic deploy. After deploy, copy the TCP proxy host/port from the Blobasaur service networking panel and point your Redis client there.

Why Deploy Blobasaur on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Blobasaur on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.