Graphite Messenger on GrapheneOS: The Private Phone Meets the Private Messenger

TL;DR: The strongest GrapheneOS messaging apps in 2026 are Signal and its hardened fork Molly — both run fully without Google Play Services, and Molly adds Google-free push through UnifiedPush. SimpleX, Briar and Session minimise metadata at the cost of convenience. Graphite Messenger, PrivacyPortal's own free beta, is a new privacy-first option worth trialling.

By the PrivacyPortal team — content current as of July 2026. Picking the right GrapheneOS messaging app is the step that trips up most people moving to a de-Googled phone, because so many apps quietly assume Google Play Services is present for push notifications. The good news: in 2026 you have real choices that work without Google. Signal runs fully on GrapheneOS and falls back to a persistent WebSocket connection when Firebase Cloud Messaging is missing. Molly, a hardened Signal fork, adds UnifiedPush for battery-friendly, Google-free notifications. SimpleX, Briar and Session go further on metadata. And Graphite Messenger — our own free public beta — gives you one more option. Below we compare them honestly and show you how to install one.

A GrapheneOS home screen with Signal, Molly and Graphite Messenger installed side by side.

Why messaging is the hardest part of going de-Googled

GrapheneOS ships without Google Play Services by default. Most Android apps use Firebase Cloud Messaging (FCM) — a Google service — to wake up and receive notifications while closed. Strip Google out and, historically, messages arrived late or only when you opened the app. That single dependency is why any GrapheneOS messaging app needs either its own always-on background connection or an alternative push system. Every option below solves that problem in a different way, so the "best" choice depends on how much convenience you'll trade for how much privacy.

The best messengers for GrapheneOS at a glance

Here's how the leading private messenger, no-Google-Play options compare on the things that actually matter on a de-Googled phone.

App	No-Google push	Fully FOSS?	Identifier	Best for
Signal	Built-in WebSocket fallback	Client yes; some Google libs	Phone number	Reaching contacts you already have
Molly	UnifiedPush or WebSocket	Yes (merged, Dec 2025)	Phone number (Signal account)	Hardened Signal for de-Googled phones
Graphite Messenger	Built-in (beta)	Beta by PrivacyPortal	See graphite.chat	Trialling a new privacy-first app
SimpleX	UnifiedPush or socket	Yes	None at all	Maximum metadata privacy
Briar	Tor / direct P2P	Yes	None	No-server, high-risk threat models
Session	Onion routing (polls)	Yes	Random account ID	No phone number required
Element (Matrix)	UnifiedPush	Yes	Matrix ID	Groups, communities, bridging

Signal without Google: the WebSocket fallback

Signal is the pragmatic default for most people, simply because your existing contacts are probably already on it. On GrapheneOS it installs and runs normally — you do not need Sandboxed Google Play. When FCM is unavailable, Signal keeps a persistent WebSocket connection open to its servers so notifications still arrive while the app is closed. In practice this costs a little more battery than Google's push, but on a modern phone the difference is small. If you want a private, mainstream messenger that "just works" the moment you leave Google behind, this is the one to start with.

Molly: the hardened Signal fork with UnifiedPush

Molly speaks the same Signal protocol and reaches the same people, but adds hardening the mainline app doesn't: an encrypted database at rest, automatic RAM wiping when locked, and stricter connection controls. It's the enthusiast's choice among GrapheneOS apps.

As of v7.68.5-1 (25 December 2025) the separate Molly and Molly-FOSS builds merged into a single, fully-FOSS app; the current release is v8.7.3-2 (April 2026).

Crucially for de-Googled users, Molly supports UnifiedPush via a MollySocket relay, giving you battery-friendly notifications with no Google service anywhere in the path. You can read the details on the Molly project on GitHub. If you can't or don't want to run a relay, Molly falls back to the same WebSocket mode as Signal — so it works out of the box either way.

Graphite Messenger: private messaging with nothing to hand over

Graphite Messenger is PrivacyPortal's own take on a degoogled phone messenger, built around the idea that the safest data is the data you never collect.

Graphite Messenger is in free public beta (v1.13.25), with the tagline "Private messaging with nothing to hand over."

We'll be straight with you: Signal and Molly are the mature, battle-tested choices, and Graphite is younger. But it's built by the same team that ships de-Googled phones, it's free, and it's designed from the ground up for people who don't want to depend on Google. If you like trying privacy tools early and feeding back to the developers, it's a genuinely useful thing to run alongside your main messenger. Grab it from graphite.chat or the download section at the end of this guide.

Graphite Messenger's chat screen running on a de-Googled GrapheneOS device.

Metadata-minimising options: SimpleX, Briar and Session

If your concern is not just message content but who-talks-to-whom, three apps go further and run without Google by design:

• SimpleX Chat — has no user identifiers at all; you connect via one-time invite links. Supports UnifiedPush for timely notifications.
• Briar — routes over Tor or connects device-to-device with no central server, so it keeps working even without internet infrastructure. Notifications are best-effort.
• Session — uses onion routing and a random account ID instead of a phone number, but polls for messages, so alerts can lag.

The trade-off is real: no phone number means it's harder to find friends, and P2P or polling designs mean notifications aren't always instant. Pick these when your threat model justifies the friction.

How to install a private messenger on GrapheneOS

Prerequisites: a phone running GrapheneOS, 15 minutes, Wi-Fi, and a backup of any existing chats. Messengers like Signal and Molly do not restore history from the cloud, so an export is your only copy.

1. Back up first. In your current app open Settings > Chats > Backups, create a backup, and write down the passphrase somewhere safe. Without it the backup is unrecoverable.
2. Update GrapheneOS. Go to Settings > System > Update, install any pending build, and reboot.
3. Download the installer. From the "Modules, apps & files to try" section below, get your chosen app — Graphite Messenger, Molly or Signal. GrapheneOS's built-in package installer opens the APK; approve the one-time "install unknown apps" prompt for your browser.
4. Install and open it. Grant only the permissions you actually need — Signal and Molly work without Contacts access if you prefer to keep your address book private.
5. Set up notifications. Signal and Molly both work immediately using a background WebSocket, no Google required. For fully battery-optimised, Google-free push on Molly, switch Settings > Notifications > Delivery to UnifiedPush and pair a distributor such as ntfy plus a MollySocket relay (advanced — you host or trust a relay).
6. Register or link. Register your number, or link as a secondary device from Signal on another phone. For Graphite Messenger, follow the in-app onboarding at first launch.
7. Verify it works. Open Settings > Help and confirm the version (for example Molly v8.7.3-2 or Graphite v1.13.25). Then lock the phone, have a second account message you, and check the notification lands within a few seconds.

The GrapheneOS package installer approving a messenger APK, with the version number visible.

How Google-free push actually works

When people ask why the best messenger for GrapheneOS still notifies them instantly, the answer is usually one of two mechanisms: a self-maintained background socket (Signal, Molly's WebSocket mode) or UnifiedPush, an open standard that replaces FCM.

UnifiedPush reached its five-year milestone in January 2026 and now underpins Google-free push for Molly, Element, SimpleX and other clients.

With UnifiedPush you run a "distributor" app (commonly ntfy) that holds one connection open on your behalf; other apps route their notifications through it. It's efficient because one socket serves many apps instead of each app maintaining its own. You can learn more at the UnifiedPush project site. The upshot: Google is genuinely optional for modern private messaging.

Common pitfalls to avoid

• Over-aggressive battery restrictions. If Android's background limits kill the WebSocket, notifications stop. Exempt your messenger from battery optimisation.
• Expecting instant push from Session or Briar. These poll or work peer-to-peer, so delays are normal, not a bug.
• Losing your backup passphrase. Signal and Molly backups cannot be recovered without it.
• Believing any messenger "defeats" a bank or app check. Messengers are unrelated to Play Integrity or banking detection — do not assume one protects the other.
• Running old separate Molly builds. Molly and Molly-FOSS are now one app; uninstall the legacy split builds before migrating.
• Registering the same number on two apps at once. Only one Signal-based app can hold the primary registration; the others must be linked devices.

Which GrapheneOS messaging app should you choose?

Use this quick decision framework:

• You want your existing contacts and zero fuss → Signal.
• You want Signal's network but hardened, with Google-free push → Molly.
• You want to support and trial a new privacy-first app → Graphite Messenger.
• You want no phone number and minimal metadata → SimpleX or Session.
• You have a high-risk threat model and want no servers at all → Briar.
• You need group communities or bridging → Element on Matrix.

Most readers are well served running Signal or Molly as their daily driver and keeping one metadata-minimising app for sensitive conversations. If you'd rather skip the setup entirely, our pre-configured de-Googled phones arrive ready for exactly this.

Frequently asked questions

Does Signal work on GrapheneOS without Google Play Services?

Yes. Signal detects when Firebase Cloud Messaging is unavailable and automatically opens a background WebSocket to its servers, so notifications arrive without Google. You don't need Sandboxed Google Play installed.

What is the best messenger for GrapheneOS?

For most people, Signal — because your contacts are already there and it works without Google. If you want extra hardening and battery-friendly, Google-free push, choose Molly. For minimal metadata, look at SimpleX, Session or Briar.

Do I need Sandboxed Google Play to send messages?

No. Signal, Molly, Graphite Messenger, SimpleX, Briar, Session and Element all run without any Google Play components on GrapheneOS. Sandboxed Google Play is only needed for unrelated apps that hard-depend on Google APIs.

Will notifications be delayed without Google?

Usually not. Signal and Molly's WebSocket mode and UnifiedPush both deliver alerts within seconds. The main cost is a small amount of extra battery from keeping a connection open. Poll-based or P2P apps like Session and Briar can be slower by design.

Is Graphite Messenger ready to replace Signal?

Graphite Messenger is a free public beta (v1.13.25), so we'd suggest running it alongside a mature app rather than as your only messenger for now. It's a great way to try a privacy-first tool early and shape its development — but Signal and Molly remain the established recommendations.

Can I use WhatsApp on a de-Googled phone?

It can be made to run, but WhatsApp is neither open source nor metadata-minimising, and it works best with Google components present. If privacy is your goal, one of the messengers above is a far better fit.