Skip to main content
Webhooks have no separate charge on Trigger.dev Cloud. Receiving, verifying, filtering and recording deliveries is included in every plan. The runs a delivery starts or resumes are billed like any other run: a per-run invocation cost plus compute time. See pricing. A delivery that no subscriber’s filter matches starts no run, so it adds no run cost. A run already waiting for that webhook still resumes and is billed like any other run. A run waiting for a webhook is suspended, so it uses no compute until the webhook arrives. Each plan sets limits on the ingest rate, waiting runs, processing concurrency and how long deliveries are kept. See Limits. Webhooks are open source, so they also work self-hosted. See Self-hosting webhooks to turn them on.