72 / 100

Trigger.dev pricing teardown

https://trigger.dev/pricing

Trigger.dev's pricing page is clean and developer-focused, with a well-structured 4-tier model (Free → Hobby → Pro → Enterprise) anchored by usage-based compute billing layered on top of flat monthly fees. The page does strong work on transparency — compute rates, run invocation costs, and a worked usage example are all visible — but lacks an annual billing toggle and the featured 'Hobby' plan at $10/mo may undercut perceived value relative to the $50 Pro tier. Overall it's a solid self-serve page with a few optimization gaps.

Tier structure

Free

$0/mo

Hobby

$10/mo

Pro

$50/mo

Enterprise

Custom

Value metric

flat-rate per tier with included credits + usage-based compute (per second) and per-run invocation fees on top

How limits scale

Concurrent Runs 20 → 50 → 200+ → Custom
Schedules 10 → 100 → 1000+ → Custom
Log Retention 1 day → 7 days → 30 days → Custom
Alert Destinations 1 → 3 → 100+ → Custom
Realtime Connections 10 → 150 → 1000+ → Custom

Escalation logic

Tiers escalate from a free entry tier with $5 credits to Hobby ($10) and Pro ($50), each including more credits, higher concurrency, longer log retention, and more team/environment features. Enterprise adds compliance, SSO, and custom discounts with no public price.

Psychological anchors

  • Highlighted recommended plan — The Hobby plan card has a green border and a green 'Get started' CTA button, visually distinguishing it as the featured/recommended tier via the decoy effect.
  • Enterprise as price anchor — The 'Enterprise — Custom' tier with no public price anchors perception of Pro at $50/mo as accessible and reasonable by comparison.
  • Free tier as entry anchor — A $0 Free plan with $5/mo included credits lowers the barrier to entry and drives top-of-funnel signups, with feature gating pushing upgrades.
  • Included credits framing — Each paid tier states '$X/month credits included', making the subscription feel like prepaid value rather than a pure access fee, reducing perceived cost.
  • Transparent compute pricing table — A detailed machine-size pricing table with per-second and per-hour rates, plus a worked dollar example in the FAQ, builds developer trust and reduces purchase anxiety.
  • Expansion pricing signals on Pro — Pro lists overage prices inline (e.g. '$10/month per 50 concurrency', '$20/month per seat') signaling a clear expansion revenue path without hiding costs.

What this page is optimizing for

The page is primarily optimized for self-serve developer conversion — transparent pricing, instant 'Get started' CTAs, a free tier, a worked usage example, and a detailed FAQ all reduce friction for individual developers and small teams. Secondary optimization is for expansion revenue via Pro's metered overage pricing on concurrency, seats, and branches.

Red flags

  • No annual billing toggle is present anywhere on the page, leaving a standard 17-20% discount lever unused and reducing perceived value for committed buyers.
  • The Hobby plan at $10/mo is highlighted as featured, but the jump to Pro at $50/mo is a 5x price increase with no intermediate tier, creating a large gap that may cause churn at the Hobby ceiling.
  • Team member limit is identical on Free and Hobby (both 5 members), removing a meaningful upgrade trigger between those two tiers.
  • The value metric is complex — flat fee + included credits + per-second compute + per-run invocation — which may confuse non-technical buyers or finance stakeholders evaluating the product.
  • Enterprise tier has no feature count or limit hints visible, making it hard for mid-market buyers to self-qualify without contacting sales.
  • No social proof, customer logos, or testimonials appear on the pricing page itself, which are standard trust signals at the point of purchase decision.

Best-practices scorecard

What works · 4

  • Clear recommended tier — Hobby is visually highlighted with a green border and green CTA, clearly signaling the recommended entry point.
  • Visible prices — Free ($0), Hobby ($10/mo), and Pro ($50/mo) are all publicly visible; only Enterprise is custom/opaque.
  • FAQ or objection handling — A comprehensive FAQ section covers usage estimation, concurrency, self-hosting, rate limits, HIPAA, and more — directly addressing developer purchase objections.
  • Clear CTAs per tier — Each tier has a distinct CTA: 'Get started' for Free/Hobby/Pro and 'Contact us' for Enterprise, with appropriate differentiation.

Half measures · 3

  • Value metric matches usage — Usage-based compute pricing aligns well with developer workflows, but the layered model (flat fee + credits + compute + invocations) adds cognitive complexity for new visitors.
  • Tier differences are scannable — Feature lists are detailed and structured, but the long vertical lists per tier make side-by-side comparison difficult without a comparison table.
  • Trust signals present — GitHub star count (15.8k) in the nav and open-source Apache 2.0 license mention provide credibility, but no customer logos, case studies, or testimonials appear on the pricing page.

What's missing · 1

  • Annual discount offered — There is no annual billing toggle or annual discount mentioned anywhere on the page.