Loading...
2 tracked companies leading container & infrastructure orchestration in 2026, by publicly observable engineering signals.
Container orchestration and infrastructure-as-code tooling remained dominated by HashiCorp's stack in 2026 (Terraform, Vault, Consul, Nomad) — until IBM's $6.4B acquisition closed and reshaped the category's commercial dynamics. Cloud-native challengers (Pulumi, Crossplane, OpenTofu) gained ground.
infrastructure · public · Go
A quantitative view of HashiCorp's public engineering activity — what we track and why investors watch it.
infrastructure · series b · Go / Elixir / Rust
A quantitative view of Fly.io's public engineering activity — what we track and why investors watch it.
IaC and orchestration are the boring infrastructure layer that nonetheless underpins every enterprise platform team. The category-leader in 2026 is the one whose engineering org navigates the post-HashiCorp-acquisition consolidation by either acquiring the next IaC team or shipping the cleanest cloud-native challenger.
Watch the OpenTofu and Pulumi ecosystem signals. With Terraform now under IBM, contributor influx around OpenTofu (the OSS fork) and Pulumi (the cloud-native challenger) will shape the next cycle. Engineering-signal pattern: provider/plugin contributor counts on each.
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.
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.
From the VC Deal Flow Signal tracked set, the leaders are HashiCorp, Fly.io. Ranking is by publicly observable engineering acceleration (commit velocity, contributor influx, repo creation pulse, language-bias drift) — not by revenue, valuation, or fundraise size.
IaC and orchestration are the boring infrastructure layer that nonetheless underpins every enterprise platform team. The category-leader in 2026 is the one whose engineering org navigates the post-HashiCorp-acquisition consolidation by either acquiring the next IaC team or shipping the cleanest cloud-native challenger.
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 OpenTofu and Pulumi ecosystem signals. With Terraform now under IBM, contributor influx around OpenTofu (the OSS fork) and Pulumi (the cloud-native challenger) will shape the next cycle. Engineering-signal pattern: provider/plugin contributor counts on each.
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.