Background Jobs & Cron pricing, compared

Trigger.devFree

Compute is priced on the Small 1x machine (0.5 vCPU) at $0.0000338/s = $0.12168/hour; the Micro machine (0.25 vCPU) costs half that. The monthly credit (Free $5, Hobby $10, Pro $50) pays for both runs and compute, but the model spends it all on compute and charges runs from the first one, so paid plans are overstated by at most the run charges inside the credit. Free is modelled as two separate caps ($5 of compute alone = 41.09 hours, $5 of runs alone = 200k runs); really both draw on the same $5. Waits longer than 5 seconds are not charged compute, and runs in the DEV environment are free. Pro add-ons (extra concurrency $10 per 50, extra seats beyond 25 at $20 each) are left out.

UpstashPay as you go

Messages are taken as runs (one delivery attempt = one run). The daily limits are converted to months as × 30: Free 1,000/day ≈ 30k/month, Fixed 1M/day ≈ 30M/month, Fixed 10M/day ≈ 300M/month — a bursty month can hit the daily cap sooner. QStash calls your own HTTP endpoint, so compute_hours is not charged here — it is paid to your host. Bandwidth is not modelled. Upstash's Redis and Workflow products are priced separately.

TemporalDeveloper (pay as you go)

Assumes one action per run or step: a simple workflow that starts and calls two activities with no retries, timers or signals ≈ 3 actions; heartbeats, retries and timers add more, so real usage is usually higher. Rate = $50 per million actions × 1.10 for the 10% Developer support fee = $0.055 per thousand. The docs say the Developer plan stays at $50 per million at any volume (the pricing page mentions self-service discounts down to $25 per million at higher volume, which the docs attach to Business and above). Business ($500/month minimum, 2.5M actions included, graduated rates from $50 to $25 per million) is left out — at solo volumes it costs more than Developer. Storage is not modelled. compute_hours is not charged (your own workers). New accounts get $150 of credits for 90 days, not modelled.

InngestPro

runs_k is read as executions = runs × (steps + 1), Inngest's own formula. Overage tiers come from the pricing calculator on the vendor's page: $0.00005 per execution from 1M to 5M, $0.000025 to 15M, $0.00002 to 50M, $0.000015 to 100M; above 100M is not published, so the model stops there. Inngest calls your own functions (serverless or workers you host), so compute_hours is not charged here — it is paid to your host. Business ($499/month, 10M executions) is left out: at 10M executions Pro costs about $424. Event ingestion beyond the included amount (Pro 5M, then $0.50 per 1M) is not modelled.