Glossary · Definition
Vendor lock-in
Vendor lock-in is when switching away from a supplier would be so costly or risky that you effectively can’t — because they control your code, infrastructure, data or knowledge.
By Nythrex EngineeringUpdated 1 min read
In plain words
In software outsourcing, lock-in usually isn’t in the contract — it’s in the details: a repository in the vendor’s account, production in their cloud, a domain registered to their employee, no documentation. Most of it can be fixed administratively, before you need to.
When it matters to you
- Any outsourced development
- Choosing AI platforms and proprietary tools
- Before renegotiating with a vendor
Common pitfalls
- Assuming the contract alone protects you
- Forgetting AI assets like prompts and evaluation data
- Only checking when the relationship is already in trouble
Keep reading
Free toolVendor lock-in testTwelve questions about code, cloud, access, contracts and docs reveal how locked in you are to your development vendor — with a prioritised fix list.GuideWho really owns your code?Paying for software doesn’t make it yours. The clauses that decide code ownership: IP assignment, background IP, open source, AI assets, exit terms.GuideSwitching vendors without a rewriteHow to change development vendors safely: secure assets, plan the handover, transfer knowledge and keep shipping — with a complete handover checklist.
Want a second opinion on your project?
Tell us what you’re building and where you’re stuck. We’ll reply within one business day with the most practical next step — even if that step isn’t us.