A month-long hands-on evaluation published today by TechRadar has given GrapheneOS its most significant mainstream endorsement yet, concluding that the privacy-hardened Android alternative is capable of serving as a primary smartphone for daily use in 2026 — while making clear that one critical capability is gone forever by design: Google Pay will never work on GrapheneOS, and no update or workaround will change that.

The evaluation, conducted by TechRadar's VPN Editor Rob Dunne on a Google Pixel 8 Pro, marks a meaningful shift in how GrapheneOS is covered by major tech outlets. Where earlier coverage framed the project as a niche tool for security researchers and privacy absolutists, Dunne's conclusion is more prosaic: it mostly works. Setup takes roughly ten minutes with no command-line skills required. Battery life and performance are indistinguishable from stock Android. The trade-off is real and specific, not vague or theoretical — and for the right user, it may be a trade-off worth making. Dunne noted that banking apps and Android Auto presented real friction during his test, and that the experience left him wanting more from the platform overall — a candid assessment that reflects both the genuine progress GrapheneOS has made and the gaps that remain.

GrapheneOS in 2026: What It Actually Is

GrapheneOS is an open-source mobile operating system built on the Android Open Source Project (AOSP) but maintained by the Canadian non-profit GrapheneOS Foundation rather than by Google. It strips out all Google services by default — no Play Store, no Gmail, no Maps, no location telemetry routed to Google's servers — and replaces the standard Android security model with a significantly hardened alternative.

The project was founded in 2014 (initially as CopperheadOS) and is currently compatible with Google Pixel devices ranging from the Pixel 6 series through the Pixel 10 series, which receive timely security updates and are the only Android devices that meet the project's strict hardware requirements. Out of the box, it ships with a lean set of applications: a calculator, a camera, a sandboxed PDF viewer, and the GrapheneOS App Store. What it conspicuously does not include is the Google Play Store — though, as Dunne found, installing it is the practical first step for most users.

What Sandboxed Google Play Actually Does

GrapheneOS's breakthrough compatibility mechanism — and the source of both its usability gains and its hardest limits — is its sandboxed Google Play implementation.

On stock Android, Google Play Services operates with a massive amount of special system-level privileges, running entirely outside the app sandbox that restricts every other application's access to the device. In plain terms: while your banking app is locked in a security container that prevents it from reading other apps' data or accessing privileged system functions, Google Play Services runs alongside the operating system itself, with access that no third-party app can revoke.

GrapheneOS's approach is architecturally different. It runs the entire Google Play stack — Play Services, the Play Store, and any Play-dependent apps — inside the same unprivileged app sandbox as everything else. Google Play receives no special OS-level access. Its permissions are set by the user, individually, exactly as they are for any other installed application. Push notifications, in-app billing, FIDO2 authentication, Firebase Cloud Messaging — these all continue to work, because they operate through standard Android APIs that the sandbox permits. What does not work is any function that requires Play Services to have system-level authority rather than user-level authority.

This matters beyond GrapheneOS itself. If full Google Play app compatibility can be maintained while removing system-level Play Services access, then the system-level access in stock Android was never technically required for app compatibility — it was required for something else. What that something else is, Google has not been obligated to explain; what it enables in practice is Google's collection of continuous device telemetry, location data, and behavioral signals that fund its advertising business.

What Works, What Doesn't, and Why the Google Pay Wall Is Permanent

Dunne's month-long test on the Pixel 8 Pro produced a compatibility picture that has shifted substantially from even two years ago — though he found meaningful friction with banking apps and Android Auto specifically.

Community-maintained compatibility lists and independent 2026 reviews report that most mainstream applications function normally through sandboxed Google Play: social media, messaging (including WhatsApp, Signal), streaming services, navigation, email, and password managers all work without meaningful friction. Banking has improved significantly. Major US banks — Chase, Amex, Discover, Wells Fargo, Navy Federal — as well as UK banks including HSBC, Barclays, Monzo, and Starling, and most EU retail banks, are now reported to pass GrapheneOS users through their security checks when sandboxed Google Play is installed. The key variable is which level of Google's Play Integrity API a specific bank uses. Apps that check only whether the device is rooted (the basicIntegrity check) pass GrapheneOS fine. Apps that check whether the device has Google's official device certification (the ctsProfileMatch check) do not — and many major banks updated their requirements between 2024 and 2025 following guidance from the GrapheneOS project and regulatory pressure in the EU and UK. Users should check a current community-maintained compatibility list for their specific bank before switching.

Android Auto, which required extra configuration steps in earlier versions of GrapheneOS, has functioned since late 2023 when the project added compatibility through the sandboxed Play layer, though some users report setup complexity.

Google Pay is a different case entirely, and the distinction is not one of omission or neglect. Google Pay requires Host Card Emulation — the mechanism by which a phone's NFC chip simulates a payment card — to be managed by a service running with system-level privileges and NFC routing rights that only system services can hold. GrapheneOS's sandboxed Play model cannot grant these privileges without compromising the core principle of the security model. There is no version of this that works. There is no upcoming fix. Google Pay is architecturally incompatible with what GrapheneOS is. Readers who rely on tap-to-pay from their phone need to know this before they consider the switch. Alternatives include contactless bank cards, a Curve card linked to existing accounts, or a paired smartwatch with its own NFC hardware.

Why It Only Runs on Pixels Right Now

GrapheneOS's Pixel exclusivity is not a preference — it is a hardware requirement. The project demands devices with specific security features: an unlockable bootloader that supports user-set signing keys (which GrapheneOS re-locks after installation, preserving verified boot), a dedicated security chip equivalent to Google's Titan M2, hardware memory tagging support (the Memory Tagging Extension, or MTE, introduced with Tensor G2 in the Pixel 8 series), and a vendor committed to timely firmware security updates. Current Motorola devices do not meet these requirements. Existing Pixel devices do.

This also explains the security benefit that goes beyond app sandboxing. GrapheneOS patches a VPN kill-switch bypass vulnerability that Google declined to address in stock Android — a flaw under which traffic could escape an active VPN tunnel under certain conditions. It implements an auto-reboot mechanism that returns the device to a "Before First Unlock" state after 18 hours of inactivity, making forensic extraction significantly harder. And it provides per-app network and sensor permissions that stock Android does not offer — allowing users to run an application with no internet access, or with the microphone and accelerometer disabled, without affecting other apps.

How Does GrapheneOS Get Installed?

The project provides a web-based installer at grapheneos.org that requires no command-line knowledge. The process takes roughly ten minutes on a supported Pixel connected over USB. The bootloader must be unlocked via the device's developer settings — a one-time process — before installation. Once GrapheneOS installs and verifies, the bootloader is re-locked, restoring verified boot with GrapheneOS's own signing keys rather than Google's.

Dunne's description of the initial experience mirrors what community reviews have reported: the interface is immediately familiar to anyone who uses stock Android. The home screen, app drawer, and quick settings panel are structurally identical to standard Pixel software. The practical difference appears at setup: no Google Play Store, no Google account prompt. The first substantive decision point is whether to install sandboxed Google Play — and for most users, the answer will be yes.

Motorola Partnership Signals Broader Hardware Future — But Not Yet

The only significant hardware development since the Pixel exclusivity began came at Mobile World Congress on March 2, 2026, when Motorola and the GrapheneOS Foundation announced a formal long-term partnership. The partnership is real but the timeline is specific: compatible Motorola devices are not expected until 2027, targeting flagship lines including the Motorola Signature, Razr Ultra, and Razr Fold. Existing Motorola hardware does not meet GrapheneOS's requirements and will not receive support. The 2027 devices are being engineered from scratch with the required hardware security components.

The origin of the partnership is instructive. GrapheneOS developers have noted publicly that Google stopped publishing the userspace driver library code for Pixel devices, which had previously been open-source. That decision "directly led to Motorola reaching out to us and our partnership," the GrapheneOS team stated. What had been a stable arrangement between GrapheneOS and the Pixel hardware ecosystem became strained by Google's move toward more closed-source components — and Motorola identified an opportunity.

The practical implication for buyers today: anyone evaluating GrapheneOS must currently commit to Google Pixel hardware, which carries its own irony. If the Motorola timeline holds, that constraint ends in roughly 12 to 18 months.

Who Actually Needs GrapheneOS Right Now?

The honest answer from Dunne's evaluation — and from the broader technical picture — is that GrapheneOS is no longer a project that requires significant technical tolerance to use. Setup is accessible, app compatibility has reached a threshold where most users will not notice meaningful gaps, and the security benefits are real.

The specific population for whom it makes unambiguous sense: users who want full Google Play app compatibility but who also want Google Play Services running with no elevated privileges, who can tolerate losing Google Pay, and who are willing to verify that their banking apps are on the compatibility list before committing. Privacy researchers, journalists, professionals handling sensitive communications, and users who want the strongest available protection against device forensics are the natural audience. But the technical barrier that once separated that audience from everyone else has substantially narrowed.

The specific population for whom it clearly does not: anyone whose financial life is organized around Google Pay or similar mobile NFC payment, anyone who depends on apps that use ctsProfileMatch device attestation, and anyone who is not currently using a supported Pixel and is not willing to purchase one.

Edward Snowden, who has used GrapheneOS on Pixel hardware for years, represents one end of the user spectrum. Dunne's evaluation represents the other — a privacy-curious mainstream technology writer who spent a month with it and came away acknowledging the real limitations while noting that they weren't the limitations he expected.

Frequently Asked Questions

Does GrapheneOS work with most banking apps in 2026?

Most major banking apps — including Chase, Amex, HSBC, Barclays, Monzo, and Starling — are reported to work on GrapheneOS when sandboxed Google Play is installed. The key variable is which level of Google's Play Integrity API a specific bank uses. Apps that check only for basic device integrity (basicIntegrity) pass GrapheneOS fine; apps that require Google's official device certification (ctsProfileMatch) typically do not. Most major banks updated their requirements in 2024–2025 following guidance from the GrapheneOS project. Users should check a current community-maintained compatibility list for their specific bank before switching.

Why will Google Pay never work on GrapheneOS — and what can I use instead?

Google Pay requires a payment credential management service to run with system-level NFC routing privileges — the kind of access that only a system process, not a sandboxed app, can hold. GrapheneOS's core security model deliberately prevents any app, including Google Play Services, from gaining system-level access. This is not a bug or a missing feature; it is the security model working as designed. No update will change it. Alternatives include using contactless bank cards directly, a Curve card that routes NFC payments through existing accounts, or a paired smartwatch (such as a Garmin or Samsung Galaxy Watch) that has its own NFC hardware.

What hardware do I need to run GrapheneOS, and when will Motorola phones work?

GrapheneOS currently supports Google Pixel devices from the Pixel 6 series through the Pixel 10 series. Only Pixel devices meet the project's hardware requirements: an unlockable bootloader with user-settable signing keys, a dedicated security chip (Titan M2), hardware memory tagging support, and a vendor commitment to timely firmware security updates. Motorola announced a partnership with the GrapheneOS Foundation at MWC 2026 in March; compatible Motorola devices are not expected until 2027, and existing Motorola hardware will not be compatible. The 2027 devices are being engineered from scratch to meet the requirements.

Is GrapheneOS harder to install than standard Android?

GrapheneOS provides a web-based installer at grapheneos.org that requires no command-line knowledge. The process takes approximately ten minutes on a supported Pixel connected to a computer via USB. The only prerequisite is unlocking the device's bootloader through standard developer settings — a one-time step — after which GrapheneOS installs, verifies, and re-locks the bootloader with its own signing keys. Users who have followed step-by-step web installers for other software should find the process manageable.