Inngest VPS hosting.

You pay a fixed monthly price for the VPS, not per run, step or event. The VPS plans scale by RAM, CPU and storage, and the current prices are shown live in the pricing section above. Inngest's self-hosted server is open source, and ZAP-Hosting bills only the VPS.

• Fixed monthly VPS price instead of usage-based billing
• Live plan prices in the pricing section
• Cancel anytime

Order a VPS, open One-Click Apps in the dashboard and deploy Inngest from the Coolify marketplace in one click. Coolify pulls the container and starts the server. If you prefer your own setup, root access lets you run the official Docker image or a Docker Compose stack by hand. One-Click Apps guide in the Help Center

• One-click deploy via the Coolify marketplace
• Manual Docker or Docker Compose setup with root access

It depends on your workload, not on a fixed minimum. Small projects with a handful of functions run fine on an entry plan. Plan for more RAM and CPU when you queue many steps at once, raise concurrency limits or run Postgres and Redis on the same VPS. Root access lets you watch real usage and move up a plan when the numbers call for it.

• Load drivers: queued steps, concurrency, Postgres and Redis
• Compare all plans in the pricing section

Inngest is open source and built to be self-hosted, so it runs on any server you control. A ZAP-Hosting VPS gives it an always-on home with full root access and DDoS protection. Choose from locations in Europe and America and pick the one closest to your app and its users. Many teams in North America start with Ashburn, Dallas or Los Angeles.

• Open-source, self-hostable Inngest server
• Locations in Europe and America: choose the one nearest your app

Point the SDK at your server instead of Inngest Cloud: set INNGEST_BASE_URL to your server's URL and use the same INNGEST_SIGNING_KEY and INNGEST_EVENT_KEY you configured on the server. Then register your app's serve endpoint so Inngest can sync your functions. The official Inngest self-hosting docs list the exact options for each SDK.

• INNGEST_BASE_URL points to your server
• Matching signing key and event key

Treat the dashboard as an admin tool. Serve it through your own domain with HTTPS and access control in front, restrict the Inngest ports with firewall rules so only your apps and trusted IPs can reach them, and keep the signing key and event keys secret. With root access you can set all of this up the way your team needs. Firewall guide in the Help Center

• Domain and HTTPS with access control
• Firewall rules for the Inngest ports
• Signing and event keys kept secret

To update Inngest, redeploy the newer image in Coolify, then check logs and memory usage over SSH to confirm the new version runs cleanly. For persistent run history, use Postgres instead of the default SQLite file. You create and restore VPS Backups in the ZapX panel; manual Backups and restores require ZapX Pass. Backup guide in the Help Center

• Updates via redeploy in Coolify
• Postgres for durable run history
• Manual Backups and restore with ZapX Pass

Yes. As your workflows grow, you can switch to a larger plan with more RAM, CPU and storage. Disk space can't be reduced again later. You can also cancel anytime, and the cancellation takes effect at the end of your current term.

• Upgrade to more RAM and CPU as you grow
• Cancel anytime