← Templates · Databases
IN
Inngest
CommunityDurable function platform for event-driven background jobs — step functions, retries, and scheduling with a built-in dashboard.
| Runs | inngest/inngest:v1.46.0 |
|---|---|
| Stack | go |
| Provisioned for it | postgres |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions postgres alongside it automatically — zero-downtime deploys, automatic backups and scaling come from the same platform, on a server you already pay for.
Deploying Inngest is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Event-driven background jobs and durable step functions for your own app
- A self-hosted alternative to Inngest Cloud for scheduling, retries, and fan-out workflows
- Local dev-server-style orchestration wired to a real Postgres for production persistence
Good to know
- Postgres is wired up automatically for run history and queue state
- Register your app's SDK endpoint (the URL your Inngest functions are served from) from this app's dashboard after deploy — INNGEST_EVENT_KEY and INNGEST_SIGNING_KEY are the values your app's Inngest client needs to connect