A/B tests we've caught
Trigger.dev
trigger.dev1 detection · 5 conversion patterns
Pages we're watching
- landing · 28
- home · 2
- pricing · 1
- product · 1
Detected A/B tests at Trigger.dev

ABWatcher has detected 1 A/B test at Trigger.dev since Jun 2026. Most target the hero.
Key facts
- Detections
- 1
- Latest detection
- Jun 25, 2026
- Conversion patterns
- 5
- Pages we monitor
- landing, home, pricing, product
| Detected | Page | Surface | What changed |
|---|---|---|---|
| home | hero | Chrome visit shows a different hero description copy emphasizing 'full observability, Use existing Node.js SDKs and code from your repo' and a different hero code/terminal layout, while Safari, Firefox, and Edge all show consistent copy about 'tool-calling, automatic retries, realtime, queuing, scheduling.' Edge and Chrome share the Blink engine yet diverge, indicating a real A/B test rather than browser rendering differences. |
Conversion patterns
contrarian
"Only pay when your code is actually executing"
A contrarian pricing value prop embedded mid-page as a feature callout, not buried in pricing. This directly kills the #1 objection (idle infrastructure cost) at the moment a developer is evaluating the product.
risk reversal
"We love open source" brand values moment with Apache 2.0 call-out
A dedicated section with a heart icon explicitly stating the Apache 2.0 license and self-host option acts as a risk-reversal for enterprise/developer buyers worried about lock-in — rare to see license terms elevated to a trust signal at this prominence.
calculator
Granular compute pricing table with machine specs
Instead of opaque 'usage-based pricing', they expose a full machine-spec table (vCPU, GB RAM, cost/sec) letting developers calculate exact costs before committing. This eliminates the #1 objection for infra pricing pages — bill shock fear — right on the pricing page.
contrarian
Separate per-second compute cost + per-invocation run cost model
Trigger.dev splits billing into two transparent components (compute cost per second + $0.25 per 10,000 run invocations), which is highly unusual and signals developer-first honesty. Most SaaS hides this complexity; surfacing it builds trust with the exact ICP (engineers) who would otherwise distrust black-box pricing.
copy
"Can I run AI agents on Trigger.dev?" FAQ answer as use-case unlock
Embedding an AI-agent use-case answer directly in the pricing FAQ (not the product page) intercepts the fastest-growing buyer persona at the moment of purchase consideration, reframing the product as an agentic infrastructure play rather than just a job queue.
Common questions about Trigger.dev
Does Trigger.dev A/B test?
Yes. ABWatcher has detected 1 A/B test at Trigger.dev across 4 page types since Jun 2026. Latest detection: Jun 25, 2026.
What has Trigger.dev recently changed?
Most recent change (6/25/2026): Chrome visit shows a different hero description copy emphasizing 'full observability, Use existing Node.js SDKs and code from your repo' and a different hero code/terminal layout, while Safari, Firefox, and Edge all show consistent copy about 'tool-calling, automatic retries, realtime, queuing, scheduling.' Edge and Ch
Which pages of Trigger.dev does ABWatcher monitor?
landing (28), home (2), pricing (1), product (1). We add new pages as they become discoverable via the sitemap.
How does ABWatcher detect A/B tests on Trigger.dev?
We crawl the brand's public pages from isolated browser sessions with varying fingerprints, look for vendor-SDK fingerprints (Optimizely, VWO, Statsig and others), compare the DOM across isolated visits within a single run, and diff each run against the prior week's snapshot. A vision model then describes what changed.
Get Trigger.dev's tests the day we catch them.
7 days of Pro, free, no card. Then Free forever for ten watched companies. Watched brands get crawled first.
Want us to watch a brand we don't track yet?
Requests reorder the crawl queue. We'll email you the moment the first detection lands.
Embed the live feed on your site
Drop this snippet into any page. It renders the latest 5 caught tests at Trigger.dev and refreshes automatically.
Spotted a test at Trigger.dev we haven't caught?
Send us the URL and a quick note. We review every submission; if it confirms, we credit you on the detection page.