What makes a developer platform “great”?

Cloudflare begins this year’s Platform Week with a focus on its core value of being principled — a guiding idea for the announcements ahead. The company argues that the common yardsticks for judging platforms — raw speed, novelty, or raw capability — can distract from what developers actually need: the freedom to assemble the best available services into a single application.

That promise, however, has eroded as the cloud industry consolidated. Many of the early underdogs became dominant incumbents, and the ecosystem shifted from healthy competition to an unbalanced market. In Cloudflare’s view, the result is that too many providers make it deliberately difficult to leave once you start building with them, whether through pricing structures or through proprietary APIs that create invisible switching costs.

Lock-in: pricing and code

The most direct form of this lock-in is egress fees, which effectively punish developers for moving data between providers. The result is that teams stay with an in-ecosystem tool not because it is the best fit, but because leaving is economically wasteful. Cloudflare positions freedom of choice as the true promise of the internet for developers: the ability to specialize and mix best-of-breed offerings without hidden economic penalties.

A second, often subtler kind of lock-in happens at the code level. Applications bind themselves to a vendor’s APIs, and over time it becomes practically impossible to switch. The antidote is open standards — common languages and behavior that let developers move between providers without rewriting their applications. Vendors that commit to standards compete on the quality of what they offer, rather than on making their customers dependent on them.

What to expect this Platform Week

The week’s announcements will center on that philosophy rather than on novelty alone. Cloudflare has outlined areas where it intends to demonstrate principles in practice:

  • The open web foundation: The company sets out to contribute back to the open standards that the web’s infrastructure is built on, treating that shared groundwork as a prerequisite for everything else.
  • Data: An update on a service that has been in beta, with the possibility of a related new offering to follow.
  • Connectivity: Making it easier and cheaper to send data between the different pieces of a stack, so integrations don’t create hidden costs.
  • Media workflows: New ways to upload, stream, and share content — the practical stuff developers build for every day.
  • Programmability: Extending the concept beyond mere API calls. Cloudflare wants developers to be able to customize behavior of its network itself — bot scores, load balancing, routing — and to build with true programmability that reaches across the web, not just inside a single vendor’s platform.

The goal is longer-term than one week of product launches. Cloudflare wants a landscape where developers can build on their chosen provider combination, and where staying with a vendor is a sign of continued quality, not entrapment.