Deployment
Moving to production requires deploying your Inngest Functions on your favorite Cloud Provider and configuring it to allow the Inngest Platform to orchestrate runs:
Deploy on any platform or runtime
Inngest Functions can be deployed to any serverless cloud or container running on any server.
Deploy with Vercel
Use our Vercel Integration to deploy your Inngest Functions.
Deploy with DigitalOcean
Deploy your Inngest Functions on DigitalOcean.
Deploy with Cloudflare Pages
Deploy your Inngest Functions on Cloudflare Pages.
Deploy with Render
Deploy your Inngest Functions on Render.
Connect workers to Inngest
Use Connect for persistent worker-style deployments on long-running compute.
Use checkpointing in production
Resume durable functions quickly across steps, retries, and deploys.
Self-host Inngest
Self-host Inngest on your own infrastructure.
Most serverless and API-route deployments use the serve() HTTP handler. Long-running worker or container deployments can use Connect, which keeps a persistent connection open to Inngest. If you need to run the execution engine on your own infrastructure, see Self-hosting.
How Inngest handles Function Runs
The Inngest Platform hosts the Inngest Durable Execution Engine, responsible for triggering and maintaining the state of Function runs happening on your Cloud Provider:
The Inngest Platform relies on Event and Signing Keys, as well as other security mechanisms, to communicate securely and reliably with the Inngest SDK.
Learn more on Inngest's Durable Execution Engine in our "How Inngest Functions are executed" guide.