Deploy Inngest
Self-hosted durable workflows and background jobs, with dashboard login
Just deployed
Just deployed
/var/lib/postgresql/data
Redis
Just deployed
/data
Deploy and Host Inngest on Railway
Inngest is an open-source engine for durable workflows and background jobs. Your app sends events, and Inngest runs the matching functions step by step, saving each step's result, retrying failures, and handling queues, crons, delays, concurrency and rate limits. Its dashboard shows every event, run and step.
About Hosting Inngest
Inngest ships as a single binary that contains the event API, queue, executor and dashboard. This template runs it from Inngest's official v1.53.0 image with Railway Postgres for apps, events and run history, and Railway Redis for the queue and run state. The event key, the signing key and the dashboard password are generated at deploy time. The self-hosted dashboard has no login of its own, so a small Caddy proxy in front asks for one. The routes your SDKs call are still checked by Inngest's event and signing keys. To finish, point your app at the private URL and sync it once.
Common Use Cases
- Durable background jobs for an app already on Railway: emails, webhooks, imports, billing runs
- Multi-step AI and LLM workflows that resume after failures without redoing finished steps
- Scheduled jobs (cron), delayed jobs, fan-out and event-driven pipelines with concurrency and rate limits
Dependencies for Inngest Hosting
- PostgreSQL (Railway Postgres, included)
- Redis (Railway Redis, included)
Deployment Dependencies
- Inngest self-hosting docs: https://www.inngest.com/docs/self-hosting
- Inngest v1.53.0 release: https://github.com/inngest/inngest/releases/tag/v1.53.0
- Template source (updates arrive from here): https://github.com/aalfath/inngest-railway-template
Implementation Details
Add these variables to the app service in your Railway project that uses an Inngest SDK. They use the private network, so events never leave Railway:
INNGEST_DEV=0
INNGEST_BASE_URL=http://${{Inngest.RAILWAY_PRIVATE_DOMAIN}}:8288
INNGEST_EVENT_KEY=${{Inngest.INNGEST_EVENT_KEY}}
INNGEST_SIGNING_KEY=${{Inngest.INNGEST_SIGNING_KEY}}
Then sync your app once with curl -X PUT https://YOUR-APP-DOMAIN/api/inngest. To sync on every Inngest restart instead, set INNGEST_SDK_URL=http://YOUR-APP.railway.internal:YOUR-APP-PORT/api/inngest on the Inngest service. Workers using Inngest Connect reach the gateway at ${{Inngest.RAILWAY_PRIVATE_DOMAIN}}:8289.
Open the dashboard at the Inngest service's public domain and log in as admin with the DASHBOARD_PASSWORD variable. Optional settings such as INNGEST_POLL_INTERVAL or INNGEST_QUEUE_WORKERS can be added as variables (any inngest start flag works as an INNGEST_ variable, for example --poll-interval becomes INNGEST_POLL_INTERVAL). Leave INNGEST_POSTGRES_URI empty to use SQLite on a volume mounted at /data instead.
Licence: Inngest is under the Server Side Public License (SSPL) with a delayed Apache 2.0 release. Self-hosting it for your own apps is allowed. Read the licence before you offer Inngest itself as a service to others.
Why Deploy Inngest 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 Inngest 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
