Skip to content
inetGeek

Trigger.dev vs Zeplo

SEPT 2026 audit

A comparison of Trigger.dev and Zeplo built from values read directly from each provider's own documentation, with the source recorded against every figure.

Reviewed by Palash BagchiUpdated 21 criteria comparedSources last checked

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.

Neither quite fits? Every other option, ranked by iScore: Trigger.dev alternatives · Zeplo alternatives

12 sourced criteria separate them — see where, with sources, below.

Visit Trigger.dev documentationVisit Zeplo documentation

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionTrigger.devZeplo
Pricing
Free tierYesYes
Kind of free offerFree tierFree tier
What the free plan includes$5 of credit each month with 20 concurrent runs and one day of log retention.500 requests a month, described as free forever, for a single developer with 30-day log retention.
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 modelA 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.
Infrastructure
RegionsThree AWS regions for running tasks: us-east-1 (US East, Virginia), us-west-2 (US West, Oregon) and eu-central-1 (Europe, Frankfurt). Changelog dated July 13, 2026; region set per project or per run on the dashboard Regions page.Hosted on Google Cloud Platform; no selectable region is offered and data may be transferred between countries.
Queues
Included per monthCredits 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 retentionLog 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.
Concurrency20 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).
Compliance
GDPR / data residency
Stated GDPR compliant; DPA forms part of the Terms of Service automatically on sign-up.
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 restData encrypted at rest with AES-256 and in transit with HTTPS/TLS.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 controlRole-based access control (RBAC) and SSO listed as Enterprise plan features.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 infrastructureCloud is fully managed; the docs route teams with data residency, compliance or infrastructure-control requirements to self-hosting instead.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.

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

Where they differ.

What the free plan includes

Trigger.dev
$5 of credit each month with 20 concurrent runs and one day of log retention.
Zeplo
500 requests a month, described as free forever, for a single developer with 30-day log retention.
Sources (2) →

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) →

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) →
  • 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 · 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

Trigger.dev
Three AWS regions for running tasks: us-east-1 (US East, Virginia), us-west-2 (US West, Oregon) and eu-central-1 (Europe, Frankfurt). Changelog dated July 13, 2026; region set per project or per run on the dashboard Regions page.
Zeplo
Hosted on Google Cloud Platform; no selectable region is offered and data may be transferred between countries.
Sources (2) →
  • New region: US West (Oregon) | Changelog ↗

    “Trigger.dev now runs in three AWS regions: [...] us-east-1 (US East, Virginia) [...] us-west-2 (US West, Oregon) [...] eu-central-1 (Europe, Frankfurt)”

    Read 2026-09-13 · official site · 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

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) →

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.

Zeplo

256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company.

Sources (2) →
  • 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 · 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

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.
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) →

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) →

GDPR / data residency

Trigger.dev
Stated GDPR compliant; DPA forms part of the Terms of Service automatically on sign-up.
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) →
  • Security | Trigger.dev ↗

    “Yes, Trigger.dev is GDPR compliant. Visit our Security Portal for more information, or contact us to request data deletion.”

    Read 2026-09-13 · official site · 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

Trigger.dev
Data encrypted at rest with AES-256 and in transit with HTTPS/TLS.
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) →

Role-based access control

Trigger.dev
Role-based access control (RBAC) and SSO listed as Enterprise plan features.
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) →

Dedicated infrastructure

Trigger.dev
Cloud is fully managed; the docs route teams with data residency, compliance or infrastructure-control requirements to self-hosting instead.
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) →

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

03.

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.

When the free offer endsZeplo: Never — 500 requests a month, free forever.
Maximum delayZeplo: 30 days (2,592,000 seconds) maximum delay_seconds per request.
Dead letter queueZeplo: Limited — Dead-letter handling is a webhook fired on permanently failed requests, not a separate queue you consume.
Support on entry paid planTrigger.dev: Community support on the $5 and $10 plans; dedicated Slack support on Pro ($50/month); priority support on Enterprise.
SOC 2Trigger.dev: SOC 2 Type II compliant; latest report available on request for Enterprise customers.
HIPAATrigger.dev: Meets HIPAA Business Associate requirements; a signed BAA is a paid add-on for running PHI workloads on Trigger.dev Cloud.
Private networking / VPCTrigger.dev: AWS PrivateLink to resources in your own AWS VPC; a Pro and Enterprise feature enabled on request.
04.

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.

Provider pages

Trigger.devBackground jobs platform billed as monthly credits against compute, with plan tiers set by concurrent runs.ZeploHTTP request queue priced per request, with 30-day log retention on every plan including free.

Related comparisons

Amazon SQS vs Trigger.devAmazon SQS vs ZeploCloudflare Queues vs Trigger.devGoogle Cloud Pub/Sub vs Trigger.devHatchet vs Trigger.devHatchet vs ZeploInngest vs Trigger.devInngest vs Zeplo

Comments

Every page here is sourced and dated.