Vendor lock-in

Vendor lock-in describes a situation where switching away from a vendor's product becomes costly or difficult, not because the product is still the best option, but because of proprietary data formats, deep integrations, retraining costs, or contractual terms that make leaving expensive. In analytics, this commonly shows up as data stored in a proprietary format, custom logic written in a vendor-specific query language, or pipelines that depend on a platform's particular APIs.

Lock-in risk is not binary: a fully proprietary, closed-format platform carries more risk than one built on open standards and portable formats, even from a single vendor, and an open-core model vendor sits somewhere between the two, since its core is portable but its advanced features may not be. This differs from ordinary switching cost, which exists to some degree with any tool change; lock-in specifically refers to switching costs a vendor has structural or contractual incentive to keep high.

Vendor lock-in matters because it shifts negotiating leverage to the vendor over time and can trap an organization on an aging platform, alongside concerns like data sovereignty when data is bound to a specific jurisdiction. Teams manage the risk by favoring open data formats and standard query interfaces, running a proof of concept before committing, and asking about data export and portability explicitly during a request for proposal process, rather than discovering the cost of leaving only when they try to.