Inngest Hosting Live In 5 Minutes

Inngest hosting on xCloud gives your application a self-hosted durable function runtime for background jobs and multi-step workflows that retry on failure. Deploy Inngest from the OneClick catalog and xCloud starts the pinned v1.45.1 server with Redis behind a Caddy gateway, generates the dashboard password, signing key and event key, mounts two volumes and publishes it over HTTPS. The dashboard sits behind Basic Authentication, while SDK and event routes use their own keys.

  • No terminal
  • No technical skills needed
  • No lock-in, cancel anytime

What is Inngest?

Inngest's README says its durable functions replace queues, state management and scheduling, so any developer can write reliable step functions without touching infrastructure. A function has triggers such as events, cron schedules or webhooks, flow control such as concurrency, throttling and rate limiting, and steps that turn it into a workflow that can run for months and recover from failures. Self-hosted Inngest is a server you run yourself instead of the hosted Inngest platform. It is licensed under SSPL-1.0 with an Apache 2.0 future licence, which is source-available and not open source.

On xCloud this template deploys Inngest v1.45.1, pinned by digest, with SQLite history on inngest_data and Redis queue state on inngest_redis_data. A Caddy gateway puts Basic Auth in front of the dashboard and API routes that have no upstream login. Workers connect over HTTPS with the signing key, and the Connect gateway is not published.

From Sign-Up to a Live Inngest Server In 3 Easy Steps

A self-hosted workflow engine normally means a runtime, a Redis queue, a gateway for dashboard auth and a domain before your first function syncs. This is the same result without assembling any of it.

  1. Step 01

    Sign Up

    Create your xCloud account, choose Inngest from the OneClick catalog and select a domain. There are no other fields to fill in.

  2. Step 02

    We Deploy It For You

    One click. We bring up Inngest v1.45.1 with its Redis and Caddy sidecars, all pinned by immutable digest, mount the persistent volumes, generate the credentials and publish the Inngest URL over HTTPS.

  3. Step 03

    Save Your Keys And Sync

    Save the dashboard password, signing key and event key from your protected credentials. Sign in as admin, then point your SDK at your domain with the signing key and sync your app from the dashboard.

Everything Inngest Needs, On Your Own Server

The durable function runtime runs in full here, with the dashboard, queue and history on infrastructure you control.

  • Durable Functions

    Trigger functions from events or cron schedules, built from steps that retry on failure.

  • Flow Control

    Set concurrency, throttling, debouncing, rate limits and prioritization for your background work.

  • Your Own Workers

    Keep your functions on your infrastructure and sync them to this server over HTTPS.

  • Protected Dashboard

    HTTP Basic auth guards the dashboard, GraphQL, MCP, /invoke and /metrics routes.

  • Signing And Event Keys

    Workers and event senders are checked by Inngest's own signing key and event key.

  • Persistent Queue State

    Event history and Redis queue state live on their own volumes, separate from the app.

Everything You Need To Run Your Workflows 24/7

Managed hosting for Inngest, so the server, gateway and queue that keep it running are not your problem.

  • Inngest v1.45.1 deployed instantly
  • Upstream image pinned by digest
  • Dashboard behind HTTP Basic auth
  • Signing and event keys generated
  • HTTPS on your domain
  • 30+ server locations
  • Unused balance refunded

What You Can Do With Inngest

  • Run reliable background jobs

    Your app sends an event, and Inngest runs the matching function with automatic retries when a step fails.

  • Build multi-step workflows

    A workflow made of steps pauses, waits and resumes, surviving crashes and deploys without you writing queue code.

  • Control concurrency and rate

    You limit how many runs execute per user or throttle calls to a third-party API using the flow control settings.

  • Keep job history on your own server

    A team that does not want its run history in a hosted platform keeps it in SQLite and Redis volumes it controls.

Inngest vs Alternatives

Inngest Cloud
Inngest also offers a hosted platform, which its README links to. This template is a separate self-hosted server you run yourself, with its own keys and no account on the hosted service.
Temporal
Temporal is a separate durable execution platform with its own OneClick page. Inngest runs event-, cron- and webhook-triggered step functions that it invokes over HTTPS on your own app server.
BullMQ
If you are weighing BullMQ, Inngest is a server with a dashboard, event API and step functions that retry on failure, with flow control such as concurrency, throttling and rate limiting set per function.
A cron job and a queue
A hand-built cron and queue need no extra server but leave retries, state and visibility to you. Inngest provides them, at the cost of running a server and its licence terms.

Simple Pricing. Everything Included.

Dedicated Cloud VPS sizes, pre-configured for Inngest. Pick the one that fits, and resize any time.

Cloud VPS 6 GB

Most popular

A team running durable jobs and workflows for one product.

$24.99per month

  • 6 GB RAM
  • 4 vCPU cores
  • 100 GB NVMe SSD
  • 30 TB
  • Unlimited
Get started

Cloud VPS 16 GB

More event volume, longer history and several apps' workflows.

$59.99per month

  • 16 GB RAM
  • 6 vCPU cores
  • 200 GB NVMe SSD
  • 30 TB
  • Unlimited
Get started

Cloud VPS 24 GB

Inngest alongside other self-hosted apps on the same box.

$84.99per month

  • 24 GB RAM
  • 8 vCPU cores
  • 300 GB NVMe SSD
  • 30 TB
  • Unlimited
Get started

Every size is a dedicated Cloud VPS we provision, patch, monitor and restore. Billed monthly with no lock-in. Inngest's own license terms apply to the software, so review SSPL-1.0 for your use.

Already Have a Server? Bring Your Own

Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Inngest on it through the same panel, for a per-server management fee instead of a Cloud VPS rental.

Free

Start your journey without cost.

$0forever

  • 1 server
  • 10 sites
Start free

Starter

Most popular

Your rate with 2–5 servers connected.

$5per server / month

  • 2–5 servers
  • Unlimited sites
  • All features included
  • Bring any VPS provider
Get started

Professional

The same platform, discounted at 6–10 servers.

$4per server / month

  • 6–10 servers
  • Unlimited sites
  • All features included
  • Bring any VPS provider
Get started

Agency

The same platform, discounted at 11+ servers.

$3per server / month

  • 11+ servers
  • Unlimited sites
  • All features included
  • Bring any VPS provider
Get started

Priced per connected server, so your rate adjusts automatically as you add or remove servers. You pay your own provider for the server itself.

Ready To Run Your Own Workflow Engine?

Inngest on xCloud runs on a dedicated Cloud VPS that we provision, patch, monitor and restore. Deploy faster. Own the server. Keep your functions where they belong.

Hear what people are saying about us

See why agencies, developers, startups, and growing businesses choose xCloud to power their projects.

xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising. Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Brian Geovanny
I've been with runcloud for the last 3 years. However, after trying xcloud for the last month, I'm switching over. They are on a roll with their setup.
Kevin Pineda
I'm moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud! #xCloud #wordpress #hosting
Leo Koo
How Cloud Nine Web Elevated Client Experience While Streamlining Hosting Operations using xCloud
Ed Ellingham
xCloud is like having an expert server team on call — without the big agency costs. It's given me back my time and given my clients peace of mind. Highly recommended for freelancers and small teams who want reliable performance and security.
Dumitru Butucel
xCloud isn't just a solution. It's like one of that friend who got your back when you screw things up pretty bad.
Waqar Ahmed
Trust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahul Singh
So far my experience has been smooth like silk. I didn't imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included). For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation. I'm sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Massimo Villa
Came from cloudways then to runcloud then to xcloud. Looks like I'm staying here.
Gerson El
I've recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud. I have to say, I'm really impressed with xCloud so far! The interface is definitely the standout feature for me.
Tony Lewis
I came from Cloudways and won't go back. Highly impressed with xCloud. Glad I gave them a chance.
Jared McDowell
I like xCloud better than RunCloud, but one thing I'll point out is that some years ago RunCloud was hungry for business, the support was outstanding, and the community was active and helped each other. Maybe it was sold, there was a change in management, or they stopped being hungry, but the quality of the RunCloud offering declined and it hasn't been moving forward quickly. My point is that currently the xCloud team has the edge and it is theirs to keep or lose
David McCan
How Kevin Heinrichs Cut Hosting Costs by 84% While Running WooCommerce & Node.js Sites Efficiently
Kevin Heinrichs
I had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
Dan Spinoza
Dear xCloud Team, I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It's a fantastic service, and my experience so far has been very positive. Successful migrated 5 sites on a single server. Xcloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Rahil Maknojia
Came from runcloud. Tried xcloud and never came back.
Karl Fanega
How Advanced Web Strategies Saved Over $2,000 & Recovered 56 Hours per Month Managing 70+ Client Websites
Gary Moody
xCloud gave me what no other hosting platform could: the flexibility of a VPS with the convenience of managed WordPress. As a solo founder running an entire business on one server, that combination is an important unfair advantage.
Jorge de los Reyes Martínez
I use Server Avatar and xCloud and I'll sooner use xCloud than Server Avatar personally.
Jay Pagano
How Newman Web Solutions Ensured Perfect Uptime and Seamless Scaling For 120+ WordPress Sites with xCloud
Lori Newman
I too have moved over to xCloud. It's pretty sweet. One click n8n and uptime Kuma apps
John Aperture
I went from Cloudways to xCloud. No intention on switching in the foreseeable future.
Blaine Moore

Frequently Asked Questions

Feel free to contact us with any questions or concerns you may have.

Is self-hosted Inngest free to use?

The Inngest server at v1.45.1 is licensed under SSPL-1.0 with an Apache 2.0 future licence, linked from this page. SSPL is source-available, not open source, and its section 13 restricts offering the program as a service, so review the terms before running it for others. xCloud bills for the Cloud VPS.

Can you self-host Inngest with Docker?

Yes, and this Inngest Docker hosting template does it for you: the upstream inngest/inngest image, pinned by digest, runs beside private Redis and a Caddy gateway on your own server, with HTTPS in front. It is not an Inngest cloud account, so run history stays on your server.

How much RAM does Inngest need?

Per its manifest, Inngest needs at least 1024 MB of RAM, 1 CPU core and 8 GB of disk, though upstream publishes no formal RAM floor. Queue depth and history growth drive usage. The 6 GB tier sold on this page sits far above that.

How do I sign in to the Inngest dashboard?

Use the username admin and the generated dashboard password from the credentials. Inngest has no dashboard login of its own, so the Caddy gateway puts HTTP Basic Authentication in front of the dashboard, GraphQL, MCP, /invoke and /metrics. Change the password in the environment and redeploy to rotate it.

Which Inngest routes need the dashboard password?

The dashboard, GraphQL, MCP, /invoke, /metrics and debug routes. SDK and event routes, such as /e, /fn and /v1, stay open to Basic Authentication and rely on Inngest's own event key and signing key. Both use the Authorization header, so the open list must not be narrowed.

Can my Inngest workers reach it without the dashboard password?

Yes. Workers configure the signing key and use your site as the Inngest base URL, and they sync over HTTPS, since the Connect gateway is not published. Event producers post to /e with the event key. Neither uses the dashboard password, so keep both keys secret.

Where do I send events to Inngest?

POST them to https://your-domain/e/<event-key>, using the generated event key shown in the event ingest URL in the credentials. The key is applied on every start, so changing it in the environment means updating every producer. Serve your functions over HTTPS and sync the app from the dashboard.

What does xCloud configure automatically for Inngest?

The Inngest server, a private Redis with a generated password, the Caddy gateway, the dashboard password, the signing key and the event key, plus two volumes and HTTPS. It does not sync your functions or verify that your workers connect, so test one function end to end.

How do I back up Inngest?

Back up inngest_data, which holds SQLite history, and inngest_redis_data, which holds queue and run state, together. Restoring only one can leave history and queue state out of sync. Keep REDIS_PASSWORD and the matching Redis URI with the Redis volume, and test a restore.

How do I rotate Inngest keys or upgrade?

Edit the signing key or event key in the Environment editor, redeploy and update every worker. A running install stays on pinned v1.45.1 until you adopt a newer template version, and a newer upstream tag exists. Back up both volumes first and read the release notes.

Is Inngest an alternative to Temporal?

It can be, if you want durable, retryable workflows. Inngest is event-driven: it invokes step functions you serve over HTTPS when triggering events arrive. Temporal has its own OneClick page. This page makes no feature or scale comparison, so read both licences before choosing.

Can I cancel anytime?

Yes. There is no lock-in — cancel any time. Hosting is billed monthly and charged for what you actually use, so when you delete the server the unused balance is refunded to your account, less up to 10% in payment-processing fees.

Ready to Run Your Own Workflow Engine?

Connect your first server in minutes. No plan you have to grow into.