CalyxOS vs GrapheneOS — which privacy operating system suits you?

CalyxOS and GrapheneOS are the two best-known privacy versions of Android. This guide compares their security, app compatibility and supported phones, so you can pick the one that fits.

CalyxOS vs GrapheneOS — which privacy operating system suits you?

CalyxOS vs GrapheneOS

CalyxOS and GrapheneOS are the two best-known privacy versions of Android. This guide compares their security, app compatibility and supported phones, so you can pick the one that fits.

Who this guide is for. This guide is for people already considering a privacy-focused Android OS and trying to decide which one actually fits their risk tolerance and tolerance for friction.

It fits especially:

  • readers deciding between GrapheneOS and CalyxOS on supported hardware
  • people who want a clearer answer than “both are privacy phones”
  • users who need to balance security depth against daily convenience

What you gain, and what it costs

If you compare these properly, you gain:

  • a clearer match between your real priorities and the OS you install
  • a better understanding of why GrapheneOS and CalyxOS are not interchangeable
  • fewer chances of choosing an OS you will later abandon because it does not fit your habits

What it costs:

  • accepting that there is no one-size-fits-all winner
  • some honest self-assessment about how much friction you will actually maintain
  • the reality that the strongest technical option is not automatically the best personal fit

When this is overkill

If you are not yet sure whether you want a privacy-focused Android OS at all, do not start here. First decide whether changing phones or operating systems is really on the table for you.

This comparison matters once you already know that a privacy OS is relevant to your situation and you are choosing between two serious options.

GrapheneOS and CalyxOS are both built on Android’s open source code and focused on privacy, but they make different choices. In our reading, GrapheneOS puts security hardening first, and CalyxOS puts ease of use first, with privacy-friendly defaults.

This is not a moral ranking. The right choice depends on your risk profile, your device options, and how much extra friction you are actually willing to maintain.


The core difference

GrapheneOS: Hardening comes first: less attack surface, more exploit mitigations and stronger sandboxing on top of AOSP. It ships no Google apps or services. If you want Google Play, you install it yourself as ordinary sandboxed apps with no special privileges.

CalyxOS: User-friendly privacy Android. It comes with microG (an optional, open-source replacement for part of Google Play Services), F-Droid and Aurora Store, and handles location without Google. Easier to start with, but we found no comparable list of extra hardening in its documentation.


Comparison table

GrapheneOS CalyxOS
Security focus Extra hardening on top of Android Privacy defaults; no comparable extra hardening documented
Ease of use Medium Good
Google Services None included; Google Play optional in the normal app sandbox microG (optional, partial replacement)
App compatibility “Near complete” with sandboxed Google Play, says GrapheneOS “Most apps” with microG, says CalyxOS
Supported hardware Pixel 6 up to Pixel 10a; no Pixel 11 yet Pixel 6 to 9 series and Pixel 10a (not Pixel 10 or 10 Pro, no Pixel 11), older Pixels, Fairphone, Motorola, SHIFTphone 8
Security update speed Full November 2026 patch level in build 2026110200 Aims for the same week for the open source parts; proprietary parts can lag
Android 17 June 2026 October 2026
Verified Boot Yes Yes, with the bootloader relocked
Open-source The OS yes, device firmware no The OS yes, device firmware no
Our pick for Higher-risk users Users who want an easier switch

Ease of use and “our pick” are our own assessment, not measurements. The update and Android 17 rows are from each project’s release notes, read on 4 November 2026.


GrapheneOS in detail

GrapheneOS is developed as a non-profit open source project, founded in 2014. The GrapheneOS Foundation, a non-profit created in Canada in March 2023, handles donations, and developers are hired as remote contractors. The project also partners with companies, Motorola among them.

What GrapheneOS adds to AOSP (Android Open Source Project):

  • Hardened malloc: Replacement memory allocator with extra security checks
  • Vanadium: Hardened variant of Chromium, used as both the default browser and the WebView
  • Exploit mitigations: Extra protection against memory corruption, the most common class of serious bugs
  • Network permission: A per-app toggle that blocks an app’s network access, on top of other permission changes
  • Sandboxed Google Play: Google Play Services run in an isolated sandbox without special system privileges
  • Attack surface reduction: Optional features such as NFC, Bluetooth and UWB are off by default, and new USB connections are blocked while the phone is locked

Sandboxed Google Play: This is the key difference. On standard Android, Google Play Services bypasses the app sandbox with highly privileged access. On GrapheneOS it runs as a regular app without extra rights. GrapheneOS calls compatibility with apps that depend on Google Play “near complete”, and only a small set of privileged functions is missing.

Hardware requirements: Pixel phones only, today. Production support runs from the Pixel 6 to the Pixel 10a; GrapheneOS recommends buying a Pixel 8 or newer, and minimum support for the Pixel 6 and 6 Pro ended in October 2026. The Pixel 11 series has no builds as of 4 November 2026: GrapheneOS expects to be able to support it once Android 17 QPR2, due in December by its account, ships the firmware it needs. Its requirements include a secure element and full hardware security with an alternate OS; current Pixels use the Titan M2 chip (Pixel 11: Titan M3). Motorola announced a partnership with the GrapheneOS Foundation on 2 March 2026, but GrapheneOS says none of Motorola’s existing phones meet its requirements. The first supported device is planned for 2027, as the successor to the Motorola Signature (2026). So today, CalyxOS’s broader device list is the practical difference.


CalyxOS in detail

CalyxOS is developed by an international team of volunteers and staff at the Calyx Institute, a 501(c)(3) non-profit in New York, and most of its development is funded by member donations. The project says it is designed for everyone and also for human rights defenders, journalists, lawyers and activists; our pick above for higher-risk users is our own judgement on hardening and on the hiatus below.

Note: CalyxOS stopped for most of a year. In August 2025 the project said founder Nicholas Merrill and tech lead Chirayu Desai had left, that security updates would pause while it replaced its signing keys, and that people running CalyxOS should uninstall it. Regular releases came back on 1 July 2026 with 7.2.2.0; anyone on an older build has to do a clean install. Builds are now signed with a hardware security module, in a setup the project says Trail of Bits audited. The Android 17 rollout began on 1 October 2026, and 8.0.4.50 reached the Stable channel for all supported devices on 2 November 2026. The recovery is recent, so check calyxos.org/news for the current release status before installing.

What CalyxOS offers:

  • microG: Open-source replacement for part of Google Play Services, with four modes from off to signed in with a Google account. The default sends push notifications through Google’s servers, not tied to an account. To work, microG needs signature spoofing; CalyxOS says it limits that to microG alone. GrapheneOS rules out including microG.
  • F-Droid and Aurora Store: F-Droid Basic is the default app store, installed during setup; Aurora Store gives access to Google Play’s catalogue without a Google account
  • Location without Google: microG works out your location from locally stored Wi-Fi and cell tower data, and CalyxOS offers Positon, BeaconDB or no online service
  • Datura: A firewall that sets network access per app. GrapheneOS uses its Network permission instead, which it says also covers what a firewall can miss
  • Seedvault: Encrypted backup to USB or to WebDAV storage such as Nextcloud (GrapheneOS includes Seedvault too)

microG vs Sandboxed Google Play:

microG (CalyxOS) Sandboxed Google Play (GrapheneOS)
Compatibility Varies (see Plexus) “Near complete”, says GrapheneOS
What Google sees IP address and device model at registration; push notifications; no account unless you add one What any app can see; Play services runs with Google’s own code, and you can leave it out
Privileges Signature spoofing, limited to microG No special access
Transparency Open-source Closed-source, but isolated
Push notifications Through microG, via Google’s servers Through Play services, in the app sandbox

CalyxOS says most apps run fine with microG but calls it “not yet a mature replacement” for Play Services. Plexus collects community ratings of how apps work on de-Googled phones.


Is Android still open source? What changed in 2026

Both ROMs are built from AOSP, so readers ask whether Google is closing it. As of 4 November 2026, Google’s own AOSP pages show a change in timing, not a closing:

  • What Google says: “Effective in 2026 … we will publish source code to AOSP in Q2 and Q4”, tied to its “trunk stable” development model. Its pages list an Android 17 tag (android-17.0.0_r1) and a manifest (android-latest-release) that always points to the newest release, and the site was still being updated in October 2026. We found no statement about closing the source.
  • What it changes for custom ROMs: without early access, a ROM can only start porting once the source is public. CalyxOS says it gets no early access to monthly patches, and that because Google stopped publishing AOSP source for the QPR1 and QPR3 releases, it can’t update Pixel firmware and other proprietary parts on time for builds on those branches. GrapheneOS said in September 2025 that it has early access to the Android Security Bulletin patches and was seeking it for quarterly and yearly releases, because porting without it is “an immense workload with a lot of time pressure”. In September 2026 its build 2026092500 moved Pixel firmware and drivers to Android 17 QPR1. It also criticised Google for making security patches “almost entirely quarterly” with 3 to 4 months of early access for phone makers; that is GrapheneOS’s view, not a neutral finding.
  • What it means for you: nothing to do today. GrapheneOS’s FAQ lists complete monthly security patches for firmware and drivers as a requirement for future devices. What to watch is the gap between a new Android release and your ROM’s release; check the ROM’s release page before you rely on it.

When to choose GrapheneOS?

GrapheneOS is better if:

  • Security is an absolute priority (journalist, activist, lawyer, high-risk individuals)
  • You’re willing to learn a bit more about app installation and configuration
  • You want regular Android apps, including ones that need Google Play, to stay inside the normal app sandbox
  • You have or can buy a supported Pixel, ideally a Pixel 8 or newer

Maintenance burden: medium. This choice only pays off if you genuinely keep carrying that extra learning curve.

See also the GrapheneOS and Pixel 9 review for installation instructions.


When to choose CalyxOS?

CalyxOS is better if:

  • You want to move from standard Android to privacy Android without too steep a learning curve
  • The apps you depend on work with microG (check Plexus)
  • You have a Fairphone 5 or Fairphone (Gen. 6) (CalyxOS supports them, and the Fairphone 4 until December 2026; GrapheneOS supports none of them)
  • Privacy protection without perfect security is sufficient

Maintenance burden: medium, but usually lower-friction than GrapheneOS for readers who mainly want a manageable switch.


Other options

LineageOS: A much longer device list, and CalyxOS itself draws heavily on its code. In our assessment it has less security focus than GrapheneOS or CalyxOS, and is more of a “custom ROM” than a privacy OS.

/e/OS (Murena): Privacy Android that replaces Google services with microG and centres on its own cloud account, Murena Workspace. We rate it as less hardened than GrapheneOS.

DivestOS: No longer an option. Its build repository is archived and was last changed in December 2024, and its website did not load when we checked on 4 November 2026.


Practical: which device?

For GrapheneOS: The Pixel 9a is our value pick for 2026. The Pixel 10a is the newer model, supported until March 2033, with the same Tensor G4 chip as the Pixel 9 series. The Pixel 10 uses Tensor G5 but is more expensive. Pixel 8 and newer have a 7-year minimum support period. For UWB you need a Pro model such as the Pixel 10 Pro; the base Pixel 10 does not include it. The Pixel 11 series has no GrapheneOS builds yet.

For CalyxOS: A Pixel 8 or newer gives the longest support, except that the Pixel 10 and 10 Pro and the Pixel 11 series are not on its list as of 4 November 2026 (the Pixel 10a is). Outside Pixel, look at the Fairphone 5 (estimated to September 2031) or Fairphone (Gen. 6) (estimated to June 2033). Don’t buy a Motorola, a SHIFTphone 8 or a Fairphone 4 for it: support is listed as ending between December 2026 and March 2027. On non-Pixel phones, CalyxOS says the stock updates it depends on are usually a month or two behind AOSP.

Fairphone consideration: Fairphone offers long software support (the Gen. 6 until 2033, with a five-year warranty; in Europe three of those years need registering the phone), but it doesn’t meet GrapheneOS’s published hardware and update requirements. For example, the Fairphone 5 moved to security updates every two months from mid-2026 and the Gen. 6 will from June 2028. A reasonable choice for CalyxOS (which relocks the bootloader on Fairphone, using its installer’s checks); not available for GrapheneOS. More in Fairphone and privacy.


Conclusion

There is no universal answer. In our assessment, GrapheneOS is the strongest security choice and suits people with higher profiles or who want the best possible Android security. CalyxOS is more accessible and enough for many people who want to move away from Google without becoming a security expert, as long as you accept that it has only recently returned from a long pause.

In their default setup, both send far less to Google than standard Android does.

It becomes overkill when you choose GrapheneOS because it sounds like “the best,” while CalyxOS or even a better-configured stock phone would be more realistic for your situation. The reverse is also true: CalyxOS is the wrong choice when your risk or actual requirements clearly call for more hardening than the project offers.

Next step

Decide first

Go further

Reviews