Inngest

Inngest is a durable workflow orchestration platform that lets developers run reliable stateful step functions and AI workflows on serverless, self-hosted, or…

  • Automation
  • Development
Inngest is a durable workflow orchestration platform that lets developers run reliable stateful step functions and AI workflows on serverless, self-hosted, or edge runtimes.

Platform availability

Available on 2 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 8 days ago
Popular
766,034 GitHub stars
Easy to install
352 install platforms, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
6,034
Open issues
284
Last commit
2026-11-13
Latest release
v1.53.0
Activity
rising

Checked 8 days ago - source: GitHub (inngest/inngest)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Set Inngest keys before starting Docker Generate an event key (a code used to send events) and a signing key (a secret used to verify events), then run the Docker command with those settings supplied. Without them, you may start Inngest without the basic credentials your app expects. source
  • Open ports 8288 and 8289 Run the Docker command so it exposes ports 8288 and 8289 (the network doorways Inngest is told to use) on your machine. If those ports are not reachable, other apps or devices cannot connect to Inngest. source
  • This Docker setup is disposable Treat the example as a throwaway test, and add persistent storage if you need to keep Inngest data. The example does not save the SQLite database (the small local file that holds records) to a permanent place, so deleting the container can also delete your local data. source

Fetched 8 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I deploy my Inngest functions to my own infrastructure?

Yes. You can deploy your functions to your own infrastructure and sync them with a self-hosted Inngest server.

Do I need hosted Inngest for local development?

You can run the Inngest Dev Server for a local development experience with production parity.

Is self-hosting appropriate if I have data residency needs?

Self-hosting Inngest is appropriate for teams with data residency requirements or those wanting to avoid vendor lock-in on workflow infrastructure.

Answers sourced from github.com, github.com

Community

Collected 8 days ago - public community threads