Trigger.dev

Open coreWorkflow engine

Build and deploy durable AI agents and workflows

Homepage Docs Pricing Repository

Scanned 15 Oct 2026 · Schema v5 · features v21

From: $10/mo
plan tier (quotas + features) + usage (per-second compute per machine size + per-run invocation fee)
Free tier: Yes
No card required.
Isolation: Container
shares the host kernel
Regions: —
Region placement is now a real user-facing capability ('Deploy tasks to multiple regions for lower latency to users or data sources'; per-region static IPs) — so multi-region scores pass — but the actual region list and per-region addresses stay behind the dashboard (the auth-gated 'Regions' page), not the public surface. Sub-processors (updated 2026-10-13) show AWS + DigitalOcean (USA) and Cloudflare/ClickHouse as the infra plane; PostHog (EU) and some UK/US SaaS providers. Self-host placement is the operator's choice.
Capabilities: 18 / 61
6 partial · 29 fail · 0 not assessed
Agent readiness: 10.5/11 · 10.5/11
read · drive, pre-login surface

Advertised for

AI agents · AI chat agents · Background jobs · Scheduled tasks & cron · Etl/rags · Media processing · Human in the loop · Browser automation

Built for

Developers, then technical

· Code-first: 'Plain async/await code with no DSL' TypeScript tasks; CLI init/dev/deploy; MCP/skills for coding agents
· First-class TS SDK + Realtime React hooks; Python only via build extension
· Usage pricing: per-second compute per machine size + $0.25/10k runs; paused time free

01 Pricing plan tier (quotas + features) + usage (per-second compute per machine size + per-run invocation fee)

Tier	EntryFree	Hobby	Pro	TopEnterprise
Price	$0/mo	$10/mo	$50/mo	custom
Includes	$5/mo free credits · 20 concurrent runs · unlimited tasks · 5 team members · 10 schedules · 1-day logs/query · 10 Realtime conns · 1 alert destination · preview branches	$10/mo credits · 50 concurrent · 100 schedules · 7-day logs · 5 preview branches · 3 alert destinations · 150 Realtime conns · HIPAA BAA add-on	$50/mo credits · 200+ concurrent ($10/50) · 25+ members ($20/seat) · 20+ preview branches ($10/ea) · 1000+ schedules ($10/1k) · 30-day logs/query · 1000+ Realtime conns ($10/1k) · 5+ custom dashboards ($10/ea) · AWS PrivateLink · HIPAA BAA add-on · dedicated Slack support	All Pro + custom discounts, custom log retention, RBAC, SOC 2 report, penetration test report, SSO, priority support, HIPAA BAA
Compute hours overage	$0.12168/h	—	—	—
Request overage	$0.000025 per request	$0.000025 per request	$0.000025 per request	—

compute-second (per machine size) + per-run invocation ($0.25/10,000 runs); paused/checkpointed time NOT billed·Card required: No·trigger.dev

Overages: per-run $0.000025 ($0.25/10k); compute per-second per machine (Small 1x $0.0000338/s ≈ $0.122/hr → Large 2x 8vCPU/16GB $0.00068/s); add-on blocks: +50 concurrency $10, +seat $20, +preview branch $10, +dashboard $10, +1k schedules $10, +1k Realtime conns $10

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

Dark, restrained developer-tool marketing site: near-black surfaces (body background rgb(18,19,23)), soft off-white text, generous whitespace and a large type hierarchy, with one vivid lime-green accent (measured rgb(168,255,83) on CTAs and active nav) used sparingly. Pricing uses a clean four-column card grid with fine low-contrast rules; docs shares the dark theme with a conventional 304px sidebar, search and lime active-state markers. A blurred terminal hero image and a cookie-consent banner (landing/pricing) are visible; no broken images or failed renders on any of the three pages.

Editorial minimalism

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Containershares the host kernel

Persistence

checkpoint-resume (no persistent-disk; runs ephemeral, state snapshotted at wait points)

Snapshots / forks

Yes

Resources & limits

Storage

ephemeral per-run; durable run state via managed checkpoint storage (Cloud); self-host operators provide object storage themselves

Limits & quotas

Concurrency per environment (prod: Free 20 / Hobby 50 / Pro 200+, then $10 per +50); API rate limit 1,500 req/min all tiers (higher on request; batchTrigger up to 1,000 tasks/call); queued-run TTL cap 14 days (Cloud); machines Micro 0.25 vCPU/0.25 GB → Large 2x 8 vCPU/16 GB; Realtime connections Free 10 → Pro 1000+ ($10/1k); schedules Free 10 → Pro 1000+ ($10/1k)

GPU

Access

Deploy interface

cligit-deploy

SDK languages

TypeScriptJavaScriptpython (via build extension only)

Network & secrets

Egress controls

Not documented

Secrets

Yes

Bring your own cloud

advertised (placeholder)

Placement & use

Jurisdiction

multi-region workers (region list behind the dashboard); subprocessors in USA (AWS, DigitalOcean, Cloudflare, ClickHouse) + EU provider present

Advertised workloads

AI agentsAI chat agentsBackground jobsScheduled tasks & cronEtl/ragsMedia processingHuman in the loopBrowser automation

04 Capabilities 18 pass · 6 partial · 29 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 4/10

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Not applicable

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Partially supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 0/4

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Not applicable

Built-in reverse proxyPlatform routes external traffic to workload services.

Not applicable

Custom domainsBring-your-own domain via CNAME/DNS.

Not applicable

Public preview URLsShareable per-deploy / per-branch URLs.

Not applicable

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Not supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Partially supported

Email send / receiveSend and/or receive email from the workload.

Not applicable

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 5/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 2/11

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Not applicable

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not supported

Data 0/4

First-party databasePlatform-provided managed database.

Not supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 4/6

Scheduled tasksCron / scheduled job primitive.

Supported

Durable workflowsDurable execution / long-running workflow primitive.

Supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Partially supported

Organisation & security 3/8

Built-in authPlatform-provided authentication / IAM for workloads.

Not applicable

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Partially supported

BYOCRuns inside the customer's own cloud account.

Partially supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Supported

Proposed, not verified

Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.

Realtime / bidirectional input streamsrealtime-streams
“Streams push typed data INTO a running task and stream run state/tokens out to React hooks or backend subscribers — a first-class bidirectional stream primitive” trigger.dev
chat.agent durable agent sessionsdurable-agent-sessions
“Every conversation gets its own computer: state survives in memory between turns, idle conversations sleep and cost nothing, and the next message resumes on the same line of code” trigger.dev
Ask Trigger — in-dashboard AI assistant over project datadashboard-ai-assistant
“Introducing Ask Trigger to your dashboard (changelog, 2026-10-05) — a first-party assistant that answers questions about your project” trigger.dev

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

10.5/11

10 full · 1 partial · 95% of applicable checks

llms.txt
Supported
“GET /llms.txt 200, 7.7KB, last updated 2026-10-09 — links docs + pricing + product pages + comparisons + a for-ai-crawlers index (https://trigger.dev/for-ai-crawlers)”
llms-full.txt
Supported
“GET /llms-full.txt 200, 28KB 'Extended technical documentation' (updated 2026-10-08) with Quick Facts table + full exposition — CHANGED from fail (2026-06: not located)”
robots.txt AI policy
Supported
“robots.txt (946B) explicitly Allows GPTBot, ChatGPT-User, OAI-SearchBot, Claude-User/Chat/Web/Bot, PerplexityBot, Cohere-ai, Google-Extended, Applebot-Extended, Meta-ExternalAgent, anthropic-ai”
JSON-LD
Supported
“homepage carries application/ld+json SoftwareApplication: name 'Trigger.dev', applicationCategory DeveloperApplication, description, url”
Sitemap
Supported
“robots.txt Sitemap pointers → GET /sitemap.xml 200, 22KB, non-trivial (also blog/changelog/for-ai-crawlers RSS)”
Meta tags
Supported
“homepage: title 'Trigger.dev | The open source platform for durable AI agents' + og:title + descriptive meta description”
Markdown negotiation
Supported
“VERIFIED this scan: curl -H 'Accept: text/markdown' https://trigger.dev/pricing returns text/markdown (15.6KB); llms.txt also documents 'append .md to the URL … or request the HTML URL with the header Accept: text/markdown' — CHANGED from partial”
Content efficiency
Partially supported
“homepage readable-text÷HTML = 14,125/464,197 bytes = 3.04% — a Next.js app-shell+RSC payload; above the 1% JS-shell floor, below the 5% server-rendered bar”
Docs discoverable
Supported
“'Docs' is a first-class header nav item on every page; docs root serves a 335-URL llms.html index and its own /docs/llms.txt (64KB)”
Machine-readable pricing
Supported
“structured per-tier plans (Free/$0·$5 credit, Hobby/$10, Pro/$50, Enterprise/custom) + a per-second per-machine compute matrix + per-run fee, in clean markdown”
No anti-bot wall
Supported
“No challenge on any public content: every fetch 200 (curl + the browser design pass); a cookie-consent banner is present but not a bot wall”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

10.5/11

10 full · 1 partial · 95% of applicable checks

Public API
Supported
“Documented management REST API (trigger/manage runs, batches, bulk actions, errors, queues, schedules) via @trigger.dev/sdk + HTTP”
OpenAPI spec
Supported
“https://trigger.dev/docs/v3-openapi.yaml — fetchable OpenAPI 3.1.0, 248KB, verified 200 on 2026-10-15 (CHANGED from fail: the docs API surface links it; the apex /openapi.json still 404s, which is where the 2026-06 scan stopped)”
MCP server
Supported
“npm-installable MCP server with docs + interactive installer: 'npx trigger.dev@latest install-mcp' (v3 rubric full credit; /.well-known/mcp 404s but is not required)”
SDK packages
Supported
“Official npm packages: @trigger.dev/sdk (4.7.4) + trigger.dev CLI + React Realtime hooks (registry.npmjs.org verified)”
Auth documented
Supported
“/docs/apikeys: per-environment secret keys (TRIGGER_SECRET_KEY); public API keys omit payload/output for security”
Self-serve credentials
Partially supported
“Signup → dashboard/CLI key (no card required, but a human OAuth/signup step; programmatic key issuance not documented)”
Webhooks
Supported
“wait-for-token: 'pause for approvals, webhooks, and external events' — the waitToken URL is designed to be handed to external services (openapi spec) + docs/wait-for-token”
CLI tool
Supported
“Official trigger.dev CLI (init, dev, deploy, login, skills, install-mcp; command docs per page in docs index)”
Error model
Supported
“Documented JSON error model: OpenAPI components.schemas.ErrorResponse on 401/404/422/429 + a whole Errors API (error groups, resolve/ignore/unresolve) — CHANGED from partial (2026-06: schema unverified)”
Rate limits documented
Supported
“/docs/limits: 1,500 API requests/min all tiers (higher on request, paid), batchTrigger to 1,000 tasks/call, TTL/quota tables”
Agent config files
Supported
“Multiple agent-config surfaces: trigger.dev/SKILL.md (bootstrap skill), /docs/skills (open-standard installable skills), /docs/mcp-agent-rules, MCP installer for 12 named clients”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 11

Claude Code Anthropic
Supported
“Client Configuration … Claude Code: npx trigger.dev@latest install-mcp --client claude-code (or .mcp.json config 'command': 'npx', 'args': ['trigger.dev@latest', 'mcp'])”
Source trigger.dev
Trigger.dev SKILL.md also teaches Claude Code to bootstrap a project ('trigger.dev/SKILL.md').
Codex CLI OpenAI
Supported
“Codex CLI install tab: npx trigger.dev@latest install-mcp --client codex”
Source trigger.dev
Cursor Anysphere
Supported
“Cursor install tab with .cursor/mcp.json config”
Source trigger.dev
Also targeted by the open-standard agent skills installer (npx trigger.dev@latest skills writes .cursor/skills/).
Windsurf Codeium
Supported
“Windsurf install tab: npx trigger.dev@latest install-mcp --client windsurf”
Source trigger.dev
Cline Cline
Supported
“Cline install tab in the MCP client configuration list”
Source trigger.dev
Zed Agent Zed
Supported
“Zed install tab in the MCP client configuration list”
Source trigger.dev
Zed is a multiple-cursor Zed agent host — recorded under the harnesses.yml zed-agent slug.
Gemini CLI Google
Supported
“Gemini CLI install tab: npx trigger.dev@latest install-mcp --client gemini-cli”
Source trigger.dev
Amp Sourcegraph
Supported
“AMP install tab in the MCP client configuration list”
Source trigger.dev
OpenCode opencode
Supported
“opencode install tab in the MCP client configuration list”
Source trigger.dev
Crush
Supported
“Crush install tab in the MCP client configuration list”
Source trigger.dev
UNREGISTERED in harnesses.yml as of this scan — recorded here per the harnesses.yml AGENT-GATED rule (unknown names are recorded + surfaced for admission); propose admitting Charm's Crush CLI.
Ruler
Supported
“Ruler install tab in the MCP client configuration list”
Source trigger.dev
UNREGISTERED in harnesses.yml — recorded for admission review (Ruler is a cross-tool agent-rules manager, arguably an orchestrator like OpenClaw). VS Code is also named in the docs but deliberately NOT recorded (an editor host, held out of the registry per the vscode 'host, not a harness' note in features.yml).

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 3

SOC 2 Type II
certifiedhostedExplicit TYPE II now stated on the dedicated security page with SOC 2 Type II badge (previously 'SOC 2 report' on the Enterprise tier with type unspecified). scope:hosted — covers the managed Cloud, NOT a self-hosted deployment. The Enterprise tier additionally ships the SOC 2 report + a penetration-test report.
“Trigger.dev is SOC 2 Type II and GDPR compliant.”
Source trigger.devConfidence: high
HIPAA
enterprise-onlyhostedHIPAA BAA available as a paid add-on from Hobby upward ('Request a BAA' links on Hobby/Pro/Enterprise pricing cards). status per schema enum: enterprise-only/b paid-add-on gated; not a certification the company holds.
“Request a HIPAA Business Associate Agreement as a paid add-on to process Protected Health Information.”
Source trigger.devConfidence: high
GDPR
self-attestedhostedGDPR badge/attestation on the security page; DPA available at /legal/dpa. Self-attested standing for GDPR (no certifying body). scope:hosted.
“SOC 2 Type II and GDPR compliant”
Source trigger.devConfidence: medium

Regions —

Regions are not disclosed on the public surface.

Region placement is now a real user-facing capability ('Deploy tasks to multiple regions for lower latency to users or data sources'; per-region static IPs) — so multi-region scores pass — but the actual region list and per-region addresses stay behind the dashboard (the auth-gated 'Regions' page), not the public surface. Sub-processors (updated 2026-10-13) show AWS + DigitalOcean (USA) and Cloudflare/ClickHouse as the infra plane; PostHog (EU) and some UK/US SaaS providers. Self-host placement is the operator's choice.

Legal

Privacy notice Terms of service

08 Open source Apache-2.0 · fetched by machine, not quoted from marketing

Licence & repository

Licence: Apache-2.0OSI
Primary language: TypeScript
Stars: 16,545
Forks: 1,499
Created: 30 Nov 2022
Archived: No

Activity

Last commit: 14 Oct 2026
Latest release: v4.7.4 · 14 Oct 2026
Issues open / closed: 178 / 827 · 82% closed

Weekly-ish patch/minor cadence: v4.7.0 (10-01) → 4.7.1 (10-02) → 4.7.2 (10-02) → 4.7.3 (10-06) → v4.7.4 (10-14); paired helm-vX tags now ship for every release (Helm chart maintained). Very active.

Fetched via gh on 15 Oct 2026.

Self-hosting

Methods: dockercomposekuberneteshelm
You operate: postgresredisclickhouseobject-storage

Apache-2.0, fully self-hostable via Docker Compose, Kubernetes, or a maintained Helm chart (helm-v4.7.4 releases). Self-host loses vs Cloud (docs feature-comparison table, 2026-10-15): warm starts ❌, auto-scaling ❌, CHECKPOINTS ❌ (self-hosted waits block the executor rather than snapshot-and-free — the durability model is weaker off-Cloud, t.y good to re-verify per release), dedicated support ❌. Operator also runs the dependency plane (Postgres + Redis + ClickHouse for logs + object storage).

Documentation signals 8/8

SupportedQuickstart
SupportedAPI reference
SupportedSelf-host guide
SupportedChangelog
SupportedOpenAPI
Supportedllms.txt
SupportedExamples
SupportedArchitecture doc

09 Company & presence Facts only, not scored

Company

Headquarters: Altrincham, Cheshire, United Kingdom (registered office: 3rd Floor, 1 Ashley Road, WA14 2DT); team UK remote/hybrid
Founded: 2022
Team size: small startup (~10–15; not formally disclosed)
Hiring: active — 6 open positions (2026-10-15)

Funding

2023-08Seed · $3M
2025-12Series A · $16M

Notable people

Matt Aitken (CEO)
Eric Allam (CTO)
James Ritchie
Dan Patel
ex-JSON Hero team

Activity

Last release: v4.7.4 (2026-10-14); weekly-ish v4.7.x cadence since 10-01 trigger.dev
Last blog post: 2026-10-14 — '7 things we wish we'd known before building an AI chat agent' trigger.dev

Presence 6

Links found on the public surface scanned; not an exhaustive search.

10 Sources & method How this entry was produced

Public surface only

Everything here was read from trigger.dev's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Workflow engine products →