Deploy Temporal
Durable workflows: Temporal server + Web UI with login on Railway Postgres
Just deployed
/var/lib/postgresql/data
Just deployed
Temporal UI
Just deployed
Deploy and Host Temporal on Railway
Temporal is an open-source durable execution platform. You write workflows as ordinary code in Go, Java, TypeScript, Python, .NET, PHP or Ruby, and the Temporal server records every step, so a workflow resumes where it left off after crashes, deploys or outages, with retries, timers and long-running state handled for you.
About Hosting Temporal
Self-hosting Temporal means running the Temporal server (frontend, history, matching and worker services), a database for workflow history and visibility, and the Web UI. This template runs Temporal 1.32.2 as one service on Railway Postgres. On every start it creates and migrates the temporal and temporal_visibility databases and registers the default namespace, so there is nothing to set up by hand. Elasticsearch is not needed: Postgres visibility supports custom search attributes. The Web UI 2.58.1 sits behind a login with a generated password. Your workers run as services in the same Railway project and connect over the private network.
Common Use Cases
- Reliable background jobs and order, payment or onboarding flows that must finish even when services fail
- Orchestrating microservices, data pipelines and scheduled jobs with retries and timeouts
- Long-running AI agent and LLM workflows with human-in-the-loop steps
Dependencies for Temporal Hosting
- Postgres (Railway Postgres, included) for workflow history and visibility
- Your own Temporal workers, built with any Temporal SDK
Deployment Dependencies
- Temporal server release: https://github.com/temporalio/temporal/releases/tag/v1.32.2
- Temporal UI release: https://github.com/temporalio/ui/releases/tag/v2.58.1
- Self-hosting guide: https://docs.temporal.io/self-hosted-guide
- Template source: https://github.com/aalfath/temporal-railway-template
Implementation Details
Services: Temporal (server, private network only), Temporal UI (public, basic auth) and Postgres. Log in to the UI as admin with the UI_PASSWORD shown in the Temporal UI service's Variables tab.
Point workers in the same project at the frontend:
TEMPORAL_ADDRESS=${{Temporal.RAILWAY_PRIVATE_DOMAIN}}:7233
TEMPORAL_NAMESPACE=default
The gRPC frontend has no TLS or authorizer, which is safe because it is reachable only inside the project. Don't add a public TCP proxy to port 7233 without configuring mTLS first. The temporal CLI is included in the Temporal service (railway ssh, then for example temporal operator namespace create --namespace orders). Optional: NAMESPACE_RETENTION (default 72h) and DEFAULT_NAMESPACE on Temporal; OIDC login and other TEMPORAL_* UI settings on Temporal UI. Updates arrive from the template repo; apply Temporal minor versions in order.
Why Deploy Temporal 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 Temporal 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.
Template Content
