Railway

Deploy Inngest Single Node (SQLite)

Platform for running durable, event‑driven workflows and background jobs

Deploy Inngest Single Node (SQLite)

Just deployed

/app/data

Deploy and Host Inngest Single Node (SQLite) on Railway

Inngest is an event-driven durable execution platform for running reliable background functions, workflows, and AI agents. The single node SQLite configuration bundles all services—Event API, Runner, Executor, Queue, and Dashboard—into a single process with zero external dependencies, using embedded SQLite for persistence and an in-memory Redis implementation for queuing and state.

About Hosting Inngest Single Node (SQLite)

Hosting Inngest in single node mode is designed for simplicity. The inngest start command runs all system services in one process with no external database or queue dependencies. SQLite handles persistence by writing system state to disk, while a bundled in-memory Redis powers the queue and state store with periodic snapshots to disk. The server exposes port 8288 for the Event API, REST/GraphQL APIs, and Dashboard UI, and port 8289 for the Connect WebSocket gateway. Your application SDKs (TypeScript, Python, or Go) communicate with the server using event keys and signing keys for authentication. This setup is ideal for staging, CI/CD, lower-traffic production workloads, or air-gapped environments.

By default, the Inngest server uses SQLite for persistence. This is convenient for zero-dependency deployments, but does not support scaling beyond a single node. You may choose to run your own Postgres database or use a cloud-based Postgres service like AWS RDS, Neon, Supabase, etc.

Note on debugging: You can temporarily create a public HTTP endpoint (e.g. via Railway's public networking) to access the Inngest Dashboard UI for debugging. However, the Dashboard is not authenticated in self-hosted mode, so the public endpoint should be removed once debugging is complete to avoid exposing your event data and function configuration.

Common Use Cases

  • Run reliable background jobs with automatic retries, scheduling, and step-based workflows for applications built with TypeScript, Python, or Go
  • Orchestrate multi-step AI agent workflows with built-in concurrency control, throttling, rate limiting, and observability
  • Self-host a durable execution engine for staging, CI/CD pipelines, or production environments where zero external dependencies and full data control are required

Dependencies for Inngest Single Node (SQLite) Hosting

  • None — the single node SQLite configuration is fully self-contained with no external database or queue dependencies

Deployment Dependencies

Implementation Details

Key environment variables and configuration:

# Authentication (must be hexadecimal strings with even number of characters)
INNGEST_EVENT_KEY=your_event_key_here
INNGEST_SIGNING_KEY=your_signing_key_here

# Server ports
# 8288 - Event API, REST/GraphQL API, Dashboard UI
# 8289 - Connect WebSocket gateway

Start command:

inngest start --sqlite-dir /data --port 8288

Your application SDKs connect by setting:

INNGEST_BASE_URL=https://your-inngest-instance.railway.app
INNGEST_EVENT_KEY=your_event_key_here
INNGEST_SIGNING_KEY=your_signing_key_here

Why Deploy Inngest Single Node (SQLite) 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 Single Node (SQLite) 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

More templates in this category

View Template
Foundry Virtual Tabletop
A Self-Hosted & Modern Roleplaying Platform

Lucas
View Template
(v1) Simple Medusa Backend
Deploy an ecommerce backend and admin using Medusa

Shahed Nasser
View Template
peppermint
Docker-compose port for peppermint.sh

HamiltonAI