---
published: true
layout: post
title: Open at Launch, Walled Off by Series D
image: https://kinlane-images.s3.amazonaws.com/apievangelist/api-evangelist-images/open-at-launch-walled-off-by-series-d.png
date: 2026-08-06
author: Kin Lane
tags:
  - APIs
  - Business
  - Investment
  - Walled Gardens
  - SaaS
  - Strategy
---
I can almost set my watch by it now. A startup launches with an open API, generous free tier, real documentation, an SDK in every language, and a developer relations person who genuinely wants you to build something. They mean it, in that early moment. They need you--your integrations are how they prove traction, how they show the market they are a platform and not just an app. So the doors are wide open, and for a couple of funding rounds it feels like the good old days of the API economy.

Then Series D shows up, and the doors start to close. It is not personal and it is not a betrayal of principles, because the openness was never a principle--it was a growth tactic with an expiration date. Early on, the business needs your integrations more than it needs to monetize your access, so it gives access away. Later, once the platform has captured enough gravity that leaving is painful, the math flips: now the data flowing through your integrations is worth more locked up than given away, and the investors who put in that late-stage money expect to see it captured. The free tier shrinks. The useful endpoints move behind enterprise sales. The export that used to be one click sprouts an "contact us" form. The API is still there. It is just no longer for you.

I said this to [Nordic APIs](https://nordicapis.com/kin-lane-on-ai-and-the-future-of-apis/) and I will say it here: this is not a bug in the venture playbook, it is the playbook. Capture as much value as you can, give away as little as possible, and treat the early openness as a customer-acquisition cost you stop paying the moment you can get away with it. SaaS makes the trap tighter, because once your data lives inside their walls and their formats, the closing of the API is not an inconvenience you route around--it is a wall you are already standing inside of. You did not lose access to a tool. You lost access to your own operational history, which now lives somewhere you can only read on their terms.

And this pattern does not stay confined to scrappy startups--it scales all the way up, and gets worse as it climbs. The enterprise version of the walled garden used to belong to Oracle, and we all understood the shape of that particular cage. But the gardens got bigger. Now it is Microsoft, Amazon, and Google, and the walls are taller and the grounds are vastly larger than anything Oracle ever fenced. A Google shop buys Google's answer to every problem. A Microsoft shop standardizes on the Microsoft version of everything and lives inside Office 365. The quirky, best-in-class third-party API with the weird auth and the brilliant feature loses--not because it is worse, but because it is outside the garden, and the garden's whole value proposition is that you never have to leave.

That is the part that should bother anyone who cares about a healthy ecosystem. The consolidation is not selecting for the best tools. It is selecting for the tools that are already inside the wall. Enterprises are trading away access to genuine innovation for the comfort of a single vendor relationship and one throat to choke, and they are calling it a strategy. The mediocre-but-integrated option beats the excellent-but-external one, over and over, until the external option gives up or gets acquired and absorbed into a garden of its own. The incentives all point toward enclosure, and very little points back the other way.

I do not have a tidy fix for this, because the forces driving it are economic, not technical, and you do not out-engineer a business model. But I do think the first move is to stop being surprised by it. If you are building on someone else's open API today, price in the closing. Assume the free tier is a promotion, assume the export will get harder, assume the Series D or the acquisition is coming, and own your own data flows accordingly. And if you are a founder, understand that every wall you build to please a late-stage investor is also a wall around your own ceiling--the same enclosure that captures short-term value is the thing that caps how large the platform could have ever become. The gardens are winning right now. That does not make the enclosure a good idea. It makes it the thing worth designing against.