Background jobs and cron

The ledger

Newest first. A fact, a company’s own claim about itself and a user’s opinion are all here, and the tag on each row is which one you are reading.

• Trigger.devPRODUCTFACTSep 30, 2026

  The v4.6.1 release (Sept 15, 2026) added new CLI commands for projects, runs, and environment management, and introduced Node.js 21 deprecation warnings in deployment logs and email notifications.

  Baseline record of current CLI/runtime deprecation posture.

  trigger.dev/changelog/v4-6-1
• Trigger.devPRODUCTFACTSep 30, 2026

  The v4.6.2 release (Sept 16, 2026) added authorization hardening across realtime payloads, public tokens, and chat sessions, and improved chat agent trace spans showing warm idle time versus durable waits separately.

  Continued build-out and security hardening of the new chat-agent feature area.

  trigger.dev/changelog/v4-6-2
• Trigger.devPRODUCTFACTSep 30, 2026

  In the v4.6.0 release (Sept 14, 2026), Trigger.dev shipped 'chat agents' with a TranscriptStorage adapter that persists conversation history turn-by-turn; the platform still defaults to snapshot storage, but developers can point it at their own database adapter.

  Signals a product push into durable AI agent/chat workflow infrastructure, a new product area beyond generic background jobs.

  trigger.dev/changelog/v4-6-0
• Trigger.devPRICINGCOMPANY CLAIMSep 30, 2026

  Trigger.dev Cloud has four tiers: Free ($5/month included credits, 20 concurrent runs, unlimited tasks, 5 team members, 1-day log retention), Hobby ($10/month, $10 credits, 50 concurrent runs, 7-day retention), Pro ($50/month, $50 credits, 200+ concurrent runs, 25+ seats, 30-day retention, dedicated Slack support), and Enterprise (custom pricing with SSO, RBAC, SOC 2/pen-test reports, priority support). Usage beyond credits is billed per-second by machine size plus a per-run invocation fee of about $0.000025.

  Establishes the current pricing/packaging baseline for future comparison.

  www.zenml.io/blog/trigger-dev-pricing
• Builders of generated apps adding scheduled workDISCOURSEFACTSep 30, 2026

  A 2026 comparison piece frames the current background-job decision for new projects as choosing between Solid Queue (Postgres-backed, no Redis needed, good for teams wanting 'operational simplicity') and Sidekiq (Redis-backed, wins at higher throughput or when advanced batch features are needed).

  Shows the broader (non-Next.js) ecosystem is also converging on 'skip Redis, use what you already have' as the framing — relevant context for how generated-app builders think about adding infra.

  ttb.software/2026/02/08/background-jobs-rails-solid-queue-sidekiq/
• Builders of generated apps adding scheduled workCOMPLAINTUSER OPINIONSep 30, 2026

  A recent guide notes that on serverless platforms like Vercel, 'node-cron won't work since there's no always-running server process,' and that using node-cron inside Next.js API routes 'may cause issues... since API routes are stateless, leading to multiple cron registrations on each request.'

  Captures the core friction driving this segment's search for alternatives — the naive scheduling approach breaks on the exact deployment targets generated apps typically use.

  webredo.net/article/how-to-set-up-cron-jobs-in-nextjs-without-vercel
• Builders of generated apps adding scheduled workPRODUCTFACTSep 30, 2026

  Inngest provides a documented pattern for running scheduled cron functions and event-triggered background jobs in Next.js apps deployed on Vercel or Netlify without provisioning additional infrastructure like message queues or dedicated schedulers.

  Represents a well-established competing path for the same buyer need (serverless-friendly scheduled/background work) that generated-app builders commonly reach for.

  www.inngest.com/blog/run-nextjs-functions-in-the-background
• Builders of generated apps adding scheduled workPRICINGFACTSep 30, 2026

  Queuebase's homepage lists a Free tier explicitly 'For hobby projects and side-builds' at $0 forever, including 10,000 jobs/month, 5 concurrent jobs, 7-day retention, and 1 project.

  Establishes a concrete, named free-tier price point that side-project builders could adopt instead of rolling their own queue.

  www.queuebase.com/
• Builders of generated apps adding scheduled workPRODUCTCOMPANY CLAIMSep 30, 2026

  Queuebase positions itself as a type-safe background job SDK for Next.js with no new infrastructure, no workflow DSL, and no lock-in, offering a local dev worker (npx queuebase dev) that mirrors the hosted production service's API.

  Directly targets the exact buyer in this segment — someone shipping a generated Next.js app who needs scheduling without provisioning Redis/queues — with a named, purpose-built product.

  www.queuebase.com/
• Serverless background workPRODUCTCOMPANY CLAIMSep 30, 2026

  Multiple third-party tools (QStash, Inngest, Tickstem, Crontap, Runhooks) have been built specifically to work around Vercel's serverless timeout and cron limitations by orchestrating retried steps, external HTTP scheduling, or heartbeat/failure monitoring.

  Indicates an active third-party ecosystem/market has formed around this complaint theme, a signal of the discourse crossing into a recognized niche product category.

  dev.to/whoffagents/upstash-qstash-serverless-background-jobs-without-the-infrastructure-pain-ic8
• Serverless background workPRODUCTFACTSep 30, 2026

  Vercel's Fluid Compute feature allows functions to run up to 5 minutes on free plans and up to 800 seconds (about 13 minutes) on paid plans, with durations up to 30 minutes available in beta for supported Node.js, Bun, and Python runtimes, and supports background processing via waitUntil (or after in Next.js) to continue tasks after sending an initial response.

  Represents Vercel's own platform mitigation for the timeout complaint, relevant to developers evaluating whether to build custom workarounds.

  vercel.com/kb/guide/what-can-i-do-about-vercel-serverless-functions-timing-out
• Serverless background workCOMPLAINTUSER OPINIONSep 30, 2026

  On Vercel's free Hobby plan, cron jobs are capped at a small number (1-2) and can run at most once per day, with sub-daily cron expressions rejected at deploy time, forcing upgrades to Pro or use of external cron services.

  Affects Hobby-tier developers needing frequent scheduled jobs; a recurring third-party-verified complaint theme (multiple independent sources).

  crongenerator.dev/cron-vercel/
• Serverless background workCOMPLAINTUSER OPINIONSep 30, 2026

  Vercel's built-in cron is criticized for having no failure alerts, no execution history on the Hobby plan, HTTP-only scope, no heartbeat/completion monitoring, and a minimum 1-hour interval on Hobby requiring a paid plan for sub-hourly schedules.

  Affects teams relying on Vercel cron for scheduled jobs who need monitoring/frequency beyond Hobby limits, pushing them to third-party schedulers.

  dev.to/mike_tickstem/vercel-cron-alternative-what-to-use-when-built-in-cron-isnt-enough-52dp
• Serverless background workCOMPLAINTUSER OPINIONSep 30, 2026

  Developers report that Vercel serverless function timeouts (as low as 10 seconds on Hobby, up to 300-800s on paid tiers) kill long-running jobs like PDF generation, data imports, and multi-step AI pipelines mid-execution with no partial-completion guarantee.

  Affects developers building full-stack Next.js/Vercel apps with long-running background work; drives adoption of workaround tools.

  daily.dev/posts/how-to-fix-vercel-function-timeouts-with-background-jobs-p3k8jvisv
• UpstashCOMPLAINTUSER OPINIONSep 30, 2026

  Users report Upstash can get very expensive for large-scale use cases, citing a $800/month fixed price for 100GB with only a 16,000 requests/second limit, and note pay-as-you-go metered costs compound at high traffic.

  Establishes a baseline complaint theme (cost-at-scale) to track for repeat/independent sightings.

  www.tryorbye.com/products/upstash
• UpstashPRICINGCOMPANY CLAIMSep 30, 2026

  Upstash bills per request rather than per server: Redis is $0.20 per 100K commands, Vector is $0.40 per 100K query/update requests, and QStash is $1 per 100K messages, each with storage at $0.25/GB and a permanent free tier, plus fixed plans from $10/month up to $1,500/month.

  Establishes baseline pricing structure across product lines for future comparison.

  www.srvrlss.io/provider/upstash/
• UpstashPOSITIONINGFACTSep 30, 2026

  Upstash's current homepage describes itself as a serverless data platform offering Redis, Vector, Search, QStash, Workflow, Box, and Blob, with per-request pricing and no servers to provision.

  Positioning has broadened well past 'serverless Redis and Kafka' to a multi-product data/AI-agent platform, adding Box (sandboxed AI agent containers) and Blob (S3-compatible storage) as newer product lines.

  upstash.com/
• UpstashPRODUCTFACTSep 30, 2026

  Upstash deprecated Upstash Kafka on September 11, 2024 and fully discontinued it on March 11, 2025, directing users toward Upstash Workflow for durable serverless functions instead.

  Buyers evaluating Upstash for Kafka workloads must look elsewhere; this is a significant narrowing from its original 'Redis and Kafka' positioning.

  www.srvrlss.io/provider/upstash/
• CronitorCOMPLAINTUSER OPINIONSep 30, 2026

  Independent comparison sites frame Cronitor's per-monitor plus per-user pricing as expensive at scale relative to flat-rate or usage-based competitors, citing example costs like $125–$350/month for teams with 50-150 monitored jobs.

  Recurring competitive narrative that Cronitor's per-seat/per-monitor model is costly for growing teams — worth tracking for repeat mentions.

  drumbeats.io/blog/drumbeats-vs-cronitor-cron-job-monitoring
• CronitorPRICINGCOMPANY CLAIMSep 30, 2026

  Third-party pricing trackers describe a three-tier Cronitor structure: free 'Hacker' plan (5 monitors, email/Slack alerts, 1-month retention), 'Business' plan priced near $2/monitor plus $5/user with unlimited API requests and 12-month retention, and a custom 'Enterprise' plan reported around $6,000/yr with a dedicated engineer.

  Baseline pricing reference; could not be independently confirmed by directly fetching cronitor.io/pricing, so treat as provisional until verified.

  www.xpay.sh/saas-pricing/cronitor-io/
• CronitorPRODUCTCOMPANY CLAIMSep 30, 2026

  Cronitor's status pages product automatically opens and resolves incidents from monitor state changes, supports four uptime windows (24h/7d/30d/90d), custom domains with HTTPS, and keeps flapping failures grouped into a single readable incident.

  Baseline feature set for comparison against other status-page offerings.

  cronitor.io/status-pages
• CronitorPRODUCTCOMPANY CLAIMSep 30, 2026

  Cronitor markets heartbeat monitoring explicitly for AI agents in addition to services, scripts, and devices, letting users attach metrics (tokens, cost, latency) to each heartbeat and alert on bad values even when beats arrive on time.

  Relevant to any competitor targeting AI-agent-ops or LLM-cost-tracking monitoring niches.

  cronitor.io/heartbeat-monitoring
• CronitorPOSITIONINGCOMPANY CLAIMSep 30, 2026

  Cronitor's homepage now leads with AI agent monitoring alongside its traditional cron/uptime/heartbeat positioning: "Monitor AI agents, cron jobs, websites, APIs, and everything in between — with instant alerts when something breaks."

  Signals Cronitor is repositioning toward the AI agent observability market, a space competitors should watch for overlap.

  cronitor.io/
• InngestFUNDINGCOMPANY CLAIMSep 30, 2026

  Inngest has raised $34M across four rounds including a $3M seed in July 2023 from GGV Capital and a $6.1M Series A in January 2024 from Andreessen Horowitz, with a Series B in May 2025.

  Baseline funding history; no Series B amount was stated so it is omitted from amountMillions.

  hokai.io/hub/tools/inngest
• InngestPRODUCTFACTSep 30, 2026

  As of mid-September 2026, Inngest shipped CLI OAuth login for cloud/MCP clients, expanded REST API and run-list filtering with CEL support, and introduced sandbox lifecycle contracts, alongside queue, debounce, and error-handling fixes.

  Shows continued investment in developer tooling/CLI and AI-assistant (MCP) integration ahead of any baseline comparison.

  releasebot.io/updates/inngest
• InngestPRODUCTFACTSep 30, 2026

  TypeScript SDK v4 reached general availability on March 16, 2026, a major version with breaking changes but described as trivial migration for most apps.

  Core SDK migration affecting all existing Inngest developer customers.

  www.inngest.com/changelog/2026-03-17-typescript-sdk-v4-ga
• InngestPRODUCTFACTSep 30, 2026

  Inngest's changelog shows a recent run of AI-focused and observability features: an 'AI Overview' dashboard for monitoring gen_ai cost/latency/usage (added around August 7, 2026), propagated Sessions across child runs for grouping related workflow runs, a beta 'Scoring' API (inngest.score()) to judge AI run quality, and 'Experiments' for safely testing code changes against live production traffic.

  Signals a positioning shift toward AI agent observability/evaluation tooling, relevant to competitors in the agent-orchestration space.

  www.inngest.com/changelog
• InngestPRICINGFACTSep 30, 2026

  Inngest also offers an Enterprise tier sold via AWS Marketplace as a 12-month contract billed at $50,000, covering custom scale limits, dedicated support, and security controls like SAML, RBAC, and audit trails.

  Relevant to enterprise buyers evaluating contract-based procurement via AWS Marketplace.

  aws.amazon.com/marketplace/pp/prodview-iuavm7g2rxwz4
• InngestPRICINGFACTSep 30, 2026

  Inngest's current pricing page lists a Free/Hobby tier (5 seats, 50k executions, 5 concurrent steps, 3 workers, 500k events ingested), a Pro tier starting at $99/mo (15 seats, 1M executions + add-on, 100+ concurrent steps, 20 workers + add-on, Datadog/advanced observability add-on, HIPAA add-on), and a Business tier starting at $499/mo.

  Establishes the baseline pricing ladder buyers compare against Temporal and Trigger.dev.

  www.inngest.com/pricing