Trigger.dev vs Zeplo
SEPT 2026 auditA comparison of Trigger.dev and Zeplo built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Trigger.dev if…
Teams that want background jobs written as normal code with the bill expressed as compute credits rather than a per-message meter.
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…
- Trigger.dev: Concurrency is the axis that forces an upgrade — 20 simultaneous runs on free, 50 on Hobby, then $10 a month per additional 50.
- 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.
6 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.
Trigger.dev 0
Zeplo 0
At a glance.
| Criterion | Trigger.dev | Zeplo |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Entry paid plan | $10/month for Hobby, which includes $10 of credits; Pro is $50/month including $50 of credits. | $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each. |
| Pricing model | A monthly plan fee that is also a credit balance — the fee buys compute rather than sitting on top of it — with concurrency, preview branches, dashboards and schedules each priced as separate add-ons beyond the plan's allowance. | 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. |
| Queues | ||
| Included per month | Credits rather than a message or execution count: $5 a month free, $10 included on Hobby and $50 on Pro, spent against compute. | 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 | 3 MB per trigger payload (each batch item up to 3 MB on SDK 4.3.1+); task outputs up to 10 MB; payloads over 512 KB offloaded to object storage. | 256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company. |
| Message retention | Log retention of 1 day on the free plan, 7 days on Hobby and 30 days on Pro, with the query period matching. | 30 days of log retention on every plan — free, Company and Enterprise alike. The longest window in this category by a wide margin. |
| Concurrency | 20 concurrent runs on the free plan, 50 on Hobby, and more on Pro at $10 a month per additional 50. | 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
- Trigger.dev
- $10/month for Hobby, which includes $10 of credits; Pro is $50/month including $50 of credits.
- Zeplo
- $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each.
Sources (2) →Sources ↓
- Pricing — Trigger.dev ↗
“Hobby $10/month [...] $10 / month credits included [...] Pro $50/month [...] $50 / month credits included”
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
- Trigger.dev
- A monthly plan fee that is also a credit balance — the fee buys compute rather than sitting on top of it — with concurrency, preview branches, dashboards and schedules each priced as separate add-ons beyond the plan's allowance.
- 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 — Trigger.dev ↗
“$10 / month credits included [...] Then $10/month per 50 [...] Then $20/month per seat [...] Then $10/month per branch [...] Then $10/month per 1,000”
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
Included per month
- Trigger.dev
- Credits rather than a message or execution count: $5 a month free, $10 included on Hobby and $50 on Pro, spent against compute.
- 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 — Trigger.dev ↗
“$5 / month free credits [...] $10 / month credits included [...] $50 / month credits included”
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
3 MB per trigger payload (each batch item up to 3 MB on SDK 4.3.1+); task outputs up to 10 MB; payloads over 512 KB offloaded to object storage.
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 ↓
- Limits - Trigger.dev ↗
“Single trigger payload Must not exceed 3MB Batch trigger payload Each item can be up to 3MB (SDK 4.3.1+). Prior: 1MB total combined Task outputs Must not exceed 10MB”
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
Log retention of 1 day on the free plan, 7 days on Hobby and 30 days on Pro, with the query period matching.
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 — Trigger.dev ↗
“1 day log retention 1 day query period [...] 7 day log retention 7 days query period [...] 30 day log retention”
Read 2026-09-06 · official pricing
- Pricing — Zeplo ↗
“Log retention 30 days 30 days 30 days”
Read 2026-09-06 · official pricing
Concurrency
- Trigger.dev
- 20 concurrent runs on the free plan, 50 on Hobby, and more on Pro at $10 a month per additional 50.
- 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 — Trigger.dev ↗
“20 concurrent runs [...] 50 concurrent runs [...] Then $10/month per 50”
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: Trigger.dev or Zeplo?
Trigger.dev: $10/month for Hobby, which includes $10 of credits; Pro is $50/month including $50 of credits.
Zeplo: $39/month for Company, including 1,000,000 requests and three team members. Additional members are $15 each.
Should I choose Trigger.dev or Zeplo?
Pick Trigger.dev if Teams that want background jobs written as normal code with the bill expressed as compute credits rather than a per-message meter.
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.