Hatchet vs Zeplo
SEPT 2026 auditA comparison of Hatchet and Zeplo built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Hatchet if…
Task workloads that want a countable unit and no plan fee: 1M task runs and 1M events free each month with a card on file, then $30 per million runs, with 10,000 concurrent worker slots before any contract.
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…
- Hatchet: You want a published uptime percentage or long run history: SLAs come only on the quoted Custom plan, and history is kept 7 days with a card on file (1 day without) unless you move to Custom.
- 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: Hatchet alternatives · Zeplo alternatives
13 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.
Hatchet 0
Zeplo 0
At a glance.
| Criterion | Hatchet | Zeplo |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Kind of free offer | Free tier | Free tier |
| What the free plan includes | Two levels on the free Pay-as-you-go plan. No card: 2,000 task runs and 2,000 events a day. Card on file: 1M task runs and 1M events a month included, then $30 and $5 per million. | 500 requests a month, described as free forever, for a single developer with 30-day log retention. |
| Entry paid plan | No plan fee: Pay-as-you-go is $0 a month and bills only usage past the free million runs and events ($30 per million runs). Custom, for 100M+ runs a month or enterprise features, is priced by conversation. | $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each. |
| Pricing model | Usage-based with no plan fees: 1M task runs and 1M events free every month, then $30 per million runs and $5 per million events, with volume pricing at 100M+ runs a month on Custom. Users past 50 are $10 each. | 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 | 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. |
| Queues | ||
| Included per month | 1M task runs and 1M events a month on Pay-as-you-go with a card on file, then $30 per million runs and $5 per million events. Without a card: 2,000 task runs and 2,000 events a day. | 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 MB default maximum payload size for a task's input or output between worker and Hatchet engine. | 256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company. |
| Message retention | Run history, logs and traces stay queryable for 1 day on Pay-as-you-go without a card, 7 days with a card on file, and 90+ days on Custom. This is dashboard and API history, not how long an undelivered task waits in the queue, so no magnitude is recorded. | 30 days of log retention on every plan — free, Company and Enterprise alike. The longest window in this category by a wide margin. |
| Concurrency | 2,000 worker slots (tasks running at once, totalled across all workers) on Pay-as-you-go without a card, 10,000 with a card on file; Custom gets dedicated capacity. No requests-per-second ceiling is published. | 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 built-in DLQ; failed task instances persist in the dashboard for manual analysis and retry. | Limited — Dead-letter handling is a webhook fired on permanently failed requests, not a separate queue you consume. |
| Compliance | ||
| GDPR / data residency | GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland). | 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 rest | Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit. | 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 control | Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member. | 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 | Dedicated capacity, multi-region, and self-hosted or bring-your-own-cloud (BYOC) deployment on the Custom plan (talk to an engineer). | 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. |
Where they differ.
What the free plan includes
- Hatchet
- Two levels on the free Pay-as-you-go plan. No card: 2,000 task runs and 2,000 events a day. Card on file: 1M task runs and 1M events a month included, then $30 and $5 per million.
- Zeplo
- 500 requests a month, described as free forever, for a single developer with 30-day log retention.
Sources (2) →Sources ↓
- Hatchet Pricing ↗
“Pay-as-you-go No card Pay-as-you-go Card on file Custom [...] 2,000/day 1M/mo included then $30/M [...] 2,000/day 1M/mo included then $5/M”
Read 2026-09-27 · official pricing · Report a correction
- Zeplo Pricing ↗
“You can try our developer plan, which includes 500 free requests every month for free forever.”
Read 2026-09-13 · official pricing · Report a correction
Entry paid plan
- Hatchet
- No plan fee: Pay-as-you-go is $0 a month and bills only usage past the free million runs and events ($30 per million runs). Custom, for 100M+ runs a month or enterprise features, is priced by conversation.
- Zeplo
- $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each.
Sources (2) →Sources ↓
- Hatchet Pricing ↗
“Pay-as-you-go $0 to start [...] No surprise bills. No plan fees. You pay $30 per million runs, only after your free million, with volume pricing at 100M+ runs a month.”
Read 2026-09-27 · official pricing · Report a correction
- 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 · Report a correction
Pricing model
- Hatchet
- Usage-based with no plan fees: 1M task runs and 1M events free every month, then $30 per million runs and $5 per million events, with volume pricing at 100M+ runs a month on Custom. Users past 50 are $10 each.
- 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 ↓
- Hatchet Pricing ↗
“1M runs and 1M events free, every month Then $30 per million runs, $5 per million events [...] No surprise bills. No plan fees. You pay $30 per million runs, only after your free million, with volume pricing at 100M+ runs a month. [...] Users 50 included, then $10/user”
Read 2026-09-27 · 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
- Hatchet
- 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2.
- Zeplo
- Hosted on Google Cloud Platform; no selectable region is offered and data may be transferred between countries.
Sources (2) →Sources ↓
- Region Availability - Hatchet Documentation ↗
“aws-us-west-2 Oregon (US) Live aws-us-east-1 N. Virginia (US) Live aws-eu-west-1 Ireland Live aws-ap-southeast-2 Sydney Private Beta”
Read 2026-09-13 · official docs · 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
- Hatchet
- 1M task runs and 1M events a month on Pay-as-you-go with a card on file, then $30 per million runs and $5 per million events. Without a card: 2,000 task runs and 2,000 events a day.
- 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 ↓
- Hatchet Pricing ↗
“1M runs and 1M events free, every month Then $30 per million runs, $5 per million events [...] 2,000/day 1M/mo included then $30/M [...] 2,000/day 1M/mo included then $5/M”
Read 2026-09-27 · 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
4 MB default maximum payload size for a task's input or output between worker and Hatchet engine.
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 ↓
- Troubleshooting Workers - Hatchet Documentation ↗
“The payload is too large for the worker to accept or the Hatchet engine to send. The default maximum payload size is 4MB.”
Read 2026-09-13 · official docs · Report a correction
- Limits - Zeplo docs ↗
“Maximum request body size 256KB inline, unlimited via S3 offload [...] Max payload 64KB 1MB”
Read 2026-09-13 · official docs · Report a correction
Message retention
- Hatchet
- Run history, logs and traces stay queryable for 1 day on Pay-as-you-go without a card, 7 days with a card on file, and 90+ days on Custom. This is dashboard and API history, not how long an undelivered task waits in the queue, so no magnitude is recorded.
- 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 ↓
- Hatchet Pricing ↗
“Retention How long run history, logs, and traces stay queryable in the dashboard and API. 1 day 7 days 90+ days”
Read 2026-09-27 · official pricing · Report a correction
- Pricing — Zeplo ↗
“Log retention 30 days 30 days 30 days”
Read 2026-09-06 · official pricing · Report a correction
Concurrency
- Hatchet
- 2,000 worker slots (tasks running at once, totalled across all workers) on Pay-as-you-go without a card, 10,000 with a card on file; Custom gets dedicated capacity. No requests-per-second ceiling is published.
- 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 ↓
- Hatchet Pricing ↗
“Worker slots Each slot runs one task at a time. A worker with 100 slots can run 100 tasks concurrently. The limit is the total across all workers. 2,000 10,000 Dedicated capacity”
Read 2026-09-27 · official pricing · Report a correction
- 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 · Report a correction
Dead letter queue
- Hatchet
- Not supported — No built-in DLQ; failed task instances persist in the dashboard for manual analysis and retry.
- Zeplo
- Limited — Dead-letter handling is a webhook fired on permanently failed requests, not a separate queue you consume.
Sources (2) →Sources ↓
- Bulk Retries & Cancellations - Hatchet Documentation ↗
“While Hatchet does not have a built-in dead letter queue feature, the persistence of failed task instances in the dashboard serves a similar purpose.”
Read 2026-09-13 · official docs · Report a correction
- Building Webhooks for Reliable Event Delivery - Zeplo Blog ↗
“Customers want to listen for failed events (e.g. dead letter queue) so they can handle/alert in the case that the message will never be delivered again [...] User can easily setup dead letter webhook”
Read 2026-09-13 · official site · Report a correction
GDPR / data residency
- Hatchet
- GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland).
- 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) →Sources ↓
- Security - Hatchet Documentation ↗
“Hatchet is SOC 2 Type II, HIPAA, and GDPR compliant.”
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
- Hatchet
- Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit.
- 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) →Sources ↓
- Security - Hatchet Documentation ↗
“Encryption at rest : data stored in Hatchet Cloud is encrypted at rest.”
Read 2026-09-13 · official docs · Report a correction
- Zeplo Privacy Policy (app) ↗
“We implement industry-standard security measures including encryption in transit (TLS), encryption at rest, and access controls.”
Read 2026-09-13 · official site · Report a correction
Role-based access control
- Hatchet
- Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member.
- 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) →Sources ↓
- User Roles - Hatchet Documentation ↗
“Every user in a tenant has a role that controls what they can do in the dashboard and REST API. Roles are hierarchical: each role can do everything the roles below it can.”
Read 2026-09-13 · official docs · Report a correction
- Zeplo Docs - FAQ ↗
“Yes. Workspaces support multiple members with role-based access (admin, member, viewer).”
Read 2026-09-13 · official docs · Report a correction
Dedicated infrastructure
- Hatchet
- Dedicated capacity, multi-region, and self-hosted or bring-your-own-cloud (BYOC) deployment on the Custom plan (talk to an engineer).
- 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) →Sources ↓
- Hatchet Pricing ↗
“For 100M+ runs a month, dedicated capacity, or enterprise features. [...] Dedicated capacity and multi-region [...] Self-hosted and BYOC support”
Read 2026-09-27 · official pricing · Report a correction
- Zeplo Pricing (app) ↗
“Need more? [...] For custom volume, SLAs, or dedicated infrastructure, reach out.”
Read 2026-09-13 · official pricing · Report a correction
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 — 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.
Questions this comparison answers.
Entry paid plan: Hatchet or Zeplo?
Hatchet: No plan fee: Pay-as-you-go is $0 a month and bills only usage past the free million runs and events ($30 per million runs). Custom, for 100M+ runs a month or enterprise features, is priced by conversation.
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 and no plan fee: 1M task runs and 1M events free each month with a card on file, then $30 per million runs, with 10,000 concurrent worker slots before any contract.
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.

Comments are hosted by EchoThread, which sets cookies and offers social sign-in. Like the analytics on this site, it does not load until you accept — see the privacy page.