The Quiet Re-bundling of Developer Tools

The best-of-breed era produced genuinely better individual tools. It also produced stacks with fourteen vendors, fourteen SSO configurations, fourteen security reviews and fourteen renewal dates.

The integration overhead grew until it exceeded the marginal quality gain of the fourteenth tool, which is where consolidation always starts.

Developer tools were historically adopted bottom-up by engineers using company cards. The rise of platform engineering created a team whose explicit mandate is standardisation, and whose budget covers the tools.

Platform teams optimise differently. They weight audit capability, SSO, cost governance and integration surface above the developer experience an individual engineer would prioritise. That shift alone explains most of the recent consolidation.

Platforms with credible breadth win: GitHub bundling CI, security scanning and development environments; GitLab selling a single self-hosted application; Cloudflare packaging security, performance and compute on one network.

The squeeze lands on point solutions that are better than the bundled equivalent but not dramatically better. Being 20% ahead on one dimension no longer justifies a separate vendor relationship.

Consolidation has a limit, and it is observability pricing. Bundled platforms with consumption billing have produced enough invoice shock that a wave of point solutions is being adopted specifically to cut costs on individual signals.

The equilibrium looks like a consolidated core with deliberate exceptions where a bundled product's economics are indefensible, which is a more stable arrangement than either extreme.