As Mergent transitions its focus, we recommend migrating your background jobs, workflows, and event-driven systems to Inngest, a modern developer platform purpose-built for reliable, scalable background functions and workflows.

When you migrate to Inngest, the execution still happens on your own servers (whether that’s serverless or actual servers). We manage the orchestration, queueing, and function state — meaning migration is fast and easy.

This guide walks you through:

• Why you should switch
• Some key differences to be aware of
• How to switch

Why migrate to Inngest

Inngest is more than a Mergent alternative… it’s a next-generation workflow platform for modern developers, and it works everywhere — whether you’re running on serverless or servers. Using Inngest, you get a powerful suite of tools out of the box, with minimal setup:

• Durable functions and resumable workflows: Define long-running, resumable workflows with simple async/await syntax. No state machines, context juggling, or queues to manage.
• Built in retries, replay, idempotency, and flow control: Automatic retries, step isolation, and state persistence ensure workflows don’t break — even during deploys or failures.
• Local development & debugging tools: Build and test locally with the Inngest Dev Server. Log, trace, and replay events for full observability.
• Scalable by Default: Inngest is built to handle hundreds of millions of runs, without managing new infra.

Key differences

Inngest introduces several new concepts to improve reliability, performance, scale, and the developer experience compared to Mergent. Here are a few things to be aware of: