Vendor Lock-In
A dependency on a single vendor's platform that makes switching to an alternative costly or impractical.
Definition
Vendor lock-in describes a situation where a customer becomes dependent on a particular vendor's products or services to the point that switching to a competitor, or to an in house alternative, would be expensive, disruptive, or technically difficult. Lock-in can arise from proprietary data formats, closed APIs, workflows built around vendor specific features, or simply the operational cost of migrating large amounts of data and configuration out of a system once it is deeply embedded in day to day operations.
How it works
Lock-in typically builds up gradually rather than being imposed all at once. An organization adopts a platform for its convenience, integrates it into more processes over time, and accumulates data, configuration, and institutional knowledge that only exist inside that platform. If the vendor's pricing changes, the service becomes unreliable, or the organization's needs outgrow what the vendor offers, the accumulated switching cost, not the current product quality, becomes the reason to stay. Open standards, data export capabilities, and self hostable software reduce lock-in by keeping an exit path available, even if it is never used.
Why it matters for AI agent systems
An AI agent platform tends to accumulate exactly the kind of assets that create lock-in: agent configurations, prompt and workflow history, connected credentials, and logs of what agents did over time. If that platform is a closed, hosted service, an organization's agents, and the record of their actions, live entirely on infrastructure it does not control, which raises both a switching cost problem and a data control problem if the vendor changes terms, pricing, or availability. Self hosted, open source infrastructure addresses this directly by letting an organization run the platform on its own servers and keep its agent configurations, credentials, and data under its own control. Agenhood is built as self hosted, MIT licensed infrastructure specifically for this reason: an organization can operate its own fleet of agents without depending on a third party vendor for continued access to its own workflows and history.
Related concepts
- Multi-tenancy: relevant because a hosted multi-tenant service is where lock-in risk concentrates most.
- Encrypted credential storage: matters for lock-in because credentials should remain under the organization's control regardless of platform.