Up until recently, open APIs were a cheat code for SaaS.
You opened up your platform, let developers build on top of it, and suddenly you weren’t just selling software anymore. You were building an ecosystem. Salesforce, Shopify, Stripe, SalesLoft, Twilio all rode this wave. Every integration made the core product stickier. Every partner extended reach into workflows you didn’t have to build yourself.
Open APIs weren’t charity. They were leverage.
They made sense in a world where software took time to build, integrations were painful, and distribution was everything. If ten startups built on top of you, that was ten more reasons customers couldn’t rip you out.
That world is fading. Fast
Why Big SaaS Is Starting to Close the Gates
Over the last couple of years, something interesting has happened. Some of the biggest platforms in SaaS have started limiting, restructuring, or outright blocking API access. Not quietly either. Public disputes. Rate limits. Sudden policy changes. Lawsuits.
This isn’t random. It’s defensive behavior. A recent blog post by Tomasz Tunguz got straight to the point: “They don’t build defenses unless they perceive credible & urgent challengers. AI’s speed enables both startups & incumbents to own a stack end-to-end. That’s offense in an era of walls.”
Three forces are colliding.
- AI collapsed the time to competition
AI didn’t just make teams more productive. It changed the slope of what’s possible.A small team can now spin up features, products, and entire workflow layers in months that used to take years. That means the distance between “nice integration” and “direct competitor” has shrunk dramatically.If you’re a large platform and a startup can use your API plus AI to recreate 60 percent of your product and ship faster than your internal roadmap, that API stops feeling like a growth channel and starts feeling like a loaded gun.Gating access is the fastest way to slow that down. - APIs became products, not plumbing
APIs used to be connective tissue. Now they are often the product.They carry proprietary data. They expose differentiated workflows. In AI-native environments, they can directly generate revenue. Tokenized usage. Model access. Embedded automation.Once an API becomes a revenue line and a strategic surface area, it gets treated like one. Pricing. Quotas. Compliance. Legal terms. Competitive review.You don’t leave the vault door open when the vault itself is the business. - Control matters more in a fast world
The faster innovation moves, the more dangerous uncontrolled surfaces become.APIs introduce performance risk, security risk, data leakage risk, and increasingly regulatory risk. When third parties can build powerful products on top of your platform in weeks, platform owners start caring a lot more about who is building, what they are building, and how fast they can scale.Walled gardens are not just about greed. They are about predictability.
The Quiet Shift: From Open Platforms to Managed Ecosystems
This doesn’t mean APIs are going away.
They are just changing roles.
We are moving from “build whatever you want” to “build what fits inside our strategy.” Access is more likely to be tiered. Approved. Monetized. Contracted. Sometimes delayed. Sometimes denied.
The new default is not openness. It’s conditional openness.
And that’s a philosophical shift for SaaS.
In the 2010s, platforms won by expanding outward. In the 2020s, they are trying to avoid being hollowed out from the edges.
What This Means for Builders
For startups, this is already changing how companies get built.
You can’t assume API access is permanent. You can’t assume it will scale with you. You can’t assume today’s integration won’t become tomorrow’s blocked endpoint.
That forces a few strategic responses:
- Owning more of your own data layer
- Building differentiated workflows, not just wrappers
- Designing products that can survive platform hostility
- Treating platform dependence as a board-level risk
The bar is going up. Not for talent, but for independence.
What I Think Comes Next
A few predictions that feel increasingly likely.
- APIs become operating systems, not interfaces
Platforms will use APIs to enforce policy, not just expose data. Expect rules around what agents can do, what data they can touch, how automation runs, and how activity is governed, logged, and monetized. - Data gravity becomes the real moat
Features get commoditized. Control over live data streams, behavioral exhaust, and learning loops becomes the core defensibility. These surfaces will be the most locked down. - Platform risk becomes board-level
Dependency on a single API becomes a first-order diligence issue. Startups design for survivability: multi-platform support, customer-owned data planes, and replaceable dependency layers. - Open ecosystems will re-emerge elsewhere
Every time incumbents close ranks, new open layers tend to appear.
Open standards. Open data models. Open agent frameworks. Federated protocols. Infrastructure-first platforms that compete specifically on openness.
Some of the most interesting SaaS companies of the next cycle won’t win because they are the biggest. They’ll win because they are the safest place to build.
The Bigger Picture
Open APIs used to be how SaaS companies expanded. Now they are one of the main ways SaaS companies defend. AI isn’t killing platforms. It’s making their edges more dangerous.
So the gates are going up.
The next wave of software competition won’t just be about features and models. It will be about who controls the surfaces where innovation is allowed to happen, and under what terms.
That battle is already underway.
