# Trigger.dev vs Zeplo

Canonical: https://inetgeek.com/compare/trigger-dev-vs-zeplo/

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

## At a glance

| Criterion | Trigger.dev | Zeplo |
| --- | --- | --- |
| 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. |
| 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. ([source](https://trigger.dev/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

- 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. ([source](https://trigger.dev/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))

### 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. ([source](https://trigger.dev/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

- Trigger.dev: 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. ([source](https://trigger.dev/docs/limits))
- 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

- Trigger.dev: Log retention of 1 day on the free plan, 7 days on Hobby and 30 days on Pro, with the query period matching. ([source](https://trigger.dev/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

- Trigger.dev: 20 concurrent runs on the free plan, 50 on Hobby, and more on Pro at $10 a month per additional 50. ([source](https://trigger.dev/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 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.

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

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

- Regions: Zeplo: Hosted on Google Cloud Platform; no selectable region is offered and data may be transferred between countries.
- Maximum delay: Zeplo: 30 days (2,592,000 seconds) maximum delay_seconds per request.
- SOC 2: Trigger.dev: SOC 2 Type II compliant; latest report available on request for Enterprise customers.
- HIPAA: Trigger.dev: Meets HIPAA Business Associate requirements; a signed BAA is a paid add-on for running PHI workloads on Trigger.dev Cloud.
- GDPR / data residency: Trigger.dev: Stated GDPR compliant; DPA forms part of the Terms of Service automatically on sign-up.
- Encryption at rest: Trigger.dev: Data encrypted at rest with AES-256 and in transit with HTTPS/TLS.
- Role-based access control: Trigger.dev: Role-based access control (RBAC) and SSO listed as Enterprise plan features.
- Private networking / VPC: Trigger.dev: AWS PrivateLink to resources in your own AWS VPC; a Pro and Enterprise feature enabled on request.

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