Postman kills free team collaboration March 2026, driving mass Bruno migration with no CI enforcement layer for Bruno collection breaking changes
Postman eliminated free team collaboration on March 1 2026, capping the free plan to one user and pricing teams at $19 per user per month. This triggered the largest Bruno adoption wave since its launch -- Bruno is an offline-first, Git-native API client storing collections as human-readable .bru files. The HN post announcing Bruno reached 1538 points and 400 comments. Bruno's file-per-request Git-native format is its core selling point, but developers have no tooling to enforce API contract stability in CI. When a developer modifies a .bru collection file (changes an endpoint URL, adds a required header, removes a query param), there is no automated gate that catches the breaking change before it reaches staging. Existing OpenAPI CLI tools (spectral, openapi-diff) check spec files, not Bruno's .bru format. The gap: a CLI that parses .bru collection diffs in a PR, detects breaking changes against a baseline collection version, and fails CI with a human-readable report.
Score Breakdown
Social Proof 2 sources
Gap Assessment
Bruno has 60k+ GitHub stars and is the de-facto replacement for Postman for individual and small-team use. No CI enforcement tooling exists for .bru format. The existing OpenAPI breaking-change CLI in the idea pipeline targets OpenAPI spec files -- .bru collection files are a different format with different semantics. Bruno maintainer has not shipped a CI integration layer. Teams that migrated from Postman have no automated safety net.