Vendor Lock-In
Definition
Vendor lock-in is the degree to which leaving a provider is expensive, slow or impossible. It comes from dependencies that exist only inside one product: a build pipeline nobody else runs, a page builder whose output is not portable HTML, a database reachable only through that vendor's API, or a contract with an exit penalty. A plain static site is close to the opposite case, because the files are the site — the same folder of HTML, CSS, images and PDFs works on any host that can serve files over HTTP. What actually ties a published site to a provider is almost never the content. It is the address people already have, the redirect rules accumulated over years, the visitor history that cannot be re-created, and any feature the pages depend on at request time, such as an edge function or an access rule.
Why It Matters
Lock-in only becomes visible at the moment you want to leave, which is usually the moment you can least absorb disruption — a price rise, an acquisition, a policy change, a shutdown. The question worth asking up front is blunt: if this provider disappeared tomorrow, what would you not get back? For a folder of static files on a custom domain the honest answer is very little, because you point the DNS elsewhere and re-upload. For a site whose forms, redirects and search all run on one platform, the answer is several weeks of rebuilding. Knowing which of those you are is worth more than trying to avoid every dependency.
How It Works
Lock-in accumulates in four places, roughly in order of how hard each is to unwind. The address comes first: if your site lives on a subdomain of the provider, every printed card, QR code and inbound link points at them and none of it can move, which is why a domain registered in your own name is the single most effective precaution. Redirects are second, because they live in platform configuration rather than in your files, and a map built over three years is tedious to reconstruct from nothing. Visitor history is third, since view and download counts are rarely offered in a form another tool will accept, so the practical move is a periodic data export of the figures you actually use. Fourth and usually smallest are runtime features — password protection, form capture, custom headers — each of which has an equivalent elsewhere but has to be set up again by hand.
Real-World Example
A startup hosts its investor materials at northgate-docs.99helpers.site, on a domain they registered themselves and pointed at the service with a CNAME record. Two years on they decide to fold the documents into the main company site. The move takes an afternoon: download the files, upload them to the new host, change one DNS record, carry the redirect list across. What does not travel with them is three years of per-file download counts, which is the one thing they would have kept had they saved a monthly summary all along.
Common Mistakes
- ✕Treating a provider subdomain as permanent and printing it on physical material — the address is the part you cannot take with you, and a domain you own costs a fraction of a reprint
- ✕Letting a provider register the domain on your behalf without checking who the registrant of record is — transferring a domain you do not technically own is a slower and different problem
- ✕Judging portability by the content alone — the files move in minutes, while the redirects and the history are the parts that take weeks or never arrive
Related Terms
Data Export
Getting your content, settings and statistics out of a service in a form something else can read. It is the practical test of how portable an account really is.
Site Migration
Moving a site to a new host, a new domain, a new URL structure, or some combination of the three. The files are the easy part; the addresses are where the damage happens.
Domain Transfer
Moving a domain's registration from one registrar to another, while keeping the name itself. It is a deliberate, slow process with an authorisation code, a lock and several waiting periods built in to stop domains being stolen.
Custom Domain
A custom domain is a name you own, pointed at content somebody else hosts, so visitors see files.acme.com instead of the provider's address. You keep the registration; the provider keeps the servers.
Static Site
A static site is a website made of finished files — HTML, CSS, JavaScript, images — that are sent to the browser exactly as they are stored. Nothing is assembled on the server when a visitor arrives.
Put a file online in seconds
Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.
Host a file free →