# Inngest vs Zeplo

Canonical: https://inetgeek.com/compare/inngest-vs-zeplo/

Every value below is read from Inngest's and Zeplo's own documentation. See https://inetgeek.com/methodology/ for how.

## At a glance

| Criterion | Inngest | Zeplo |
| --- | --- | --- |
| 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. |
| 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. |
| 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. ([source](https://www.inngest.com/pricing))
- Zeplo: $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each. ([source](https://www.zeplo.io/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. ([source](https://www.inngest.com/pricing))
- 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. ([source](https://www.zeplo.io/pricing))

### Regions

- Inngest: All customer data hosted on AWS databases located in the United States; no other region offered on the security page. ([source](https://www.inngest.com/security))
- Zeplo: Hosted on Google Cloud Platform; no selectable region is offered and data may be transferred between countries. ([source](https://zeplo.io/privacy/))

### 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. ([source](https://www.inngest.com/pricing))
- 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. ([source](https://www.zeplo.io/pricing))

### Maximum message size

- Inngest: 4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch. ([source](https://www.inngest.com/docs/usage-limits/inngest))
- Zeplo: 256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company. ([source](https://zeplo.io/docs/limits/))

### 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. ([source](https://www.inngest.com/pricing))
- Zeplo: 30 days of log retention on every plan — free, Company and Enterprise alike. The longest window in this category by a wide margin. ([source](https://www.zeplo.io/pricing))

### Maximum delay

- Inngest: Step sleeps up to 1 year on paid plans; the free plan supports sleeps up to 7 days. ([source](https://www.inngest.com/docs/usage-limits/inngest))
- Zeplo: 30 days (2,592,000 seconds) maximum delay_seconds per request. ([source](https://zeplo.io/docs/limits/))

### Concurrency

- Inngest: 5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise. ([source](https://www.inngest.com/pricing))
- Zeplo: API rate limit rather than a concurrency figure: 100 requests/min on Developer (Free) and 2,000 requests/min on Company ($39/mo). ([source](https://zeplo.io/docs/limits/))

## Which should you choose?

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.

Consider something else: 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.

Consider something else: 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.

## Documented by only one

- SOC 2: Inngest: SOC 2 Type II compliant; report available on request via the trust center.
- HIPAA: Inngest: HIPAA BAAs offered as an add-on for healthcare compliance (Enterprise column of the pricing table).
- 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.
- Customer-managed keys: Inngest: Bring-your-own-key via SDK encryption middleware that encrypts payloads client-side before they reach Inngest; not a server-side KMS option.
- Role-based access control: Inngest: SAML, RBAC and audit trails listed as Enterprise plan features.

## 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.