LangChain built one of the most widely adopted agent frameworks in the ecosystem. They had mindshare, community, integrations — the whole package. Then they open-sourced their deep agent work and pivoted monetization entirely to LangSmith, their observability layer. The framework itself could not sustain a business.
E2B raised significant capital on the thesis that the critical monetizable layer is the execution environment — the sandbox where agents actually run. They are not trying to own the framework. They are trying to own the ground the framework runs on.
Both arrived at the same conclusion from different directions. The agent harness is not the product. It is the thing you give away. The product is the piece of infrastructure underneath it that scales with consumption. If the harness commoditizes — and it will — what are you actually paying for? And if you are building internally, what are you actually building that has lasting value?
The pattern is familiar from previous infrastructure waves. Linux did not monetize as a kernel. It monetized as Red Hat support contracts and AWS instances. Kubernetes did not monetize as a scheduler. It monetized as managed control planes. The agent harness is following the same arc, only faster, because the labs themselves are subsidizing the giveaway.
I've argued elsewhere that the orchestration bet is the durable place to stand for the same reason — the agents themselves change every quarter, and the infrastructure that survives the swap is what compounds. If your business depends on owning the harness, you are competing against every model provider's free tier and every open-source fork. If your business depends on owning the layer that makes the harness usable in production, you have a chance.
Related Essays
Agents Are Software, and Software Needs a Factory
People talk about agent harnesses as if the harness is the interesting part. It is not. The interesting part is the factory — sandboxing, orchestration, persistence, model translation.
The Framework Cannot Be the Product
Frameworks get commoditized, forked, or absorbed by model providers. The durable revenue layer is the indispensable infrastructure piece that gets harder as the ecosystem matures.
The Harness Layer Has No Moat
The agent harness — the loop that executes — is no longer a differentiator. The opportunity lives one layer up, in the abstractions an engineer Googles at 2 a.m. when the duct tape breaks.
Key takeaways
- The agent harness is becoming a giveaway. Durable monetization shifts to the infrastructure that scales with consumption.
- LangChain monetizing through LangSmith and E2B selling the sandbox arrived at the same conclusion from different directions.
- If you are building a framework as your product, you are building a marketing asset for someone else's infrastructure.
FAQ
Why can't a framework be the product?
Frameworks have a vanishing moat as model providers ship more capabilities natively, open-source forks proliferate, and any serious engineering team can clone the surface area in a weekend. The use rate stays high, but willingness to pay collapses to zero.
What infrastructure does monetize?
The pieces that scale with consumption and are painful to migrate — sandboxing, observability, orchestration, session persistence, and model gateways. These are the layers that absorb cost as agents do more work, and they are the layers customers do not want to rebuild.