Vendor lock-in
Vendor lock-in is when moving away from a service is so costly or difficult that you are effectively stuck with it, along with its prices and decisions.
On the web, lock-in usually comes from three places: content you cannot export in a usable format, a site that only runs on one provider's platform, and accounts (domain, hosting, analytics) that are in someone else's name.
Lock-in isn't automatically bad; every hosted service involves some. The question is whether you know the exit cost before you choose, and whether it is reasonable.
In Framer
Framer sites are hosted by Framer, and the design cannot be exported as a standalone codebase. CMS content can be exported as CSV. For many teams this is a fair trade for speed and simplicity.
How Regular approaches it
Standard is designed to have a documented exit: the code is in the client's GitHub, hosting and data in the client's Cloudflare account, the CMS is Open source, and content is structured data that can be exported. We would rather keep clients because they want to stay.
Sources and further reading
- Vendor lock-in, Wikipediaen.wikipedia.org