Deploy and Host Manifest on Railway

About Hosting Manifest on Railway

Manifest runs cleanly on Railway as a Docker-first deployment: one web service for the dashboard/API and one managed PostgreSQL service for persistent state.

Tech Stack

Manifest (NestJS + SolidJS single-service app image)
PostgreSQL 18 (Railway template image)
Docker images from Docker Hub and GHCR
Railway managed networking and environment variables

Why Deploy Manifest on Railway

Railway gives fast one-click container deployment, built-in private networking between services, managed Postgres volumes, and automatic HTTPS domains for immediate browser access.

Common Use Cases

Cost-optimized model routing for personal AI agents
Unified dashboard for token/cost/message analytics
Self-hosted OpenAI-compatible gateway for multi-provider routing
Team/internal experimentation with routing tiers and fallbacks

Deployment Notes

Use the pinned upstream image manifestdotbuild/manifest:5.55.0 with no custom start command. Set PORT=2099 for routing, wire DATABASE_URL from the Postgres service, and keep BETTER_AUTH_URL aligned with the public domain. Postgres persistence is at /var/lib/postgresql/data.

Dependencies for Manifest on Railway

Manifest requires PostgreSQL for application data, migrations, auth/session storage, and analytics records.

Deployment Dependencies

Service	Image	Port	Volume
manifest	manifestdotbuild/manifest:5.55.0	2099	-
postgres	ghcr.io/railwayapp-templates/postgres-ssl:18	5432	/var/lib/postgresql/data