---
title: "Deploy Inngest | (Just Updated) Durable Workflows & Background Jobs, Data Survives Redeploys"
description: "Self-hosted durable workflows, jobs and cron; SQLite on a volume"
category: "Queues"
url: https://railway.com/deploy/inngest-or-just-updated-durable-workflow
---

# Deploy Inngest | (Just Updated) Durable Workflows & Background Jobs, Data Survives Redeploys

Self-hosted durable workflows, jobs and cron; SQLite on a volume

**[Deploy Inngest | (Just Updated) Durable Workflows & Background Jobs, Data Survives Redeploys on Railway](https://railway.com/template/inngest-or-just-updated-durable-workflow)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/inngest-or-just-updated-durable-workflow/manifest.json

- **Creator:** SuperSlowSloth
- **Category:** Queues

## Template content

### inngest

- **Image:** inngest/inngest:v1.46.0@sha256:9c4a2413bdbfa31a94ff54c32ae2dcc6613dbee84bc76db6cf6644d19e357e3e
- **Start command:** `/bin/sh -c 'echo "[railway] uid=$(id -u) data=$(stat -c %u:%g /data)"; test -w /data && echo "[railway] data writable"; exec inngest start --host 0.0.0.0 --port "$PORT" --sqlite-dir /data --signing-key "$INNGEST_SIGNING_KEY" --event-key "$INNGEST_EVENT_KEY"'`
- **Health check:** /health
- **Public domain:** Yes

## Documentation

# Deploy and Host Inngest on Railway

Inngest is an open-source durable execution engine: you write step functions in your own app, and Inngest handles events, retries, scheduling, concurrency, throttling and fan-out. This template runs the self-hosted Inngest server with a persistent SQLite database, so your event history and function runs survive redeploys.

## About Hosting Inngest

This template runs the official `inngest/inngest` image (pinned by digest) with `inngest start` as a single service. State is stored in SQLite on a volume mounted at `/data`. The dashboard and event API listen on the public domain. A signing key and an event key are generated at deploy as hex secrets (`INNGEST_SIGNING_KEY`, `INNGEST_EVENT_KEY`) and passed to the server. Point your Inngest SDK at the domain with `INNGEST_BASE_URL`, `INNGEST_EVENT_KEY` and `INNGEST_SIGNING_KEY`, then register your app's serve URL from the dashboard.

## 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.

- **Durable background jobs without a queue to babysit** — retries, delays and step memoization are built in.
- **State survives redeploys** — the SQLite database sits on a volume, not on ephemeral disk.
- **Keys generated for you** — signing and event keys are random hex secrets, nothing to type at deploy time.
- **No per-run SaaS fees** — run as many events and steps as your instance handles.

## Common Use Cases

- **Background jobs and cron** — email sends, webhooks, imports and scheduled tasks with automatic retries.
- **Multi-step workflows** — sleep for days, wait for an event, then continue, without writing a state machine.
- **AI agent pipelines** — chain LLM calls with retries, rate limits and concurrency control.

## Dependencies for Inngest Hosting

### Deployment Dependencies

- A volume mounted at `/data` (included in this template) for the SQLite database.
- An app using an Inngest SDK that exposes a serve endpoint.
- Upstream docs: https://www.inngest.com/docs/self-hosting


## Similar templates

- [Celery | Web, Worker and Scheduler as Three Services](https://railway.com/deploy/celery-or-web-work-1) — Web, worker and scheduler wired up: Celery on Redis, outcomes in Postgres.
- [Redpanda](https://railway.com/deploy/redpanda-1) — Redpanda 26.2: Kafka-compatible streaming, single node, with Kafbat UI.
- [smoothmq](https://railway.com/deploy/AJv-64) — A drop-in replacement for AWS SQS

Open this page in a browser: https://railway.com/deploy/inngest-or-just-updated-durable-workflow