Skip to main content
Filament does not currently publish a supported one-click Railway template. For a temporary evaluation, deploy ghcr.io/galaxy-io/filament/standalone and expose port 8080. Its connections, pipelines, runs, and checkpoints are held in memory and disappear whenever the service restarts or redeploys. For durable operation, run the split server and control-plane images with Postgres and NATS. Railway has no Kubernetes Jobs API, so set DISPATCH_MODE=inproc; runs then share the control-plane service’s CPU and memory. Use the configuration reference for required variables. This deployment path is manual and is not currently covered by a Filament template or deployment test.