Inngest vs Zeplo
SEPT 2026 auditA comparison of Inngest and Zeplo built from values read directly from each provider's own documentation, with the source recorded against every figure.
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.
8 sourced criteria separate them — see where, with sources, below.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Inngest 0
Zeplo 0
At a glance.
| Criterion | Inngest | Zeplo |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| 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 model | 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. | 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 | ||
| Regions | All 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 month | 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. | 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 retention | 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. | 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. |
| Concurrency | 5 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). |
Where they differ.
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) →Sources ↓
- Pricing — Inngest ↗
“Pro [...] Starting at $99/mo [...] 1M executions included Pay as you go up to 20M”
Read 2026-09-06 · official pricing
- Pricing — Zeplo ↗
“Company [...] $39 /month 1M requests included $10 / million requests Team size: 3 users [...] Addition team members $15 $15 $15”
Read 2026-09-06 · official pricing
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) →Sources ↓
- 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
- 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
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) →Sources ↓
- 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
- 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
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) →Sources ↓
- 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
- Pricing — Zeplo ↗
“Free 500 requests included $20 / 100k requests [...] $39 /month 1M requests included $10 / million requests”
Read 2026-09-06 · official pricing
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.
Sources (2) →Sources ↓
- Inngest usage limits - Inngest Documentation ↗
“Step-returned payload size 4MiB Applies to data returned by a step. Function run state size 32MiB Includes event data, step data, function return data, and internal metadata.”
Read 2026-09-13 · official docs
- Limits - Zeplo docs ↗
“Maximum request body size 256KB inline, unlimited via S3 offload [...] Max payload 64KB 1MB”
Read 2026-09-13 · official docs
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) →Sources ↓
- Pricing — Inngest ↗
“100k queue depth [...] 1M+ queue depth [...] Granular tracing, metrics, alerts + 7 day trace retention [...] Advanced tracing, metrics, alerts + 90 day trace retention”
Read 2026-09-06 · official pricing
- Pricing — Zeplo ↗
“Log retention 30 days 30 days 30 days”
Read 2026-09-06 · official pricing
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.
Sources (2) →Sources ↓
- Inngest usage limits - Inngest Documentation ↗
“Step sleep duration Up to 1 year Free plan supports sleeps up to 7 days.”
Read 2026-09-13 · official docs
- Limits - Zeplo docs ↗
“Maximum delay_seconds 2,592,000 (30 days)”
Read 2026-09-13 · official docs
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) →Sources ↓
- Pricing — Inngest ↗
“5 concurrent steps [...] 100+ concurrent steps [...] Custom concurrent steps”
Read 2026-09-06 · official pricing
- Limits - Zeplo docs ↗
“Plan API rate limit Developer (Free) 100 requests/min Company ($39/mo) 2,000 requests/min”
Read 2026-09-13 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
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.
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.