# Trigger.dev

Official pricing: https://trigger.dev/pricing  
Category: paas · Isolation: container

## Pricing regimes (raw)

- **Managed tasks** (sizes): Micro 0.25 vCPU/0.25 GiB $0.060840000000000005/h; Small 1x 0.5 vCPU/0.5 GiB $0.12168000000000001/h; Small 2x 1 vCPU/1 GiB $0.243/h; Medium 1x 1 vCPU/2 GiB $0.30600000000000005/h; Medium 2x 2 vCPU/4 GiB $0.6120000000000001/h; Large 1x 4 vCPU/8 GiB $1.2240000000000002/h [alt]

## Features

Yes: snapshots, memory snapshots, pause/resume, persistent disk, idle auto-stop, ≥24 h sessions, custom image (Docker or snapshot), start from your own snapshot, browser, open internet, static egress IP, private networking, self-hosting, open source, SOC 2, HIPAA, SSO, Python, Node.js, wake on request, webhooks, scheduled runs (cron), EU data residency, scoped API keys, spend limits, MCP server, automatic snapshots, hosted agent API (their own agent)

No: fork/clone, volumes, your own Docker/OCI image, full VM (own kernel), Docker inside, nested virtualization, desktop GUI, computer-use API, browser + desktop control, anti-bot stealth, CAPTCHA solving, residential IPs, preinstalled agents, SSH, public IPv4, HTTPS preview URLs, egress allowlist, BYOC, GPU, arm64, Windows, macOS, HTTP method/path egress rules, live resize, live fork (no pause), memory fork, snapshots on demand, agent harness API, gVisor or VM (no shared kernel), inbound access rules, firewall inside (nftables), secret proxy, secret proxy for any API, extra volumes, shared volumes

Unknown: everything else. Evidence (source + quote) per feature: https://battleships.dev/data/providers/trigger-dev.json → feature_evidence

## Caveats

- Durable TypeScript tasks, not arbitrary interactive VMs; mode is alt. Billed allocated machine seconds when executing plus $0.000025/run.
- Wait >5 seconds and parent waiting for subtasks are checkpointed and unbilled. No execution timeouts. Free 20 concurrency; Hobby 50; Pro 200 + $10/month per 50.
- Extra Pro seats $20/month beyond 25; HIPAA BAA is add-on not an included plan fee.
- Null values mean unknown, not free/unlimited. No model-token cost, tax or unverified ancillary charge included.
- Native browser/device/task/credit prices with unknown CPU/RAM are deliberately non-priceable. Check regime before interpreting any partial resource estimate.
- API rate limit 1,500 requests/min on all plans (raise on request, paid only); batchTrigger up to 1,000 runs per call; batch token bucket Free 1,200 burst + 100/10 s, Hobby/Pro 5,000 burst + 500/5 s per environment.
- Waits: wait.for/wait.until >5 s are not billed, but the concurrency slot is held until 60 s into the wait. chat.agent keeps the machine warm (billed) for idleTimeoutInSeconds (default 30 s) after each turn before suspending.
- Only production/staging/preview are billed; DEV runs execute on the developer's machine and are not charged.
- MicroVM compute (Firecracker) is in invite-only private beta in us-east-1-next, staging only; same presets, all sizes capped at 1 GB disk during the beta; no separate price published.

## How this provider charges


YC: Winter 2023; directory status **Active**. Research scope: public-product-researched. Source: https://www.ycombinator.com/companies/trigger-dev

Build and deploy fully‑managed AI agents and workflows

## Regime table

| Regime | When it applies | How billed | Numbers | Source |
|---|---|---|---|---|
| Managed tasks | alt | sizes; CPU alloc, memory alloc | Micro: 0.25 vCPU/0.25 GiB $0.060840000000000005/h; Small 1x: 0.5 vCPU/0.5 GiB $0.12168000000000001/h; Small 2x: 1 vCPU/1 GiB $0.243/h; Medium 1x: 1 vCPU/2 GiB $0.30600000000000005/h; Medium 2x: 2 vCPU/4 GiB $0.6120000000000001/h; Large 1x: 4 vCPU/8 GiB $1.2240000000000002/h; Large 2x: 8 vCPU/16 GiB $2.4480000000000004/h | https://trigger.dev/pricing |
| Free | Plan limits apply | Monthly fee; credits only as stated | fee=0; included usage=$5; concurrent=20; max session h=None | https://trigger.dev/pricing |
| Hobby | Plan limits apply | Monthly fee; credits only as stated | fee=10; included usage=$10; concurrent=50; max session h=None | https://trigger.dev/pricing |
| Pro | Plan limits apply | Monthly fee; credits only as stated | fee=50; included usage=$50; concurrent=200; max session h=None | https://trigger.dev/pricing |
| Enterprise | Plan limits apply | Monthly fee; credits only as stated | fee=None; included usage=$None; concurrent=None; max session h=None | https://trigger.dev/pricing |
| Retained disk / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://trigger.dev/pricing |
| Snapshots / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://trigger.dev/pricing |
| Egress / GiB | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://trigger.dev/pricing |
| IPv4 / month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://trigger.dev/pricing |

## Verified billing facts and gotchas

1. Durable TypeScript tasks, not arbitrary interactive VMs; mode is alt. Billed allocated machine seconds when executing plus $0.000025/run.
2. Wait >5 seconds and parent waiting for subtasks are checkpointed and unbilled. No execution timeouts. Free 20 concurrency; Hobby 50; Pro 200 + $10/month per 50.
3. Extra Pro seats $20/month beyond 25; HIPAA BAA is add-on not an included plan fee.

## Worked example

Requested: 4 vCPU/8 GiB, 50 simultaneous × 8 h/day × 22 days = **8,800 instance-hours**, 30% CPU; 50 GiB snapshots and 100 GiB egress. A month is 730 hours only when explicitly used in rate conversion.

50×22=1,100 eight-hour runs: 8,800×$1.224+$0.000025×1,100=$10,771.2275 usage. Hobby $10 includes $10: $10,771.23 recurring before unverified snapshot/network costs. 30% CPU does not discount allocated execution, but explicit checkpointed waits do.

## Sources and coverage

- https://www.ycombinator.com/companies/trigger-dev
- https://trigger.dev/pricing
- https://trigger.dev/docs/introduction
- https://trigger.dev/docs/self-hosting/overview
- https://trigger.dev/
- https://trigger.dev/llms.txt

Page captures and documentation indexes/bundles are in `raw/`; provider JSON lists the evidence paths. HN query results were captured separately as `<id>--hn.txt`; they are discovery leads, not current tariff authority. Downloaded docs do not imply every feature was verified; unsupported assertions remain null.