Loading...
2 tracked companies leading background jobs & workflows in 2026, by publicly observable engineering signals.
Background-job and workflow platforms run async work that doesn't fit a HTTP request — cron, queues, multi-step durable workflows, retry logic. Inngest and Trigger.dev anchor the developer-first lane; legacy queues (Sidekiq, SQS, Celery) still dominate at scale but lose ground every quarter.
developer-tools · series a · TypeScript / Go
A quantitative view of Inngest's public engineering activity — what we track and why investors watch it.
developer-tools · series a · TypeScript
A quantitative view of Trigger.dev's public engineering activity — what we track and why investors watch it.
Every AI agent system needs durable background execution. The category became infrastructure-grade in 2026 as agent frameworks added native integrations with Inngest and Trigger.dev. Engineering signals here are dominated by TypeScript codebases plus deep workflow-engine internals.
Watch the durable-execution layer. The platform that ships the most robust crash-resume, time-travel debugging, and replay-safe execution semantics will likely be the one agent frameworks default to. Engineering-signal pattern: contributor influx on the execution-engine repos tracks closely with category-leader status.
IDEs, frameworks, build systems, package managers, and the productivity layer engineers actually touch. A single page mapping who builds, who funds, and who leads in developer tools.
Edge platforms, runtimes, networking, observability primitives, and the platform-as-a-service layer. A single page mapping who builds, who funds, and who leads in cloud infrastructure.
From the VC Deal Flow Signal tracked set, the leaders are Inngest, Trigger.dev. Ranking is by publicly observable engineering acceleration (commit velocity, contributor influx, repo creation pulse, language-bias drift) — not by revenue, valuation, or fundraise size.
Every AI agent system needs durable background execution. The category became infrastructure-grade in 2026 as agent frameworks added native integrations with Inngest and Trigger.dev. Engineering signals here are dominated by TypeScript codebases plus deep workflow-engine internals.
Companies in the trend are members of the curated /signal/ corpus. The category fit is editorial — companies are included where their public GitHub org clearly ships in this category. Ordering favors the publicly self-described category leader followed by peers ordered by editorial relevance, not by a quantitative score.
Watch the durable-execution layer. The platform that ships the most robust crash-resume, time-travel debugging, and replay-safe execution semantics will likely be the one agent frameworks default to. Engineering-signal pattern: contributor influx on the execution-engine repos tracks closely with category-leader status.
Each /signal/[company] page links the underlying GitHub org and the public signal panel. For the full methodology see /methodology and SSRN 6606558. Raw aggregates ship via the public MCP server at /api/v1.
The free Acceleration Watch: five venture-backed teams accelerating on the engineering signal, translated into plain English — 21 to 47 days before the deck circulates. No code-reading, no card.