Deploy and Host Quickwit on Railway

Deploy Quickwit behind an authenticated gateway with private PostgreSQL metadata, durable Railway Bucket index storage, and a persistent Ingest V2 WAL.

About Hosting Quickwit

Quickwit is an Apache-2.0 search engine built for logs and traces. This template runs its search, indexing, control-plane, metastore, and janitor roles in one private service, while an authenticated gateway provides public UI and REST access.

Why Deploy Quickwit on Railway

Railway supplies the private service network, PostgreSQL metadata store, S3-compatible Bucket, persistent WAL volume, generated credentials, and health-checked public gateway in one deployment. The result preserves Quickwit's durable storage model without exposing its unauthenticated listener.

Common Use Cases

Search application and infrastructure logs retained in object storage.
Build a small-team observability or trace-search service.
Evaluate Quickwit APIs and index mappings with durable metadata and splits.

Dependencies for Quickwit Hosting

The template includes every required dependency and generates all credentials automatically.

Deployment Dependencies

Quickwit 0.9.0 for indexing and search.
PostgreSQL 17 for metadata.
A Railway Bucket for committed index splits.
Caddy 2.10 for Basic Auth and public reverse proxying.
Two 5 GB volumes for PostgreSQL and Quickwit's Ingest V2 WAL/local data.

After deployment, open Quickwit Gateway and use its generated QUICKWIT_USERNAME and QUICKWIT_PASSWORD. Only the gateway receives a public domain; the Quickwit API, PostgreSQL database, and object-storage credentials remain private.

The template is single-node and intended for evaluation and small-to-medium search or observability workloads. Back up PostgreSQL, the Railway Bucket, and the Quickwit volume together before upgrades.