Leneex - Hosting Provider
Inngest

Deploy Inngest on a VPS in One Click

Automation & workflowsDevOps, CI/CD & containers

Event-driven backend for durable background jobs, scheduled tasks and multi-step AI workflows built for developers.

Deploy on a VPSAll apps
  • Ready in ~5 min
  • Free installation
  • We handle the setup
At a glance
Version
Latest (1.x)
Operating system
Ubuntu Server 24.04 LTS
Minimum RAM
4 GB
License
SSPL-1.0
Addressing
IPv4, IPv6
GitHub
6,000
Deployment~5 min
VPS plans

Choose a VPS plan for Inngest

Blazing-fast NVMe drives and powerful processors. Take a ready-made plan or build the configuration yourself.
Minex
Perfect for personal projects and small websites.
€3.20/mo
Save €0.80 per month
  • 1 vCPU core
  • 1 GB DDR5 RAM
  • 20 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 1 TB traffic
Basex
A great balance of power and affordable price.
€4.80/mo
Save €1.20 per month
  • 2 vCPU cores
  • 2 GB DDR5 RAM
  • 40 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 2 TB traffic
Most popular
Corex
For growing applications and businesses.
€7.20/mo
Save €1.80 per month
  • 4 vCPU cores
  • 4 GB DDR5 RAM
  • 50 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Midex
Resources for high-load projects.
€9.60/mo
Save €2.40 per month
  • 4 vCPU cores
  • 6 GB DDR5 RAM
  • 60 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Proex
Maximum power and scalability.
€12.00/mo
Save €3.00 per month
  • 6 vCPU cores
  • 8 GB DDR5 RAM
  • 70 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Scalex
Resources for scaling.
€16.00/mo
Save €4.00 per month
  • 6 vCPU cores
  • 10 GB DDR5 RAM
  • 150 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Maxex
A large reserve of power.
€44.00/mo
Save €11.00 per month
  • 8 vCPU cores
  • 16 GB DDR5 RAM
  • 200 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Apex
The top configuration.
€79.99/mo
Save €20.00 per month
  • 16 vCPU cores
  • 32 GB DDR5 RAM
  • 400 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic

What you can do with Inngest

Inngest is an event-driven durable execution platform that lets developers write background jobs, scheduled tasks and multi-step AI pipelines as ordinary code, without provisioning a message queue or worker fleet by hand. Each function reacts to events sent through an event API, and every step inside it retries independently if something fails. Teams building onboarding flows, billing reconciliation or LLM agent pipelines reach for it instead of wiring a broker together themselves.

What sets it apart from a plain task queue is step-level state: a function can pause for hours between steps and resume exactly where it left off, even after a crash. Choosing Inngest self hosted over the managed cloud keeps every event payload and execution trace on hardware you control, which matters once workflows touch customer data or call internal APIs that shouldn't leave your network. Running it as Inngest vps hosting also removes the per-execution billing that scales with production traffic.

Get started
The applications screen of the control panel with one-click install

Inngest features

A server surrounded by app icons — applications running on a VPS

A self-hosted Inngest installation ships with the same core engine used in the cloud product: an event API, a durable step orchestrator and a real-time dashboard. Below is what you get once the Inngest vps docker container is up and connected to your application's SDK endpoint.

01

Event API

Accepts arbitrary JSON events over HTTP that trigger one or many matching functions at once.

02

Step functions

Each function is broken into steps that retry and resume independently instead of restarting the whole run.

03

Scheduled & cron functions

Trigger workflows on a cron expression without wiring up an external scheduler.

04

Automatic retries with backoff

A failed step retries on a configurable schedule before the function is marked failed.

05

Fan-out & concurrency controls

One event can trigger multiple functions in parallel, with per-function limits to protect downstream APIs.

06

Real-time dashboard

Inspect event history, run status, step timing and error traces from a web UI.

07

Batching

Group multiple events into a single function run for high-volume workloads.

08

SDKs for TypeScript, Python and Go

Define functions inside your existing codebase and expose them at one HTTP endpoint.

Requirements

Which server to run it on

Minimum requirements for Inngest and the configuration worth starting with.
Minimum
  • CPU2 vCPU
  • Minimum RAM4 GB
  • Disk20 GB
Recommended
VPS Corex
  • CPU4 vCPU
  • Minimum RAM4 GB
  • Disk50 GB

Installation is free — you only pay for the server

Getting started

How to deploy Inngest

Three steps and the app is running on your server.
Step 1
Choose a server

Choose a vps for Inngest with enough headroom for the server plus the Postgres and Redis instances it needs once you move past the built-in SQLite dev mode.

Step 2
Pick the app

Select Inngest from the app list to install Inngest on vps automatically, with signing and event keys generated for you during setup.

Step 3
Get your credentials

Grab the generated INNGEST_SIGNING_KEY, INNGEST_EVENT_KEY and the dashboard URL to connect your app's SDK and start sending events.

Official websiteinngest.com
GitHub repositorygithub.com
Documentationinngest.com
Why us

Why Host Inngest on Leneex

Speed, protection and support you can rely on — on every plan, with no hidden limits.
Deployment speed
Durable workflows are easiest to debug when you can spin up a fresh instance in minutes, replay a failing event, and tear the environment down — waiting on infrastructure kills that iteration loop.
Free installation
Inngest Cloud bills per execution once you outgrow the free Hobby tier, so a €0 setup on your own VPS removes that per-run cost entirely, not just a subscription fee.
DDoS protection
The event endpoint is a public HTTP ingress that often receives webhooks from Stripe, GitHub or your own frontend, so it needs to stay reachable under traffic spikes or attack attempts.
Control and support
Durable execution state lives in Postgres and Redis, so root access to tune connection pools or queue depth — plus engineers on call when a backlog builds up — matters more here than on a stateless app.
99.9% uptime with SLA compensation
A function can be asleep for days waiting on step.sleep or an external event, and if the server goes down during that window, time-sensitive steps like payment retries or trial-expiry emails slip.
Flexible payment
Teams that spin up several environments for staging, retry load-testing or region-specific deployments can pay for hosting for Inngest with a card, crypto or an invoice instead of juggling per-project SaaS billing.
What to choose

Inngest: Self-Hosted vs Cloud — Which to Choose

Inngest Cloud is the official SaaS product (Hobby is free, Pro starts at approximately $75–99/month depending on usage, and Enterprise pricing is custom), so the comparison is made against the actual product rather than an abstract alternative.
Inngest Cloud
Self-hosted on LeneexRecommended
Resources and limitsFree Hobby tier caps around 50K executions/month and 5 concurrent steps; Pro raises limits but usage stays meteredDedicated CPU/RAM; execution volume and concurrency limited only by your server
Control and accessNo server access — state and traces live inside Inngest's infrastructureFull root access to the server, plus the Postgres and Redis backing your event/function state
Feature limitsTrace retention capped (around 7 days on free/Pro), lower concurrency and connection limits on lower plansFull engine, all step primitives, no vendor-imposed trace-retention window
ScalingScaling means a plan upgrade, and cost climbs with execution volumeAdd CPU/RAM to the same VPS, or move to a bigger plan anytime
CostUsage-based — roughly $50 per million executions beyond the included allowanceFixed VPS price regardless of how many events you process
Who it fitsTeams that want zero infrastructure and are fine with usage-based billing at moderate volumeTeams with steady or unpredictable event volume who want the bill to stay flat

For workloads with steady or spiky execution volume, running Inngest self hosted keeps the bill flat while Inngest Cloud's free tier runs out fast and Pro pricing scales with every event you fire. Teams that would rather deploy Inngest in one click and skip infrastructure entirely are still better served by the managed cloud — the trade-off is predictable cost against zero maintenance.

Frequently Asked Questions about Inngest on VPS

What people ask most about Inngest and our servers.

  • There's no one-click export — your functions live in your application's codebase and just point at a new server URL, but event history and run traces stored in Inngest Cloud stay there and aren't transferred.

  • Nothing needs reinstalling — Inngest, Postgres and Redis keep running, and the extra CPU/RAM simply raises the ceiling on how many workflow steps can execute concurrently.

  • SSL for the dashboard and event endpoint is provisioned automatically, so webhooks from Stripe, GitHub or your own app hit an HTTPS endpoint from day one.

  • As a rough baseline, a 2 vCPU / 4 GB server comfortably handles tens of thousands of function executions a month at moderate concurrency.

  • Once you deploy through Inngest one click install, keeping the server image and your app's SDK version compatible is on you — in practice that's pulling the latest Docker image and restarting the container.

What's running out of the box

The one-click template starts the official inngest/inngest Docker image with the inngest start command already running behind your domain, giving you the dashboard and event API without a manual Docker Compose setup — a straightforward way to get one click automation Inngest without hand-editing a compose file.

First login

Open the dashboard at the URL shown in your Leneex panel; Inngest doesn't ship a username/password screen by default, so access is controlled by the signing key rather than a login form. Once you have them, the dashboard's Apps tab shows runs and errors as soon as your application starts sending events.

Connecting your application

Inngest itself doesn't run your business logic — it only orchestrates it. Install the SDK for your language (TypeScript, Python or Go), expose your functions at an HTTP route such as /api/inngest, and point that route's URL back at the server so it can register your functions and start delivering events. From there, sending an event is a single API call from your app code, and the server handles retries, scheduling and step state without any extra queue infrastructure to maintain.

Deploy Inngest in about 5 minutes

Choose a server — we do the rest: install, configure and send you the credentials.

Choose a serverAll apps