What Briar actually does
Briar is a free, open-source messenger built for the moments when a normal app can't be trusted — when the internet is down, a server might be seized, or the mere existence of a message log is a risk. It was started by developer Michael Rogers in 2011 and has been carried since by an all-volunteer team, funded by grants from the Open Technology Fund, the NLnet Foundation, and the EU-backed NGI programme rather than by a company monetizing user data.
The core product
What sets Briar apart from almost every other messenger on this site is that it has no central server at all. Messages travel directly between contacts' devices over Bluetooth, local Wi-Fi, or the Tor network, so there is no company database to hack, no company to subpoena, and no server log for anyone to seize after the fact.
That architecture also means Briar keeps working with zero internet connection: two nearby phones can exchange messages over Bluetooth or a local Wi-Fi hotspot even during a total shutdown, which is precisely the scenario the app was designed around.
Briar is also an unincorporated, entirely volunteer-run project rather than a registered company — unusual for an app with this many users, but itself part of the design: there is no single legal entity anyone could compel to hand over data, because there is no data sitting anywhere to hand over. The whole thing is free and open source under GPLv3/AGPL, developed under a public Code of Conduct and open governance rather than behind closed doors.
What's new or notable
The notable development as of mid-2026 is not a feature but the lack of one: in July 2026 the project entered maintenance mode. The volunteer team will keep shipping security and bug fixes, but active feature work has paused, which means the app's longstanding rough edges are unlikely to be addressed anytime soon:
- High battery drain on Android
- No file attachments
- No way to back up an account
For a project that has always run on donated time and grant funding rather than revenue, that's a realistic consequence of limited resources rather than a surprise, but anyone considering Briar today should go in expecting the app as it is now, not as it might become.
Who should use Briar
Great fit if…
- You need messaging that survives an internet blackout — Briar syncs over Bluetooth or local Wi-Fi with no internet or server involved, which is exactly the scenario it was built for.
- You're an activist, journalist, or working in a high-risk environment — the entire design, from no central server to no company to subpoena, targets people who need communication to survive hostile surveillance or shutdowns.
- You want a messenger with literally nothing to seize — with messages routed device-to-device and no corporate entity behind the project, there's no central point of failure for an attacker or authority to target.
- You're on Android, Windows, macOS, or Linux — and you're comfortable with contacts needing Briar installed and online at the same time to connect.
Skip it if…
- You or your contacts use an iPhone — there is no iOS app, and the developers have said one is unlikely to ever ship, which rules Briar out entirely for iPhone users.
- You need to send files or back up your account — both are longstanding gaps, and with the project now in maintenance mode, neither is likely to be fixed soon.
- You want to message people who aren't already committed to Briar — it only talks to other Briar users, with no bridging to other networks, and getting a contact set up takes real coordination since both people generally need the app installed and online at once.
- You care about active feature development — as of July 2026 the small volunteer team is only shipping security and bug fixes, not new capabilities.
Pricing in detail
There is nothing to pay for. Briar has never had a paid tier, in-app purchase, or business plan — the entire project runs on volunteer time and outside grant funding.
| Plan | Price | What's included |
|---|---|---|
| Briar | Free | The complete app — encrypted device-to-device messaging over Bluetooth, Wi-Fi, or Tor, group conversations, and offline sync — with no ads, no premium tier, and nothing else to buy. |
Where it falls short
- No iOS app, and none planned — the developers have indicated one is unlikely to ever ship, so iPhone users are locked out of Briar entirely, no matter who they're trying to reach.
- Feature development has paused — since entering maintenance mode in July 2026, the team is only committing to security and bug fixes, so known problems like Android battery drain, the lack of file attachments, and the absence of account backup are unlikely to be resolved soon.
- It only works with other Briar users — there's no bridging to other messaging networks, and because devices generally need to be online at the same time to sync directly, building out a contact list and having live conversations takes more coordination than a typical always-connected app.
Privacy & data
Briar's privacy model is architectural rather than a policy promise: because there's no central server, there's no company database of messages, contact graphs, or metadata sitting anywhere for a hacker, advertiser, or government request to reach. Messages route directly between devices over Bluetooth, local Wi-Fi, or Tor, and the project itself has no incorporated legal entity — an unusual structure that removes any single point authorities could compel to produce data, because none exists to produce.
The code is free and open source under GPLv3/AGPL, developed in the open under a public Code of Conduct, so its claims about how data moves can in principle be checked line by line rather than taken on faith. The tradeoff is that this decentralized model has real usability costs — no cloud backup, no cross-device sync in the conventional sense — that are the direct price of not having a server to lose your data to in the first place.
How we checked this
This entry is based on Briar's own project pages and its July 2026 maintenance-mode announcement at briarproject.org, last checked on 2026-09-05, cross-referenced against its published funding sources and license. We did not run new hands-on testing beyond what the developers themselves have documented about known limitations like battery drain and missing file transfer; those are described here as the project's own team has described them, not independently re-verified in this pass.