What Is Ecosystem Lock-In?

Why leaving Big Tech is harder than canceling a subscription — and how to think about it.

Not all lock-in is the same

"Lock-in" gets used loosely to mean "hard to leave." But the reasons it's hard to leave are very different across companies, and understanding which type of lock-in you're facing tells you what kind of migration work is ahead of you.

There are three types:

Type 1: Content lock-in (DRM)

You paid for something, but you don't own it. Your Kindle books, your iTunes movies, your Audible audiobooks, your Apple Books purchases — these are licenses, not property. They are encrypted with DRM (Digital Rights Management) and can only be accessed through the company's software on the company's approved devices.

If you leave the ecosystem and close your account, the content is gone. There is no legal way to export it in a format that works elsewhere. The button that said "Buy" meant "License under our terms."

Who does this: Amazon (Kindle, Audible, Prime Video), Apple (iTunes movies, Apple Books, App Store), Google (some Play Books, Play Movies), Microsoft (Xbox games, Microsoft Store movies).

The structural solution: Stop buying DRM-locked content. Buy DRM-free ebooks from Kobo, Smashwords, or publishers directly. Buy audiobooks from Libro.fm. Buy movies on physical media or through Movies Anywhere-linked storefronts. Buy PC games from GOG.com. Going forward, you own what you buy.

Type 2: Data lock-in (surveillance)

You didn't buy anything — the product was you. Google has fifteen years of your search history, location history, email content, YouTube watch history, and voice commands. Meta has your social graph, your messages, your behavioral profile. These companies don't lock up your content — they lock up their knowledge of you.

You can export your files in an afternoon. Your data shadow is not in the export. Google's model of your behavior — the advertising profile, the predictions, the inferences drawn from a decade of queries — is not a file you can download and take with you. It remains on Google's servers whether or not you've exported your photos.

Who does this: Google (the most extensive), Meta (social and behavioral data), Amazon (purchase and voice data), Microsoft (enterprise and telemetry data).

The structural solution: Stop the flow, then drain the reservoir. Replace the services that collect the most data per day first (browser, search engine, maps, Android). Then delete the historical data that's already been collected. The Google guide covers this in the Cutting the Pipeline five-phase plan.

Type 3: Social lock-in (network effects)

Your family is on Facebook. Your friends are on Instagram. Your group chat is on WhatsApp. The restaurant you like posts specials on Instagram stories. This isn't technical lock-in at all — it's social infrastructure that happens to run on private platforms.

You can export all your photos and posts from Meta's platforms in an afternoon. What you can't export is your social graph. The connections, the groups, the communities. These exist on Facebook because your people are on Facebook. No technical solution changes that.

Who does this: Meta (the purest example), Apple (iMessage creates a social pressure dynamic unique to the US), to a lesser extent Google (Gmail is where people expect to reach you).

The structural solution: Collect contact information (phone numbers, email addresses) before leaving. Move to platforms where relationships can exist independent of any single company's servers — direct text, email, Signal. Accept that some connections will fade. This is the cost of leaving, and it's worth being honest about.

Why this matters

Knowing which type of lock-in you're facing tells you where to focus your energy:

Most people face all three, with different weights for different companies. That's why this site is organized by company rather than by type of content — because leaving Amazon is mostly a content-lock-in problem, leaving Google is mostly a data-surveillance problem, and leaving Meta is mostly a social-lock-in problem.

Where to start