Skip to content

Vendor dependency and freedom of choice

Dependencies grow around files, accounts and established routines. What matters is whether changing provider remains a practical option.

When a useful tool becomes a lasting dependency

A tool is chosen because it solves a problem well. Materials are then created in it, other services are connected and people organise their work around it. Each connection can add to the effort of changing provider. This dependency is known as vendor lock-in. Licensing models matter as well. When prices or terms change, an alternative is only practical if data and workflows can move. A provider’s country of origin alone does not answer that question. Understandable terms and usable switching options do.

Testing a change before it becomes urgent

Open formats and documented interfaces make alternatives easier to explore. A trial with selected materials shows what transfers and which permissions or functions need to be set up again. Open code does not remove every dependency either. If operational knowledge rests with one person or no support is available, the organisation’s options remain limited. Documentation, available expertise and a tested export route turn a theoretical alternative into a realistic one.

Sources and further information