Bezos API Mandate

The document Petersen calls the most important in the industry

Ryan Petersen, founder of Flexport, cites Jeff Bezos's internal directive that every team at Amazon communicate with every other team through well-defined APIs, and calls it "probably the most important document in the technology industry's history."¹ The concept, as Petersen relays and applies it, is a rule about how software organizations are allowed to talk to each other, and by extension how the humans in them are.

The rule and its logic

The prohibition is specific: you cannot write code that reaches directly into another team's database. Petersen's reasoning is that the moment someone on the other team changes the schema, everyone depending on that direct access breaks at once. The mandated alternative is to place a service with an API in between, so each team owns its own data and exposes only a stable contract. Consumers depend on the contract, not the internals, and the internals can change without cascading failures.

Petersen is candid that the discipline feels like overkill for a small startup, and that people resist it, because it genuinely makes the organization slower up front. His argument is that skipping it is the more expensive choice over time: without the API boundary, a company drifts toward a bureaucracy "where no one can do anything." He glosses the tradeoff with a phrase he attributes to the Marine Corps: "slow is smooth and smooth is fast."¹ The up-front cost of the boundary buys the ability to move quickly later without collisions.

The extension to org design

Petersen does not treat the mandate as a purely technical rule. He extends it to how teams and meetings are structured, arguing that a meeting where everyone needs everyone else's approval is the human equivalent of every team hitting the shared database directly. In both cases a change in one place forces coordination everywhere, and the organization grinds. The API discipline, applied to people, points toward autonomous units that own their piece and interact through defined interfaces rather than universal sign-off. This makes the mandate, in Petersen's reading, the technical precondition for a team-of-teams structure: APIs are what let autonomous teams own their piece of the system without colliding.¹

The same lens explains, for Petersen, why incumbents in legacy industries struggle to move. Older systems built on mainframe architectures cannot easily expose modern APIs, so the software-driven disruption of those industries is partly a story about who can and cannot present clean interfaces to the rest of the world. The pattern shares its spine with zone management: both draw hard boundaries so that ownership inside a boundary stays clean and independent.

Tensions

Petersen does not present the mandate as costless or universal. He admits that Flexport carries its own technical debt, and describes himself as "paranoid" that a faster-moving competitor could exploit it, which is a reminder that the API discipline slows even the company that adopts it.¹ The deeper tension is timing. "You go slower to go fast" assumes you survive the slower period. A company building conservatively on a stable footing can afford the up-front tax; a company running against a hard runway clock may not be able to pay it before the money runs out. The mandate is a bet that the organization will live long enough to collect on the boundary it paid for.