Skip to main content

Glossary L

Glossary · Cross-cutting

Lock-in

Area
Both strands

Lock-in is a customer's dependence on a supplier that makes it less attractive, or harder, to switch to a different one.

EU law takes up the subject in the Data Act, Regulation (EU) 2023/2854. Recital 88 states that unnecessarily high data egress charges (fees for moving data out of a service) and other unjustified charges unrelated to actual switching costs inhibit customers from switching. Such charges, it adds, have the potential to limit competition and cause lock-in effects for customers. Chapter VI covers switching between data processing services, meaning cloud-type services rather than bespoke software in general.

In our view, the dependency can also be technical, for instance when the source code stays with the provider, documentation is missing or data cannot be handed over in full. With bespoke software, the freedom to switch therefore depends on who owns the code and the data.

Our own rule is 'no lock-in': code, data and workflows belong to the client, documented and ready to hand over. For software we build on Symfony, the client gets full rights to the versioned source code, which is likewise documented and ready to hand over. There is no vendor lock-in, not even with us. For AI agents our principle is that the model is an interchangeable tool and the system belongs to the client. Ongoing optimisation work in e-commerce comes with no long-term commitment.

Where the term appears

Sources

  1. Regulation (EU) 2023/2854 (Data Act), recital 88 (opens in a new tab)

    Publications Office of the EU (EUR-Lex) accessed

Let's talk about your project.

If this term is on your desk right now, a conversation usually helps faster than any definition.

Search the website

Popular topics

All results