Briar is in maintenance mode

The Briar team announced that, after a period of speculation about a shutdown, the project will continue but strictly in maintenance mode. This shift means the developers have decided to focus solely on keeping the existing codebase safe rather than adding new capabilities. The announcement also clarifies that the project is still active and not abandoned, which counters earlier rumors within the privacy community.

For software engineers, the practical effect is that the codebase will receive only security-related patches and routine bug fixes. No new APIs, UI changes, or performance enhancements are planned, so any integration work that depends on upcoming features must be paused or re-architected. Existing deployments should continue to function, but teams need to monitor the limited update stream for critical fixes.

Adopting or continuing to use Briar now carries minimal direct cost: the current versions for Android and desktop remain available and will be patched for vulnerabilities. However, because the project will not invest in addressing known usability and resource-usage problems, developers may need to allocate their own effort to work around high battery usage or unreliable background sync if those issues affect their use cases. No additional licensing or subscription fees are introduced, but the lack of new development could translate into hidden engineering overhead.

The decision to stop work on major improvements means that known limitations, such as the app’s heavy battery draw, difficulty adding contacts offline, and the absence of account backup or file-attachment support, will persist. Environments that require robust background operation on Android or expect richer collaboration features will encounter the same constraints as before. Until the project secures a longer-term plan or new funding, those gaps remain a hard stop for any functionality that depends on them.