# Hatchet vs Zeplo

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

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

## At a glance

| Criterion | Hatchet | Zeplo |
| --- | --- | --- |
| Free tier | Yes | Yes |
| Entry paid plan | $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month. | $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each. |
| Pricing model | Usage-first: every plan is "free + usage" or "$N/mo + usage" at $10 per million task runs, with the plan fee buying users, tenants, retention and throughput rather than volume. Self-hosting is offered with support on the enterprise tier. | 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 | 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2. | Hosted on Google Cloud Platform; no selectable region is offered and data may be transferred between countries. |
| Included per month | 100,000 task runs included free, then $10 per million. The cleanest per-unit rate in this category — Hatchet counts task runs where Cloudflare counts 64 KB operations and Inngest counts steps. | 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. |
| Message retention | 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. | 30 days of log retention on every plan — free, Company and Enterprise alike. The longest window in this category by a wide margin. |
| Concurrency | 500 requests per second of throughput on Team; higher tiers are not published as a number. | 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

- Hatchet: $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month. ([source](https://hatchet.run/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

- Hatchet: Usage-first: every plan is "free + usage" or "$N/mo + usage" at $10 per million task runs, with the plan fee buying users, tenants, retention and throughput rather than volume. Self-hosting is offered with support on the enterprise tier. ([source](https://hatchet.run/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

- Hatchet: 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2. ([source](https://docs.hatchet.run/v1/region-availability))
- 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

- Hatchet: 100,000 task runs included free, then $10 per million. The cleanest per-unit rate in this category — Hatchet counts task runs where Cloudflare counts 64 KB operations and Inngest counts steps. ([source](https://hatchet.run/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))

### Message retention

- Hatchet: 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. ([source](https://hatchet.run/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))

### Concurrency

- Hatchet: 500 requests per second of throughput on Team; higher tiers are not published as a number. ([source](https://hatchet.run/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 Hatchet if Task workloads that want a countable unit — 100,000 runs free and $10 per million is the least ambiguous pricing in this category.

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: Hatchet — The jump from free to the first paid tier is $500 a month, which buys retention and throughput rather than volume, so a small production workload pays a lot for features it may not need.

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

- Maximum message size: Zeplo: 256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company.
- Maximum delay: Zeplo: 30 days (2,592,000 seconds) maximum delay_seconds per request.
- SOC 2: Hatchet: SOC 2 Type II compliant; reports available through the Hatchet Trust Center.
- HIPAA: Hatchet: HIPAA compliant per the security docs; the Scale plan ($1,000/mo) lists audit logs and HIPAA.
- GDPR / data residency: Hatchet: GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland).
- Encryption at rest: Hatchet: Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit.
- Role-based access control: Hatchet: Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member.
- Dedicated infrastructure: Hatchet: Bring-your-own-cloud and self-host support on the Enterprise plan (contact sales).

## Questions this comparison answers

**Entry paid plan: Hatchet or Zeplo?**

Hatchet: $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month.
Zeplo: $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each.

**Should I choose Hatchet or Zeplo?**

Pick Hatchet if Task workloads that want a countable unit — 100,000 runs free and $10 per million is the least ambiguous pricing in this category.
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.