Inngest server

inngest.com · 2 records in Developer services · JSON

Records 2

caveatInngest
Developer servicesfree tieridentity emailno cardlimit volume-quotaevidence documentedstale on 2026-12-01
self-hosted, last resortInngest server (self-hosted)
Developer servicesverdict qualifies-with-caveatidentity anonymousno cardevidence documentedstale on 2026-12-02

Inngest

Developer services

www.inngest.com/pricingHosted durable execution and event orchestrationdev-services/inngestJSON compare report an error

Free allowance: Free: 50,000 executions and 500,000 events ingested per month, 5 concurrent steps, no credit card required
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: emailno card, no phone
Binding limit: volume-quota50,000 executions per month; 500,000 events ingested per month
Evidence: documented27 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-12-01checked 2026-10-31 (live); stale on 2026-12-01

Free tier	Free: 50,000 executions and 500,000 events ingested per month, 5 concurrent steps, no credit card required unit requests; metered on request-count; An execution is one function run or one step execution, so a run with five steps uses six. The Free plan also allows 3 active workspaces, 5 apps per workspace, 100 functions per app and 2 active branch deploys; a run may last 30 days including sleeps. Function code runs on the user's own host, which Inngest calls.
Price	none stated
Limits	volume-quota (binding) 50,000 executions per month source volume-quota (binding) 500,000 events ingested per month source per-object-cap 256 KiB per event source retention-clamped 24 hours of trace and log history source 5 concurrent steps, queue depth 100,000, event batches of 5 with a 30-second batch timeout. A step may run up to 2 hours, subject to the host's shorter timeout. Since October 20, 2026 executions in runs with checkpointing are no longer undercounted, so a Free account may reach the cap sooner.
Binding	volume-quota 50,000 executions a month binds first, and each step counts, so multi-step functions reach it in fewer runs.
Identity	email The sign-up form asks for an email address and a password, or GitHub or Google sign-in; the free tier needs no card.
Egress	not applicable: Inngest calls the user's function endpoints; no traffic allowance is published
Per-object cap	256 KiB per event; 32 MiB of function run state
Retention	trace and log history: 24 hours on Free
Interface	rest, cli REST API at api.inngest.com (v1 stable, v2 stable in development) for events, function runs and environments; every endpoint is also exposed in the Inngest CLI endpoint: https://api.inngest.com/v1
Tooling	the Inngest SDKs in the user's app, the Inngest CLI (inngest api) and the local dev server (npx inngest-cli dev). As a last resort the open-source server can be installed and run by the user on a rented or free machine.
Composes with	Adds retries, schedules, sleeps and fan-out to functions served from a free serverless host, so it composes with a free compute tier that has no queue or cron of its own.
Reliability	Since October 20, 2026 executions in checkpointed runs count in full, so a Free account can hit its cap sooner than before.
Evidence note	documented Plan limits and sign-up fields are read on first-party pages; the REST API answered HTTP 401 to a request without a key. A function run is not measured.
Parsed numbers	has-free-tier 1 per-object-cap 256 KiB retention-clamped 24 hours

Evidence 27

date	source	what it proved
2026-10-30	www.inngest.com/pricing	the free plan needs no credit card
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free includes 50,000 executions a month
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free includes 500,000 events a month
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free allows 5 concurrent steps
2026-10-30	www.inngest.com/docs/usage-limits/inngest	a Free event is at most 256 KiB
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free queue depth is 100,000
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free event batches hold 5 events
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free batch timeout is 30 seconds
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free allows 3 active workspaces
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free allows 5 apps per workspace
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free allows 100 functions per app
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free keeps 24 hours of trace and log history
2026-10-30	www.inngest.com/docs/usage-limits/inngest	a Free run may last 30 days including sleeps
2026-10-30	www.inngest.com/docs/usage-limits/inngest	an execution is a run or a step
2026-10-30	www.inngest.com/docs/usage-limits/inngest	a five-step run uses six executions
2026-10-30	www.inngest.com/docs/usage-limits/inngest	Free allows 2 active branch deploys
2026-10-30	www.inngest.com/docs/usage-limits/inngest	function run state is capped at 32 MiB
2026-10-30	www.inngest.com/docs/usage-limits/inngest	a step may run up to 2 hours, subject to the host timeout
2026-10-30	www.inngest.com/docs/usage-limits/inngest	from October 2026 Free accounts may reach the execution cap sooner
2026-10-30	www.inngest.com/docs/usage-limits/inngest	function code runs on the user's own host
2026-10-31	app.inngest.com/sign-up	the sign-up form asks for an email address and a password
2026-10-31	app.inngest.com/sign-up	GitHub and Google sign-in are offered
2026-10-31	app.inngest.com/sign-up	the sign-up page states the free tier needs no card
2026-10-30	api-docs.inngest.com/	a REST API covers events, function runs and environments
2026-10-30	api-docs.inngest.com/	every API endpoint is also in the CLI
2026-10-31	probe: `https://api.inngest.com/v1/events`	the REST API at api.inngest.com answered HTTP 401 to a request without a key
2026-10-30	www.inngest.com/docs/self-hosting	the server can be self-hosted

Inngest server (self-hosted)

Developer services

www.inngest.com/docs/self-hostingSelf hosted durable execution and event orchestration server (open source Inngest server)dev-services/inngest-serverJSON compare report an error

Free allowance: The Inngest server is published on GitHub: installing the Inngest CLI, a single binary that includes all Inngest services, and running inngest start gives a self-hosted server on a machine the user runs, with SQLite for persistence by default
Verdict: self-hosted, last resortverdict qualifies-with-caveat: usable, with a named limit or an unprobed read path. Self-hosted options are listed last, because this site is for users who have no hardware.
Cost: not stated
Identity: anonymousno card, no phone
Binding limit: noneno named constraint binds
Evidence: documented30 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-12-02checked 2026-11-01 (live); stale on 2026-12-02

Free tier	The Inngest server is published on GitHub: installing the Inngest CLI, a single binary that includes all Inngest services, and running inngest start gives a self-hosted server on a machine the user runs, with SQLite for persistence by default unit none; metered on none; The hosted Inngest free tier (dev-services/inngest) comes first. The user's function code stays on an app host of the user's own, served through HTTP or Connect.
Price	none stated
Limits	request-rate 100 queue workers run in parallel on one server by default (--queue-workers) source inngest start runs Inngest as a single-node service labelled beta, and with the default SQLite database the server does not scale beyond a single node. The signing key must be a hexadecimal string with an even number of characters.
Binding	none The self-hosting pages state no execution or event quota; the machine, Redis and the database bound throughput, and 100 queue workers run in parallel by default.
Identity	anonymous No Inngest account is needed: the user creates an event key and a signing key in any format they choose (the signing key a hexadecimal string with an even number of characters) and passes them to inngest start.
Egress	not set by the software: the server invokes the user's functions over HTTPS or the Connect gateway from the machine the user runs it on, so the network terms of that host apply
Per-object cap	not stated on the self-hosting pages read
Retention	the server does not delete old PostgreSQL rows for events, runs or traces by itself, so retention is whatever the user's cleanup keeps; the default database is SQLite at ./.inngest/main.db
Interface	rest, graphql, cli the server provides GraphQL and REST APIs for programmatic access and management of system resources, with the Event API and the Dashboard UI on port 8288 and the Connect gateway on port 8289; the Inngest CLI starts it with inngest start, and the Inngest SDKs in the user's app send events with an event key and share a signing key with the server
Tooling	the user installs and runs the Inngest server on a rented or free machine: the Inngest CLI (npm install -g inngest-cli, the inngest/inngest Docker image or a release binary) started with inngest start, with SQLite and an in-memory Redis by default, or with PostgreSQL and Redis through the Docker Compose example or the Helm chart for Kubernetes; the Inngest SDKs in the user's own app.
Composes with	Last resort after the hosted durable-execution offers (the hosted Inngest free tier in dev-services/inngest, then Temporal Cloud in dev-services/temporal-cloud and the n8n Cloud trial in dev-services/n8n-cloud): the user's functions still run on a host that serves them, and the server adds the queue, schedules, retries and fan-out from a machine that the user installs and keeps running.
Reliability	Inngest's support team does not guarantee direct support for self-hosted instances; inngest start is labelled beta; without external services the queue and run state live in an in-memory Redis whose snapshots are saved to SQLite periodically and at shutdown, a Docker run that does not mount the SQLite directory loses the database with the container, and PostgreSQL rows for events, runs and traces are not removed automatically.
Notes	Self-hosted software and the last resort: the hosted offers come first (the hosted Inngest free tier dev-services/inngest, the Temporal Cloud credit dev-services/temporal-cloud and the n8n Cloud trial dev-services/n8n-cloud). This record is no duplicate of dev-services/inngest: it is the server that the user installs and runs.
Evidence note	documented Install, configuration, persistence and the interfaces are read on the first-party self-hosting documentation and the repository README; the server was not installed or run, and the self-hosting pages state no price or quota.

Evidence 30

date	source	what it proved
2026-11-01	www.inngest.com/docs/self-hosting	self-hosting is supported as of the Inngest 1.0 release
2026-11-01	www.inngest.com/docs/self-hosting	the Inngest CLI is a single binary that includes all Inngest services and is all that self-hosting needs to install
2026-11-01	www.inngest.com/docs/self-hosting	the source code for Inngest and all its services is available on GitHub
2026-11-01	www.inngest.com/docs/self-hosting	the CLI binary can be downloaded directly from the GitHub releases
2026-11-01	www.inngest.com/docs/self-hosting	the Event API receives events from the SDKs over HTTP
2026-11-01	www.inngest.com/docs/self-hosting	the signing key signs and validates data between the server and the apps
2026-11-01	www.inngest.com/docs/self-hosting	the self-hosting page includes a Docker Compose example
2026-11-01	www.inngest.com/docs/self-hosting	the CLI installs as a Docker image
2026-11-01	www.inngest.com/docs/self-hosting	the CLI installs from npm
2026-11-01	www.inngest.com/docs/self-hosting	inngest start serves on port 8288 with SQLite for persistence, and the Connect gateway is on port 8289
2026-11-01	www.inngest.com/docs/self-hosting	part of the text of Interface, above
2026-11-01	www.inngest.com/docs/self-hosting	the event and signing keys are chosen by the user in any format
2026-11-01	www.inngest.com/docs/self-hosting	part of the text of Limits, above
2026-11-01	www.inngest.com/docs/self-hosting	by default the queue and state store run in an in-memory Redis server
2026-11-01	www.inngest.com/docs/self-hosting	the default database is SQLite at ./.inngest/main.db and snapshots are saved periodically and before shutdown
2026-11-01	www.inngest.com/docs/self-hosting	the default SQLite persistence does not scale beyond a single node
2026-11-01	www.inngest.com/docs/self-hosting	an external PostgreSQL database is set with the postgres-uri flag
2026-11-01	www.inngest.com/docs/self-hosting	an external Redis server is set with the redis-uri flag
2026-11-01	www.inngest.com/docs/self-hosting	the server does not delete old PostgreSQL rows for events, runs or traces
2026-11-01	www.inngest.com/docs/self-hosting	each Inngest server runs 100 queue workers in parallel by default
2026-11-01	www.inngest.com/docs/self-hosting	inngest start is a single-node service labelled beta
2026-11-01	www.inngest.com/docs/self-hosting	part of the text of Reliability, above
2026-11-01	www.inngest.com/docs/self-hosting	a Helm chart deploys the server on Kubernetes
2026-11-01	www.inngest.com/docs-markdown/platform-and-operations/self-h	the application hosts its function code separately from the self-hosted server
2026-11-01	www.inngest.com/docs-markdown/platform-and-operations/self-h	the app serves its function code to the self-hosted server through HTTP serve() or Connect
2026-11-01	www.inngest.com/docs-markdown/platform-and-operations/self-h	a Docker run without a mounted SQLite database loses the database with the container
2026-11-01	www.inngest.com/docs-markdown/platform-and-operations/self-h	part of the text of Reliability, above
2026-11-01	github.com/inngest/inngest	the repository states that self-hosting the Inngest server is possible
2026-11-01	github.com/inngest/inngest	the server invokes the user's functions over HTTPS when triggering events arrive
2026-11-01	github.com/inngest/inngest	functions are written with the Inngest language SDKs