SaaS Ranking
Menu

Trigger.dev: what they publish

trigger.dev · Workflow automation · checked 2026-10-29

61/100CBand C

Rank 4 of 41 in Workflow automation, where the median is 35.

Public transparency score, not a product or security rating. Latest check: 2026-10-29. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

3 days since the newest dated result, 3 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Trigger.dev

trigger.dev · Workflow automation

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
C 61of 100 Rank 4 of 41

Published commitments5 of 9 found

Measured behaviour2 of 3 found

Checked 2026-10-29. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Trigger.dev has no such document.

Where Trigger.dev sits in Workflow automation

  1. A1 2%
  2. B0 0%
  3. C3 7%
  4. D9 22%
  5. E15 37%
  6. F13 32%
41 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Trigger.dev is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Trigger.dev states

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data location: where they say data is hosted

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://trigger.dev/security · checked 2026-10-29

Show the 7 addresses we checked
  1. https://trigger.dev/security – found, but behind a sign-in
  2. https://trigger.dev/trust – reached, no match (HTTP 404)
  3. https://trigger.dev/legal/privacy – reached, no match (HTTP 200)
  4. https://trigger.dev/privacy – reached, no match (HTTP 404)
  5. https://trigger.dev/privacy-policy – reached, no match (HTTP 404)
  6. https://trigger.dev/compliance – reached, no match (HTTP 404)
  7. https://trigger.dev/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Data location stated in Workflow automation: 16 of 42 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-29.

Show the 3 addresses we checked
  1. https://status.trigger.dev/ – reached, no match (HTTP 200)
  2. https://trigger.dev/status – reached, no match (HTTP 404)
  3. https://trigger.dev.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Status page with history in Workflow automation: 12 of 42 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-10-29.

Show the 1 address we checked
  1. https://trigger.dev/ – third-party requests before any interaction: analytics.ahrefs.com, imagedelivery.net, unpkg.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Workflow automation: 3 of 42 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-29.

Show the 6 addresses we checked
  1. https://trigger.dev/legal/sla – reached, no match (HTTP 404)
  2. https://trigger.dev/sla – reached, no match (HTTP 404)
  3. https://trigger.dev/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://trigger.dev/trust/sla – reached, no match (HTTP 404)
  5. https://trigger.dev/uptime – reached, no match (HTTP 404)
  6. https://trigger.dev/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Workflow automation: 5 of 41 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-10-29.

Show the 7 addresses we checked
  1. https://trigger.dev/legal/privacy – reached, no match (HTTP 200)
  2. https://trigger.dev/privacy – reached, no match (HTTP 404)
  3. https://trigger.dev/privacy-policy – reached, no match (HTTP 404)
  4. https://trigger.dev/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://trigger.dev/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://trigger.dev/trust/privacy – reached, no match (HTTP 404)
  7. https://trigger.dev/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Named privacy contact in Workflow automation: 28 of 41 companies

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 7
✓

Data processing agreement (DPA)

weight 3 of 3

Published and readable without a login.

Source: https://trigger.dev/legal/dpa · checked 2026-10-29

Across the market: Data processing agreement in Workflow automation: 9 of 42 companies

✓

Subprocessors: the published list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://trigger.dev/legal/subprocessors · checked 2026-10-29

Across the market: Subprocessor list in Workflow automation: 7 of 42 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://trigger.dev/pricing · checked 2026-10-29

Across the market: Public pricing in Workflow automation: 27 of 41 companies

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 63072000 seconds (730 days).
    Show the exact wording

    max-age=63072000

    Read at https://trigger.dev/

Source: https://trigger.dev/ · checked 2026-10-29

Across the market: HTTPS enforced with HSTS in Workflow automation: 30 of 43 companies

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

  • Notice promised before the list changes 30 days.
    Show the exact wording

    cessor, Trigger.dev will use reasonable endeavours to notify the Customer of such changes to Sub-processor(s), and the Customer shall have the right to terminate the Agreement within 30 days after its

    Read at https://trigger.dev/legal/dpa

Source: https://trigger.dev/legal/dpa · checked 2026-10-29

Across the market: Notice before subprocessors change in Workflow automation: 9 of 41 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page HIPAA, SOC 2 (not counted: the sentence does not carry it), SOC 2 Type II. The sentence we kept does not carry this finding on its own, so it counts in no list and no figure.
    Show the 3 exact wordings

    Get started for free Copy setup prompt Paste in your agent Open source SOC 2 Type II HIPAA BAA available GDPR Compliant Trigger.dev logo Docs Quick start Tasks Schedules Concurrency Retries

    Read at https://trigger.dev/security

    Is Trigger.dev SOC2 compliant?

    Read at https://trigger.dev/security

    Yes, Trigger.dev is SOC 2 Type II compliant.

    Read at https://trigger.dev/security

Source: https://trigger.dev/security · checked 2026-10-29

Across the market: Certifications named in Workflow automation: 24 of 41 companies

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://trigger.dev/.well-known/security.txt · checked 2026-10-29

Across the market: security.txt (RFC 9116) in Workflow automation: 8 of 39 companies

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Trigger.dev

7 found · 5 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-29.

Investigate 5 open evidence questions
  1. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  2. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  3. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  4. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  5. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    Inspect this check

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.