SOVEREIGN
← All guides/

Understanding GrapheneOS

What Is GrapheneOS?

A free, open-source operating system built for people who want their phone to stop working against them. Here's exactly what it is, and isn't.

GrapheneOS is a free, open-source, privacy and security-focused operating system built on the Android Open Source Project (AOSP). It's developed by the independent, non-profit GrapheneOS Project, and it's designed specifically for Google Pixel phones.

In practice, that means: the same familiar Android interface and app compatibility you already know, running on top of an operating system with no default telemetry, hardware-backed encryption, and a set of exploit protections that go meaningfully further than stock Android or iOS.

What GrapheneOS actually is

GrapheneOS starts from AOSP — the same open-source codebase Google's own Android is built from — and replaces the parts that collect data or weaken security by default. No telemetry sent to Google or anyone else. No Google Play Services installed unless you choose to add it. A hardened memory allocator, stricter kernel defaults, and a wider set of exploit mitigations than stock Android ships with.

It still runs Android apps. It still updates the bootloader and re-locks it for Verified Boot. It still passes standard Play Integrity checks when configured correctly, which is why the vast majority of everyday apps — including nearly all Australian banking apps — work normally.

  • It is not a jailbreak, a root exploit, or a hack — it's a legitimate, signed operating system that GrapheneOS ships officially for supported Pixel models
  • It is not made by Google — GrapheneOS is developed by the independent, non-profit GrapheneOS Project, unaffiliated with Google
  • It does not require root access — GrapheneOS specifically does not root the device, which is part of why it stays compatible with banking apps and Play Integrity checks
  • It is not exclusive to any single vendor — GrapheneOS is free and open-source, published for anyone to install themselves; SOVEREIGN sells the configuration, hardening, and support work around it, not the OS itself

Who uses GrapheneOS

GrapheneOS isn't built for one type of person. The user base spans people with a specific professional obligation to protect information, people with a concrete personal safety concern, and people who simply don't want to be the product.

Journalists and editors

Source protection is a legal and ethical obligation, not a preference. A device that can't be silently compromised, and that resists forensic extraction if seized, is core infrastructure for the job.

Lawyers and legal professionals

Client-attorney privilege depends on communications actually staying confidential. Family law, criminal defence, and corporate litigation all involve information that would cause real harm if exposed.

Medical and health professionals

Patient confidentiality obligations under Australian privacy law extend to the device in a clinician's pocket, not just the practice's servers.

Executives and high-net-worth individuals

A predictable, high-value target for social engineering, SIM-swap attacks, and targeted surveillance. Hardened defaults close off the easy attack paths.

Activists and political dissidents

In some contexts, device compromise carries physical risk, not just reputational or financial risk. Forensic resistance and a genuine duress option matter differently here.

Security researchers and engineers

People who understand the threat landscape professionally are consistently over-represented among GrapheneOS users — they're choosing it with full knowledge of the alternatives.

Anyone managing a sensitive personal situation

Domestic violence survivors, people going through contested divorces or custody disputes, and anyone whose location or communications being exposed would put them at risk.

Privacy-conscious everyday users

You don't need a specific threat to want fewer companies quietly building a profile of your life. Most GrapheneOS users fall into this last category — no dramatic threat model, just a preference for a phone that isn't the product.

Encryption, explained

"Encrypted" gets used loosely in marketing. Here's specifically what it means on a GrapheneOS device, and why the details matter more than the label.

  1. 01

    File-based encryption, on by default

    Every file on your device is encrypted at rest using keys derived from your passphrase and stored in hardware. This isn't optional or something you configure — GrapheneOS, like all modern Android, encrypts the entire filesystem before you ever set it up.

  2. 02

    Two states: Before First Unlock and After First Unlock

    A freshly booted or rebooted phone starts in Before First Unlock (BFU) state — fully encrypted, keys not yet loaded into memory. This is the strongest state a phone can be in if physically seized. Entering your passphrase moves it to After First Unlock (AFU), where the keys are held in memory to let the phone function normally.

  3. 03

    Hardware-backed keys via the Titan security chip

    Pixel phones include a dedicated Titan security chip, separate from the main processor, that stores your encryption keys and enforces passphrase attempt limits. Even with the device physically disassembled, the keys can't be extracted directly — they're locked to the chip and rate-limited against brute-force guessing.

  4. 04

    Verified Boot: a cryptographic chain of trust

    Every stage of startup — bootloader, kernel, OS image — is cryptographically signed and verified against known-good values before the next stage runs. If any part of the OS has been tampered with, the phone will refuse to boot normally and show a warning. This is what makes the verified boot fingerprint on our /verify page meaningful: it's proof the exact software you're running is genuine.

  5. 05

    Auto-reboot returns the phone to its strongest state

    GrapheneOS can automatically reboot after a configurable period of inactivity, returning the phone to Before First Unlock state — fully encrypted, keys unloaded — without you doing anything. A phone sitting in a drawer or left behind returns itself to maximum security on a timer.

  6. 06

    A duress password, if you need one

    GrapheneOS supports a secondary passphrase that, when entered, immediately and irreversibly wipes the device rather than unlocking it. It exists for the narrow but real set of situations where someone is compelled to unlock their phone under duress.

How it differs from a stock Pixel

A Pixel running stock Android — Google calls it Pixel OS — sends usage diagnostics, app data, and behavioural signals back to Google by default, and ships with Google Play Services running with elevated system privileges it can't be fully sandboxed away from. GrapheneOS replaces that base entirely: no telemetry, no elevated Google Play access unless you explicitly install it in a sandbox, and a substantially expanded set of exploit protections layered on top of the same hardware.

You're not choosing between "Android" and "something else" — GrapheneOS is Android, in the technical sense. You're choosing which version of Android: Google's, tuned for data collection and services, or GrapheneOS, tuned for not collecting anything by default and resisting compromise.

Where SOVEREIGN fits in

GrapheneOS is free, and technically capable people install it themselves in under an hour. SOVEREIGN exists for everyone else — and for anyone who'd rather have a device that arrives already configured, hardened to a documented profile, attested with a published fingerprint, and backed by support if something goes wrong.

We don't modify GrapheneOS. We install the official, unmodified release and apply configuration on top: a hardening profile, a curated set of privacy tools, and — depending on your package — Sandboxed Google Play set up and tested. You can verify none of that touches the OS itself by checking the boot fingerprint against the GrapheneOS Project's own published values.

Frequently asked questions

What is GrapheneOS?
GrapheneOS is a free, open-source, privacy and security-focused operating system built on the Android Open Source Project (AOSP), designed specifically for Google Pixel phones. It's developed by the independent, non-profit GrapheneOS Project — not by Google — and is not affiliated with or endorsed by Google in any way.
Is GrapheneOS free?
Yes. GrapheneOS itself costs nothing and is fully open-source — anyone can download and install it themselves. SOVEREIGN charges for the device, professional configuration, hardening, attestation, and ongoing support, not for the operating system.
Which phones support GrapheneOS?
As of July 2026, GrapheneOS officially supports Google Pixel devices only, because Pixel has been the only phone line giving third-party operating systems the same hardware-backed security guarantees as the stock OS — including a re-lockable bootloader and full Verified Boot support. This is a deliberate scope limitation by the GrapheneOS Project, not a gap. That is changing: GrapheneOS announced a partnership with Motorola at MWC 2026, with support expected in 2027, which would make Motorola the first major Android manufacturer outside Google to officially support it.
Do I lose access to the Google Play Store?
No. GrapheneOS ships without Google Play Services installed by default, as a privacy choice — but Sandboxed Google Play is available as an optional install from the built-in Apps repository. It runs as a normal sandboxed app with no special system privileges, and most apps — including nearly all Australian banking apps — work through it normally.
Is GrapheneOS legal to use in Australia?
Yes. Installing an alternative operating system on hardware you own is legal in Australia. GrapheneOS doesn't circumvent any access controls Google didn't explicitly design for third-party OS installation — Pixel's bootloader unlock and re-lock process exists precisely to support this.
How is GrapheneOS different from a factory reset or a VPN?
A factory reset clears your data but leaves the same operating system, with the same telemetry and default permissions, in place. A VPN protects your network traffic but does nothing about what's installed on the device itself, what permissions apps have, or how resistant the phone is to physical compromise. GrapheneOS replaces the operating system itself with a hardened alternative — it addresses a different, deeper layer than either of those tools.

Want to see how it compares to other options?

Read our honest comparisons against CalyxOS and LineageOS, or explore what a configured SOVEREIGN device includes.

Last updated: July 2026. GrapheneOS is a trademark of the GrapheneOS Project. SOVEREIGN is not affiliated with or endorsed by the GrapheneOS Project.