GrapheneOS vs LineageOS
Two well-established open-source Android projects with genuinely different goals. Here's the honest comparison, and why it matters which one you pick.
LineageOS is the largest and longest-running custom Android ROM project, supporting hundreds of devices across dozens of manufacturers. GrapheneOS supports exactly one device line — Google Pixel. That single difference tells you almost everything about how the two projects' priorities diverge.
LineageOS exists to keep phones useful — including older or officially unsupported ones — with a modern, de-bloated Android experience. GrapheneOS exists to make one specific class of hardware as secure as it can possibly be. Both are legitimate goals. They lead to very different products.
The core difference: Verified Boot
This is the single most important technical distinction, and it's worth understanding clearly. Verified Boot is a cryptographic chain of trust — every stage of startup is signed and checked against known-good values before the next stage runs, so the phone can prove its software hasn't been tampered with.
GrapheneOS re-locks the Pixel bootloader after installation with its own signing keys, so Verified Boot stays fully active — the same protection a factory phone has, just verifying different, hardened software. Most LineageOS installations, across most supported devices, leave the bootloader unlocked permanently, because most non-Pixel devices don't support relocking with custom keys the way Pixel does. That means Verified Boot is effectively off on most LineageOS phones — a meaningful security regression, not a cosmetic one.
Where else they differ
Root access. LineageOS optionally supports root, and a substantial part of its community uses it for deeper customisation. GrapheneOS deliberately excludes root entirely — root access undermines the sandboxing and permission model the entire security design depends on.
Exploit hardening. GrapheneOS implements hardened_malloc, a hardened kernel configuration, and an expanded set of exploit mitigations well beyond AOSP defaults. LineageOS largely inherits AOSP's standard hardening level — solid, but not the project's focus.
Device breadth vs. depth. LineageOS's hundreds of supported devices are maintained by a distributed community of per-device maintainers, so update speed and quality vary significantly device to device. GrapheneOS's narrow, deliberate scope — Pixel only — lets a smaller, focused team ship security updates fast and consistently, typically within days of upstream releases.
Duress and physical-security features. GrapheneOS includes a duress password and configurable auto-reboot to Before-First-Unlock state. LineageOS doesn't offer equivalents.
Side by side
LineageOS characteristics vary by device — the table reflects the typical, most common case across supported hardware.
| Feature | GrapheneOS | LineageOS |
|---|---|---|
| Primary goal | Security and privacy hardening | Customisation and extending device lifespan |
| Supported devices | Google Pixel only (Motorola support announced for 2027) | Hundreds of devices across many manufacturers |
| Verified Boot after install | Yes — bootloader re-locked, full chain of trust restored | Not supported on most devices — bootloader typically stays unlocked |
| Exploit hardening | Extensive — hardened_malloc, hardened kernel, expanded mitigations | Standard AOSP-level hardening; not a primary project focus |
| Google Play Services | Not installed by default; optional Sandboxed Google Play | Not included; LineageOS for microG variant available separately |
| Root access | Not supported — deliberately excluded | Optional, user-enabled (widely used by the LineageOS community) |
| Per-app network/sensor permissions | Yes, fine-grained | Standard Android permission model |
| Duress password | Yes | No |
| Auto-reboot | Yes (configurable) | No |
| Update cadence | Fast — typically days after AOSP/Pixel security releases | Varies significantly by device — some devices lag well behind |
| Who maintains it | GrapheneOS Project — small, security-focused team | Large open community with per-device maintainers of varying activity |
| Typical use case | Maximum hardening on current-generation Pixel hardware | Reviving older or unsupported phones with a modern Android build |
Comparison reflects typical configurations as of July 2026. LineageOS behaviour varies by specific device — verify specifics for your hardware.
Who should choose which
Choose GrapheneOS if security and privacy hardening is the actual goal, if you own a Pixel, or if maintaining Verified Boot matters to your threat model. For anyone SOVEREIGN typically works with — journalists, legal and medical professionals, executives, or anyone with a genuine reason to want a forensic-resistant device — GrapheneOS is the appropriate choice, not LineageOS.
Choose LineageOS if you have an older or officially unsupported device you want to keep using with modern Android, you want root access for deep customisation, or your priority is de-bloating and control rather than maximum security hardening. It's the right tool for that job — just a different job.
Frequently asked questions
- Is LineageOS as secure as GrapheneOS?
- No, and this isn't really a close call. LineageOS's goal is customisation and extending the useful life of a wide range of devices — security hardening isn't its primary focus. Most significantly, most LineageOS installs don't support re-locking the bootloader, which means Verified Boot — the cryptographic guarantee that the OS hasn't been tampered with — isn't active. GrapheneOS is purpose-built around security hardening and maintains a full chain of trust after install.
- Why does LineageOS support so many more devices than GrapheneOS?
- Different goals. LineageOS's mission includes keeping older or otherwise abandoned devices useful, which means supporting hardware across many manufacturers with varying capabilities. GrapheneOS deliberately limits itself to Google Pixel because Pixel is the only device line that provides the specific hardware security guarantees — a re-lockable bootloader with full Verified Boot support — that GrapheneOS's threat model requires. Broader support and stronger security guarantees are, in practice, a trade-off.
- Can I root LineageOS but not GrapheneOS?
- Yes. LineageOS supports optional root access, which a meaningful part of its community uses. GrapheneOS deliberately does not support root, because root access fundamentally weakens the security model it's built around — an app or attacker with root can bypass the sandboxing and permission controls that make the hardening meaningful.
- Is LineageOS a bad choice?
- Not at all, for what it's designed to do. If you have an older phone that's fallen out of manufacturer support and you want a modern, de-bloated Android build to keep it useful, LineageOS is a well-established, credible option with a large community. It's a poor fit specifically if your priority is maximum security hardening — that's a different project with a different goal.
- Does LineageOS have a privacy-focused option?
- Yes — LineageOS for microG is a community-maintained variant that includes microG (a reimplementation of some Google APIs) instead of Google Play Services, aimed at users who want more privacy than stock LineageOS provides without full Google integration. It still doesn't address the bootloader re-locking gap that separates LineageOS from GrapheneOS on the security side.
Need maximum hardening?
Every SOVEREIGN device ships with official, unmodified GrapheneOS on a Pixel, hardened and attested before it leaves us.
Last updated: July 2026. GrapheneOS is a trademark of the GrapheneOS Project. LineageOS is a trademark of the LineageOS project. SOVEREIGN is not affiliated with or endorsed by either project.