Briar moves into maintenance mode – project status and community implications

Briar moves into maintenance mode – project status and community implications

Briar moves into maintenance mode – what it means for users and the privacy‑messaging ecosystem

Briar is still alive but will only receive essential security patches and bug fixes; new feature work is on hold until resources allow a bigger effort.

Project status: active but limited to maintenance

The Briar team announced that the project will continue in maintenance mode. This means developers will:

  • Publish security updates and critical bug fixes.
  • Pause major work on long‑standing problems such as high battery consumption, unreliable background operation on Android, missing account‑backup and file‑attachment features, and a cumbersome contact‑adding flow.
  • Keep the existing Android and desktop binaries functional for as long as possible.

The shift follows a year‑long contemplation of shutting the project down entirely. Community support after the announced shutdown prompted the team to keep the codebase alive, albeit with a reduced scope.

"We’re only making essential security updates and bugfixes for now, but eventually we hope to make some incremental progress on those longstanding issues." – Briar project announcement, 13 Jul 2026

Why the change matters for privacy‑focused users

Briar’s core value proposition—decentralised, server‑less, end‑to‑end encrypted messaging over local networks, Bluetooth, and Tor—remains intact. However, the maintenance‑only roadmap signals that:

  • Feature parity with mainstream messengers will not improve soon. Users cannot expect new capabilities such as media attachments or seamless background syncing.
  • Battery‑life and reliability on Android will stay problematic. The team cited these as unsolved technical hurdles that contributed to the original shutdown decision.
  • Long‑term viability depends on future funding or a community‑driven fork. Without fresh resources, the codebase will age, and security updates may become infrequent.

For organizations or individuals that rely on Briar for secure, offline communication (e.g., NGOs operating in low‑connectivity regions), the announcement is a call to evaluate risk and consider contingency plans.

Community reaction on Hacker News

The HN thread highlighted several recurring themes:

  • Technical constraints of mobile OSes – Commenters noted that Android and iOS aggressively limit background processes, which forces peer‑to‑peer apps like Briar to rely on battery‑draining polling or platform push services.

    "Anything that tries to read a ‘mailbox’ on a smartphone is bound to run into difficulties… The OS listens to a single endpoint and farms out pushes that way." – Karrot_Kream

  • Comparisons to alternative mesh solutions – Some users suggested hardware‑based mesh radios (e.g., Meshtastic, Meshcore) as a more reliable backbone for off‑grid messaging.

    "I’ve been attempting to build something similar and every time I take an honest look at the state of affairs on mobile phones I’m leaning towards running the way Meshtastic users do…" – MatrixMan

  • Funding challenges – Several comments pointed out that Briar’s reliance on grants (Small Media Foundation, Open Technology Fund, etc.) left it vulnerable when those streams dried up.

    "The truth is donations do not work for tiny open source projects in the long term…" – rvz

  • Future prospects and forks – A few participants asked whether a community fork could revive development, mentioning projects like Berty Messenger or BitChat as possible successors.

    "Anyone know of a fork or similar project? Maybe Meshtastic/MeshCore/BitChat. Berty Messenger’s last update on iOS was in January 2025." – HelloUsername

Overall, the discussion underscored that Briary’s technical hurdles are intertwined with ecosystem constraints (mobile OS policies, funding scarcity) rather than purely code‑level bugs.

Funding landscape and its impact

Briar has historically received support from a diverse set of organisations, including the Small Media Foundation, Open Internet Tools Project, Access Now, Open Technology Fund, Prototype Fund, Internews, NLnet Foundation, NGI programme, ISC Project, and eQualit.ie. The announcement did not specify whether any of these funders are still active, but the lack of new financing was a key factor in the decision to scale back.

"We were reluctant to look for funding without having a long‑term plan, and so we could only work on Briar in our spare time." – Briar announcement

The comment by nyolfen hinted at possible geopolitical influences, noting that two funders have ties to US‑aid programs, though no concrete link to the maintenance decision was provided.

What users can do now

  1. Update to the latest release – Ensure you are running the most recent Android or desktop version to receive the latest security patches.
  2. Back up contacts manually – Since automatic account backup is not on the roadmap, export your contact list and conversation logs if the feature is still available.
  3. Consider complementary tools – For reliable offline messaging, explore hardware‑based mesh networks (e.g., Meshtastic) or other peer‑to‑peer apps like Berty that may still receive active development.
  4. Monitor the project’s mailing list – The developers have provided contact emails (nico@briarproject.org, torsten@briarproject.org, contact@briarproject.org) and a Mastodon account (@Briar) for updates.

Bottom line

Briar’s transition to maintenance mode preserves a valuable privacy‑focused messenger for the time being, but the lack of new feature development and ongoing funding constraints mean that users should prepare for a static product lifecycle. Community interest remains high, and the discussion suggests that hardware mesh solutions or a community‑driven fork could fill the gap left by Briar’s limited roadmap.

Contact information

Sources