What is vendor lock-in?
DefinitionVendor lock-in
Vendor lock-in is a dependency on one provider that makes switching costly or impractical, because of proprietary data formats, closed APIs, contract terms, integrations or skills that only work with that provider.
At PilaeEvery app in the Pilae catalogue is open source or source-available.
On this page (3)
What vendor lock-in means
Vendor lock-in is the point where leaving a provider costs more than staying, even when staying is no longer what you want. It builds up in layers.
Where lock-in builds up
- Data: sits in a format only the vendor reads well.
- Workflows: depend on features no other product has.
- Integrations: call a closed API.
- Staff: know one tool.
- Contract: runs for years and renews automatically.
None of this is unusual, and some dependency is a fair price for a good product. The problem starts when the vendor can change prices, terms, features or data location and you have no practical way to respond.
Why it matters when choosing where software runs
Lock-in weakens every other control. A data residency clause helps little if the vendor can change it at renewal and you cannot move. A sub-processor objection right means little if objecting leaves you without a service. Licensing changes in widely used platforms, such as the move to subscription bundles after Broadcom acquired VMware in 2023, have shown how quickly the cost of staying can change.
When you compare options, ask three questions. Can we export all our data in open formats, on our own schedule? Could someone other than this vendor run the same software? What would it take, in weeks and people, to leave?
How Pilae handles it
Every app in the Pilae catalogue is open source or source-available. Your data lives in standard databases and open formats, on machines in the location you choose. If you leave Pilae, another operator or your own team can run the same apps with the same data, and every plan includes a written exit strategy that sets out how.
To reduce lock-in you already have, we move you off SaaS products onto apps you control, plan VMware exits, and build exit plans for the providers you keep. Fixed-price migration moves the data, users and integrations and checks the result against the source.
Talk to an engineer about your exit plan
Thirty minutes with an engineer, a written plan and a fixed price for the first workload.
- Go deeperLeave a SaaSReplace a US SaaS with an open-source app you own: we migrate the data and workflows, then run it for you under an SLA.
- CompareWhat is an exit strategy?An exit strategy is a documented, tested plan for leaving a software or cloud provider: where the service moves, how the data comes out, who does what and how long it takes, so that leaving is possible without disrupting the business.
- CheckExit planA documented, tested fallback for each critical SaaS and cloud dependency, supporting DORA exit strategies and FINMA outsourcing rules.
