Description

Deploys a self-hosted Inngest server for background jobs, scheduled tasks, and event-driven workflows. You write functions in your application code using the Inngest SDK (TypeScript, Python, or Go), send events to Inngest, and it handles execution, retries, scheduling, and concurrency control.

Installs a single Helm release in the inngest namespace with bundled Postgres and Redis as sub-charts -- no other blueprints or external databases needed. The event key and signing key authenticate your application's SDK with the Inngest server.

Useful as a cron replacement, for webhook delivery, multi-step workflows, or any async work where you want retries and observability. Enable "Expose Dashboard" to publish the Inngest UI at <installation-name>.<environment-domain> with auto-provisioned TLS.

Configuration Inputs

This blueprint accepts 6 configurable inputs to customize the installation for your environment.

exposeDashboardboolean

Publish the Inngest UI at a public HTTPS URL.

eventKeystring

Event key that your application uses when sending events to Inngest. Include this in your Inngest client configuration.

signingKeystring

Signing key that Inngest uses to sign webhook requests to your functions. Your SDK uses this to verify requests are authentic.

postgresPasswordstring

Password for the bundled Postgres instance.

postgresStorageSizeGinumber

Persistent storage size for Postgres in GiB.

redisStorageSizeGinumber

Persistent storage size for Redis in GiB.