/e/OS or GrapheneOS: which de-Googled Android should you choose?

Changing your phone’s operating system is the most radical step in the journey. The browser, the maps, the photos: everything else gets replaced app by app. Here, you remove Google from the foundations. Two serious projects dominate the field, with two philosophies: /e/OS wants to make de-Googling accessible, GrapheneOS aims for security without compromise.

The match in one table

Criterion	/e/OS (Murena)	GrapheneOS
Price	Free; Murena phones sold ready to use	Free; Google Pixel smartphone required
Philosophy	De-Google without changing your habits	Reference-grade security (hardened sandboxing)
Compatible devices	Certain existing models, plus the Murena range	Google Pixel only
Google and banking apps	Some Google-dependent apps don’t work	Google Play usable in an isolated sandbox
Source code	Open	Open
Installation	Ready to use (Murena), otherwise technical with bootloader unlocking	Simplified web installer, but still a technical process

What /e/OS does better

Accessibility, and it’s decisive. /e/OS looks like the Android you know: same gestures, same landmarks, with a replacement ecosystem already built in for email, cloud storage and the app store. You don’t assemble your phone piece by piece, it arrives furnished.

The argument that changes everything for non-tinkerers: Murena phones, sold with /e/OS preinstalled. You unbox, you turn it on, it’s de-Googled. No command line, no bootloader. For a first phone without Google, it’s the best entry point, and the one I recommend in the book. Installing it on an existing device remains possible on certain models, but that becomes a technical affair again.

What GrapheneOS does better

Security, no contest. GrapheneOS is the reference in the field: hardened sandboxing, frequent and fast updates, a level of hardening praised by specialists. Its approach to Google apps is elegant, too: rather than banning them, it locks them in an isolated sandbox, where they run like ordinary apps, without privileges. In practice, that helps a lot with temperamental apps.

One irony deserves its own line: this system designed to escape Google requires a phone… made by Google. Pixels are chosen for their security chips, but you have to accept buying one. Add an installation that stays technical despite the web installer, and a smaller community than /e/OS’s: it’s a tool for advanced users.

The real question: your everyday apps

Before picking a side, take inventory. Bank, health insurance, transit pass: some apps refuse to run outside a Google-certified Android. /e/OS says so clearly for the most Google-dependent apps, and GrapheneOS answers with its sandbox, without a universal guarantee. Check the compatibility of your two or three vital apps before buying anything. That test, not the spec sheet, is what should decide.

Verdict

Choose /e/OS if you want a Google-free phone that works like before, especially via a ready-to-use Murena. It’s the best choice for a successful exit from Android without giving up your evenings.

Choose GrapheneOS if security is your first criterion, you’re comfortable with the technical side and a Pixel poses no problem of principle for you. On its own turf, it’s the reference.

The detailed profiles: /e/OS (Murena) and GrapheneOS, with the overview on the mobile OS page. And if the phone is your last step, the big picture is on leaving Google.