Nythrex

Free tool · Two-minute test

Are you hostage to your software vendor?

Twelve questions about code, cloud, access, contracts and documentation. At the end you’ll see your lock-in score and exactly what to fix first — whoever builds your product.

Vendor lock-in test

1 of 12

Is the Git repository in an organisation account your company owns?

Why lock-in is the risk to fix first

Most project problems can be fixed with time and money — as long as you control your product. Lock-in removes that option: if the code, cloud and knowledge sit with the vendor, every negotiation is on their terms. The good news is that most fixes are administrative and can be done in days: moving a repository, transferring a subscription, rotating credentials.

Next steps: read Who really owns your code? for the contract side, and 13 red flags your vendor is hiding problems for the delivery side.

Frequently asked questions

Keep reading

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.Guide13 red flags your vendor is hiding problemsVague reports, shifting dates, no access to code: 13 signs your outsourced project is in trouble — and what to ask or do about each this week.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.ServiceProject rescueVendor gone, deadline slipping, code nobody understands? We take over troubled software and AI projects: fast audit, stabilisation, a plan you can trust.

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.

Start a project