Softwr

APIs · head to head

Convoy vs Inngest

Convoy logo

Convoy

APIs

Open source webhooks gateway you self-host, handling both sending and receiving

From
Free
Rated
-
Full reviewWebsite
Inngest logo

Inngest

Automation Integration

Unbreakable Agents. Invisible Infra.

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Convoy the default deployment is self-hosted, so you operate Convoy plus Postgres and Redis and carry the on-call burden for the system that delivers your customers' events.; Inngest hobby plans pause execution once free quota exhausted; upgrade required to continue
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Convoy and Inngest actually diverge.

Attributes where Convoy and Inngest differ
AttributeConvoyInngest
Pricing modelPer month, flat rate regardless of volumefreemium
PlatformsLinux, Docker, Kubernetes, CloudWeb
CategoryAPIsAutomation Integration

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Convoy

  • Inbound and outbound
  • Broker-driven ingestion
  • Payload transformation
  • Portal links
  • Circuit breaking
  • Retry policies
  • OpenTelemetry export
  • Role-based access control

Only in Inngest

Nothing recorded that Convoy does not also cover.

What people use each for

The jobs each tool is most often brought in to do.

Convoy

  • A fintech that cannot route customer webhook traffic through a third-party SaaS for compliance reasonsnot Inngest
  • A high-volume platform for which per-message webhook pricing costs more than the flat premium licencenot Inngest
  • A team that also receives webhooks from many providers and wants ingestion, verification and deduplication in the same gatewaynot Inngest
  • An engineering group that wants webhook delivery driven directly from an existing Kafka or SQS topicnot Inngest

Inngest

  • Handling unpredictable LLM behavior with fine-grained error controlnot Convoy
  • Retrying failed workflow steps independently without restartingnot Convoy
  • Rate limiting per-tenant usage on shared infrastructurenot Convoy
  • Processing thousands of webhooks per event with replay capabilitynot Convoy
  • Persisting state across serverless function invocationsnot Convoy

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Convoy

  • The default deployment is self-hosted, so you operate Convoy plus Postgres and Redis and carry the on-call burden for the system that delivers your customers' events.
  • Frain Technologies is a small startup, and putting customer-facing delivery infrastructure on it means accepting real vendor continuity risk on a component that is hard to swap out quickly.
  • The premium tier at a flat 999 US dollars a month is poor value below substantial volume, while the community edition omits the portal, transformations and RBAC that most production deployments end up wanting.
  • The hosted cloud trial is capped at one project and 100 events a day, which is too small to properly evaluate the service before committing.
  • Documentation and the third-party ecosystem are thinner than the established webhook services, so unusual configurations often mean reading the Go source.

Inngest

  • Hobby plans pause execution once free quota exhausted; upgrade required to continue
  • Pro plan overages carry tiered metering: additional concurrent steps at $25 per 25, span data at $3/GB, scores at $1.50 per 1K, events at $0.50 per 1M

Pricing, plan by plan

Convoy

Free
  • CommunityFree
    • Self-hosted open source gateway
    • Inbound and outbound webhooks
    • Automatic retries and message broker support
  • Premium$999/month
    • Flat rate irrespective of message volume
    • Portal links and payload transformation
    • RBAC, circuit breaking and white labelling
  • Enterprise$undefined/year
    • SAML SSO
    • Dedicated support with SLA
    • On-premises deployment assistance
  • Cloud$undefined/month
    • Hosted by Convoy
    • 14 day trial limited to one project and 100 events a day
    • Usage-based tiers above the trial

Inngest

Free
  • HobbyFree
    • 50k executions/month
    • 5 concurrent steps
    • 500 MB span data
  • Pro$99/month starting
    • 1M executions included, pay-as-you-go up to 20M
    • 100+ concurrent steps
    • 5 GB span data ingested
  • Enterprise$null/custom
    • customizable metrics
    • 90-day trace retention
    • SAML, RBAC, audit trails

Which should you pick?

Choose Convoy if

  • You need inbound and outbound.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Cloud.
  • You also want broker-driven ingestion.
Convoy review

Choose Inngest if

  • You want to start without paying.
Inngest review

Questions people ask

Is Convoy or Inngest better?
Neither clearly leads. Convoy starts at Free and Inngest at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Convoy or Inngest?
Convoy starts at Free and Inngest at Free.
Does Convoy or Inngest run on more platforms?
Convoy runs on Linux, Docker, Kubernetes, Cloud. Inngest runs on Web.
Can I use Convoy for free?
Both have a free tier, so you can try either at no cost before committing.
What is Convoy best used for?
Convoy is most often used for a fintech that cannot route customer webhook traffic through a third-party saas for compliance reasons, a high-volume platform for which per-message webhook pricing costs more than the flat premium licence, a team that also receives webhooks from many providers and wants ingestion, verification and deduplication in the same gateway, an engineering group that wants webhook delivery driven directly from an existing kafka or sqs topic. Of those, a fintech that cannot route customer webhook traffic through a third-party saas for compliance reasons and a high-volume platform for which per-message webhook pricing costs more than the flat premium licence are not what Inngest is typically brought in for.
What can Convoy do that Inngest cannot?
Convoy covers Inbound and outbound, Broker-driven ingestion, Payload transformation, Portal links.

Answered from the vendors’ own pages

Convoy: Is Convoy really open source?

Yes, the community edition is open source and self-hostable, covering both inbound and outbound webhooks with retries.

Inngest: How much does Inngest cost?

Inngest offers a free Hobby plan with 50k executions per month and up to 3 users. Pro plans start at $99 per month with 1M executions included and support for up to 15 users. Additional Pro users cost $10 each. Enterprise plans require custom pricing.

Source
Convoy: What does premium cost?

A flat 999 US dollars a month, self-hosted, regardless of message volume.

Inngest: Is there a free version of Inngest?

Yes, the Hobby plan is completely free and includes 50k executions per month, 5 concurrent steps, 500 MB span data ingested, 10K scores, 500k events ingested, and support for up to 3 users. Plan changes pause execution once the free quota is exhausted.

Source
Convoy: Does it receive webhooks as well as send them?

Yes, inbound ingestion with verification and deduplication is a first-class feature, unlike most webhook services.

Inngest: What are the overage costs on Inngest Pro?

Inngest Pro includes 1M executions with additional executions at $0.50 per 1M up to 20M. Span data overages cost $3 per GB, scores at $1.50 per 1K, and events at $0.50 per 1M. Additional concurrent steps cost $25 per 25 steps beyond the included 100+.

Source
Convoy: Do I have to self-host?

No, there is a hosted cloud, but the trial is capped at 100 events a day and self-hosting is the primary model.

Share

Related pages

More on Convoy

More on Inngest

Keep looking

Other head to heads