Skip to content
inetGeek

Inngest vs Zeplo

SEPT 2026 audit

A comparison of Inngest and Zeplo built from values read directly from each provider's own documentation, with the source recorded against every figure.

Reviewed by Palash BagchiUpdated 22 criteria comparedSources last checked

The short answer

Choose Inngest if…

Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.

Editorial · Palash Bagchi · approved

Choose Zeplo if…

Turning an HTTP endpoint into a queued, retried job without running a consumer — and keeping a month of logs while doing it, which nothing else here offers on a free plan.

Editorial · Palash Bagchi · approved

Consider something else if…

  • Inngest: Every step is a billable execution, so a three-step workflow costs three times what the run count implies, and the free plan allows five concurrent steps.
  • Zeplo: The free tier's overage is $20 per 100,000 requests, twenty times the Company plan's rate, so staying free past 500 requests is the most expensive way to use it.

Neither quite fits? Every other option, ranked by iScore: Inngest alternatives · Zeplo alternatives

14 sourced criteria separate them — see where, with sources, below.

Visit Inngest documentationVisit Zeplo documentation

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionInngestZeplo
Pricing
Free tierYesYes
Kind of free offerFree tierFree tier
What the free plan includes50,000 executions and 500,000 events ingested a month with 5 concurrent steps, no credit card required.500 requests a month, described as free forever, for a single developer with 30-day log retention.
Entry paid plan
$99/month for Pro, described as a starting price with usage above the included allowance billed on top.
$39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each.
Pricing modelPer execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count.Per HTTP request rather than per message or per execution, with unlimited jobs on every tier and team size as a separate axis — three members included on Company, $15 for each beyond.
Infrastructure
RegionsAll customer data hosted on AWS databases located in the United States; no other region offered on the security page.Hosted on Google Cloud Platform; no selectable region is offered and data may be transferred between countries.
Queues
Included per month50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three.500 requests free, then $20 per 100,000. The Company plan includes 1,000,000 requests and charges $10 per million beyond — five times cheaper per request than the free plan's overage rate.
Maximum message size
4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch.
256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company.
Message retentionQueue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise.30 days of log retention on every plan — free, Company and Enterprise alike. The longest window in this category by a wide margin.
Maximum delay
Step sleeps up to 1 year on paid plans; the free plan supports sleeps up to 7 days.
30 days (2,592,000 seconds) maximum delay_seconds per request.
Concurrency5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise.API rate limit rather than a concurrency figure: 100 requests/min on Developer (Free) and 2,000 requests/min on Company ($39/mo).
Dead letter queue
Not supported — No dead-letter queue; failed runs stay in the dashboard and are re-run in bulk with Replay.
Limited — Dead-letter handling is a webhook fired on permanently failed requests, not a separate queue you consume.
Compliance
GDPR / data residencyData residency only: Inngest Cloud runs in two eastern-US footprints, AWS us-east-2 (Ohio) and Inngest bare metal in Ashburn, Virginia.Privacy policy permits storage, processing and transfer of personal information between any of the countries in which Zeplo operates. zeplo.io policy, last updated February 7, 2022; the newer v2.zeplo.io policy is silent on transfers.
Encryption at restAll data in Inngest databases is encrypted at rest and in transit; optional encryption middleware lets you bring your own key.Privacy policy states industry-standard measures including encryption in transit (TLS), encryption at rest, and access controls. v2.zeplo.io policy, last updated February 21, 2026; no cipher or key-management detail published.
Role-based access controlSAML, RBAC and audit trails listed as Enterprise plan features.Workspaces support multiple members with role-based access; roles are admin, member and viewer. Team invites are managed in the dashboard under Settings, Team; the API invite endpoint takes the same three roles.
Dedicated infrastructure
Enterprise runs on dedicated function execution infrastructure with isolated queue and constraint shards; Dedicated Infrastructure is an enterprise add-on. The add-on's contents and price are not described on the page.
Not listed on the Developer or Company plans; the pricing page says to contact sales for custom volume, SLAs or dedicated infrastructure. From the "Need more?" block under the Developer (free) and Company ($39/mo) plan cards.

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

Where they differ.

What the free plan includes

Inngest
50,000 executions and 500,000 events ingested a month with 5 concurrent steps, no credit card required.
Zeplo
500 requests a month, described as free forever, for a single developer with 30-day log retention.
Sources (2) →

Entry paid plan

Inngest
$99/month for Pro, described as a starting price with usage above the included allowance billed on top.
Zeplo
$39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each.
Sources (2) →

Pricing model

Inngest
Per execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count.
Zeplo
Per HTTP request rather than per message or per execution, with unlimited jobs on every tier and team size as a separate axis — three members included on Company, $15 for each beyond.
Sources (2) →
  • Pricing — Inngest ↗

    “TOTAL EXECUTIONS PER MONTH (30,000 runs × 2 steps per run) + 30,000 runs = 90,000 executions [...] 500 MB span data ingested [...] 10K scores [...] 500k events ingested [...] 50 realtime connections”

    Read 2026-09-06 · official pricing · Report a correction

  • Pricing — Zeplo ↗

    “Jobs Unlimited Unlimited Unlimited Included team members 1 3 Custom Addition team members $15 $15 $15 Log retention 30 days 30 days 30 days”

    Read 2026-09-06 · official pricing · Report a correction

Regions

Inngest
All customer data hosted on AWS databases located in the United States; no other region offered on the security page.
Zeplo
Hosted on Google Cloud Platform; no selectable region is offered and data may be transferred between countries.
Sources (2) →
  • Security | Inngest ↗

    “All of our data is hosted on Amazon Web Services (AWS) databases. These databases are all located in the United States.”

    Read 2026-09-13 · official site · Report a correction

  • Privacy Policy - Zeplo ↗

    “Zeplo currently uses the following services to store your information: Google Cloud Platform Cross-border data transfers Information that Zeplo collects may be stored and processed in and transferred between any of the countries”

    Read 2026-09-13 · official site · Report a correction

Included per month

Inngest
50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three.
Zeplo
500 requests free, then $20 per 100,000. The Company plan includes 1,000,000 requests and charges $10 per million beyond — five times cheaper per request than the free plan's overage rate.
Sources (2) →
  • Pricing — Inngest ↗

    “50k executions [...] 1M executions included Pay as you go up to 20M [...] (30,000 runs × 2 steps per run) + 30,000 runs = 90,000 executions [...] A single durable function run or step execution”

    Read 2026-09-06 · official pricing · Report a correction

  • Pricing — Zeplo ↗

    “Free 500 requests included $20 / 100k requests [...] $39 /month 1M requests included $10 / million requests”

    Read 2026-09-06 · official pricing · Report a correction

Maximum message size

Inngest

4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch.

Zeplo

256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company.

Sources (2) →

Message retention

Inngest
Queue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise.
Zeplo
30 days of log retention on every plan — free, Company and Enterprise alike. The longest window in this category by a wide margin.
Sources (2) →

Maximum delay

Inngest

Step sleeps up to 1 year on paid plans; the free plan supports sleeps up to 7 days.

Zeplo

30 days (2,592,000 seconds) maximum delay_seconds per request.

Sources (2) →

Concurrency

Inngest
5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise.
Zeplo
API rate limit rather than a concurrency figure: 100 requests/min on Developer (Free) and 2,000 requests/min on Company ($39/mo).
Sources (2) →

Dead letter queue

Inngest
Not supported — No dead-letter queue; failed runs stay in the dashboard and are re-run in bulk with Replay.
Zeplo
Limited — Dead-letter handling is a webhook fired on permanently failed requests, not a separate queue you consume.
Sources (2) →

GDPR / data residency

Inngest
Data residency only: Inngest Cloud runs in two eastern-US footprints, AWS us-east-2 (Ohio) and Inngest bare metal in Ashburn, Virginia.
Zeplo
Privacy policy permits storage, processing and transfer of personal information between any of the countries in which Zeplo operates. zeplo.io policy, last updated February 7, 2022; the newer v2.zeplo.io policy is silent on transfers.
Sources (2) →
  • Inngest Cloud Architecture | Scheduling & Execution - Inngest Docs ↗

    “Inngest Cloud runs across two nearby infrastructure footprints in the eastern United States: [...] AWS us-east-2 (Ohio) hosts customer-facing APIs, control plane services, and supporting data services. [...] Inngest-operated bare metal in Ashburn, Virginia hosts the primary run scheduling and function execution data plane”

    Read 2026-09-13 · official docs · Report a correction

  • Zeplo Privacy ↗

    “Information that Zeplo collects may be stored and processed in and transferred between any of the countries in which Zeplo operates to enable the use of the information in accordance with this privacy policy. [...] You agree to such cross-border transfers of personal information.”

    Read 2026-09-13 · official site · Report a correction

Encryption at rest

Inngest
All data in Inngest databases is encrypted at rest and in transit; optional encryption middleware lets you bring your own key.
Zeplo
Privacy policy states industry-standard measures including encryption in transit (TLS), encryption at rest, and access controls. v2.zeplo.io policy, last updated February 21, 2026; no cipher or key-management detail published.
Sources (2) →

Role-based access control

Inngest
SAML, RBAC and audit trails listed as Enterprise plan features.
Zeplo
Workspaces support multiple members with role-based access; roles are admin, member and viewer. Team invites are managed in the dashboard under Settings, Team; the API invite endpoint takes the same three roles.
Sources (2) →

Dedicated infrastructure

Inngest
Enterprise runs on dedicated function execution infrastructure with isolated queue and constraint shards; Dedicated Infrastructure is an enterprise add-on. The add-on's contents and price are not described on the page.
Zeplo
Not listed on the Developer or Company plans; the pricing page says to contact sales for custom volume, SLAs or dedicated infrastructure. From the "Need more?" block under the Developer (free) and Company ($39/mo) plan cards.
Sources (2) →

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

03.

Documented by only one.

These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing — except where we say we read the other provider's own page on a given date and it does not state it. Those rows lean, and the provider can correct them with a link.

Credit card to startInngest: No
When the free offer endsZeplo: Never — 500 requests a month, free forever.
SOC 2Inngest: SOC 2 Type II compliant; report available on request via the trust center.
ISO 27001Inngest: Not held as of the June 2024 SOC 2 announcement, which says Inngest is exploring additional certifications, such as ISO 27001. Stated on the SOC 2 Type II announcement, dated Jun 20, 2024.
HIPAAInngest: HIPAA BAAs offered as an add-on for healthcare compliance (Enterprise column of the pricing table).
Customer-managed keysInngest: Bring-your-own-key via SDK encryption middleware that encrypts payloads client-side before they reach Inngest; not a server-side KMS option.
04.

Questions this comparison answers.

Entry paid plan: Inngest or Zeplo?

Inngest: $99/month for Pro, described as a starting price with usage above the included allowance billed on top.

Zeplo: $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each.

Should I choose Inngest or Zeplo?

Pick Inngest if Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.

Pick Zeplo if Turning an HTTP endpoint into a queued, retried job without running a consumer — and keeping a month of logs while doing it, which nothing else here offers on a free plan.

Provider pages

InngestDurable execution platform where the billable unit is a function or step execution rather than a queued message.ZeploHTTP request queue priced per request, with 30-day log retention on every plan including free.

Related comparisons

Amazon SQS vs InngestAmazon SQS vs ZeploCloudflare Queues vs InngestHatchet vs InngestHatchet vs ZeploInngest vs Trigger.devUpstash QStash vs InngestTemporal vs Inngest

Comments

Every page here is sourced and dated.