Self-host Inngest with Levelrail

A durable workflow engine for background jobs, queues, cron and event-driven functions, backed by Postgres and Redis.

  • Authorinngest
  • LicenceLicenseRef-SSPL-1.0-DOSP
  • Memory512 MiB
  • Archarm64
  • Services3

How to self-host Inngest

  1. Pull the images

    3 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • inngest/inngest:v1.27.0
    • redis:7-alpine
  2. Create the app

    3 services start in a single Compose app, with 2 named volume mounts for your data, on port 8288.

  3. Fill in the secrets

    4 secrets are generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Inngest requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
8288
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
LicenseRef-SSPL-1.0-DOSP, source available
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Inngest. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Inngest docs page.

Deploy Inngest your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Inngest from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain db=app.example.com.

levelrail-cli templates install inngest --name my-inngest

Deploy Inngest with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/inngest/install \
  -d '{
    "name": "my-inngest"
  }'

Inngest configuration

Inngest services

ServiceImagePortsVolumes
db postgres:16-alpine none pgdata -> /var/lib/postgresql/data
inngest inngest/inngest:v1.27.0 8288 none
redis redis:7-alpine none redis -> /data

Inngest environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template
INNGEST_EVENT_KEY inngest Generated at deploy
INNGEST_POSTGRES_URI inngest Generated at deploy
INNGEST_REDIS_URI inngest Preset by the template
INNGEST_SIGNING_KEY inngest Generated at deploy

Ports and volumes

Ports
8288
Volumes
2 named mounts: pgdata -> /var/lib/postgresql/data, redis -> /data

Inngest FAQ

How much memory does Inngest need?

The catalog lists about 512 MiB of memory for Inngest across its 3 services.

Does Inngest run on arm64?

For Inngest, an arm64 image is published; amd64 is image published.

What licence is Inngest under?

Inngest is licensed under LicenseRef-SSPL-1.0-DOSP, which is source-available, so read the terms before commercial use.

Does Inngest need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Inngest bundle?

The template includes Postgres and Redis, running as its own service.

Which ports does Inngest use?

Inngest listens on port 8288 inside the stack.

Where does Inngest keep its data?

In named volumes: pgdata mounted at /var/lib/postgresql/data and redis mounted at /data.

Can I deploy Inngest on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id inngest for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, inngest/inngest:v1.27.0, redis:7-alpine is what you deploy there.

levelrail-cli templates install inngest --name my-inngest