Open-source project
TryQuiet/quiet avatar
TryQuiet/quiet

Quiet: no removal command, one community per install, and a publish hook that pushes

A private, p2p alternative to Slack and Discord built on Tor & IPFS

2,662 stars152 forksTypeScriptGPL-3.0

At a glance

What is it?
Quiet syncs messages between member devices over Tor using OrbitDB, and its own README opens with a warning that the project is not audited. The list of features it admits are still missing includes removal, direct messages, and joining a second community.
Who is it for?
Treat Quiet as an experiment for a team that accepts an unaudited client, not as a home for anything where privacy and security are critical, which is the project's own stated limit. Before anyone adopts it, look at the three gaps that decide daily use, member removal, private channels, and joining a second community, then decide who will maintain the fork.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 13 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • TryQuiet/quiet2,662 ★ · +5
Star history
Repository2026-10-042026-11-15
TryQuiet/quiet2.7k2.7k

5 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The README opens by saying the project is not audited

The first warning block on the page states that Quiet is not audited and should not be used when privacy and security are critical, then adds that it lacks basic features and will not replace your Slack or Discord yet, in the same breath as a claim that the team uses it daily. So the project hands you the disclaimer and the endorsement together, and leaves you to weigh them. The specific security argument is not in this repository either: the navigation bar sends readers to a threat model hosted in the wiki of a repository named TryQuiet/monorepo, and the comparison with similar apps lives in a second wiki page under that same other name. Nothing about the audit state can be checked from the files in this tree.

The publish script commits and pushes on its own

Releasing is not a manual step you can inspect afterwards. The root manifest runs a version bump, then a post-publish hook that copies a changelog, stages every change, commits it with the message Update packages CHANGELOG.md, and pushes, all in one command:

code
{
  "scripts": {
    "publish": "lerna version $npm_config_release --no-private",
    "postpublish": "node copy-changelog.js && git add . && git commit -m 'Update packages CHANGELOG.md' && git push",
    "applyPatches:qss": "patch -f -p0 < ./patch/qss.npmrc.patch || true",
    "pull:submodules": "git submodule update --init --recursive --no-fetch"
  }
}

The git add with no path means whatever happens to be in the working tree goes into that commit. The published versions of @quiet/desktop and @quiet/mobile are both dated 2026-09-25, two days after the last push recorded on the default branch, which is develop, on 2026-09-23, so the release and the branch history are not the same clock.

OrbitDB and the noise transport are built from in-tree copies

The README credits message syncing to OrbitDB and describes it as a mashup of Git, a gossip protocol and BitTorrent, but the manifest does not install it. It builds it. The build:orbitdb script changes into a directory called 3rd-party/orbitdb, runs an install there, and produces two outputs, a dist build and a debug build. The same pattern covers 3rd-party/js-libp2p-noise, the transport layer, and 3rd-party/auth, which uses a different package manager again, pnpm. The top level carries a .gitmodules file, and the manifest offers pull:submodules with a --no-fetch flag plus a second variant that adds --remote, along with a submodule policy test that checks pinned submodules. So the dependency most readers care about is vendored here, and the convenience script that moves submodules to the remote tip is one flag away.

Patch failures are swallowed, and every end-to-end run starts a component the README never defines

The applyPatches:qss script feeds a patch file to patch with the force flag, and ends the line with an or true, so a patch that does not apply still reports success. That is the only failure handling in the release and build path described here. The same abbreviation shows up in the test scripts: the macOS end-to-end run starts a component called qss before it launches the desktop tests, and the Linux build does the same before packaging. The README's headline is that there are no servers, and it repeats that no server is required, yet the end-to-end suites cannot start without this one named process. Nothing in the README says what qss stands for, what it listens on, or when it is expected to be running.

Removal, direct messages, and private channels are all on the still-missing list

There is a section headed Planned, with still-missing in the parenthetical, and it holds eleven entries: iOS notifications, direct messages, mentions, removal, user profiles, message deletion, status, reactions, multiple communities, account recovery, and private channels. Three of those decide whether a team can use the thing at all. Removal means a community owner has no documented way to evict a member. Private channels and direct messages together mean there is no described way to keep a message away from the rest of the community. Multiple communities means one install is one community, so work and personal chats cannot live side by side. The iOS entry also carries the project's clearest admission of its own architecture limit, since notifications there need help from a service Apple requires to be centralized.

The summary says Tor and IPFS, and IPFS appears once

The project's one line summary calls it a private, peer-to-peer alternative to Slack and Discord built on Tor and IPFS. Tor is everywhere in the page: syncing happens over it, bridges and Tor Browser support are on the post-1.0 list, and publishing is described as going out over Tor through OnionBalance and Tor2web. IPFS appears once, at the end of that publishing item, and publishing itself sits in the features the project defers until after 1.0. Read strictly, the current transport story is Tor plus a vendored OrbitDB, and IPFS belongs to a sharing feature that has not arrived. The browser story is deferred as well, with Tor Browser support and support for any modern browser through Arti compiled to WebAssembly listed after 1.0.

File transfers have no stated limit, communities are capped near 100 members

The features section promises to send and receive giant files without arbitrary limits. The post-1.0 section puts a number on the other resource: large communities of 1000 members or more are planned, and the current limit is about 30 to 100 members. Same section defers moderation, automatic removal of users who send disruptive messages, message search, threads, bridges, and both browser clients. Set that against the missing removal command and the picture is consistent: reaching the member ceiling, you have no owner action for a disruptive member today, and the settings that would handle it, moderation plus spam and denial-of-service protection, sit on the same deferred list. The desktop apps for Mac, Windows and Linux ship as ordinary installers, a dmg for macOS and an exe for Windows, and Android gets working notifications while the iOS build ships through TestFlight without them.

The threat model and the comparison live in another repository's wiki

Two of the links a reader is told to rely on point outside this tree. The threat model and the frequently asked questions are both wiki pages under the TryQuiet/monorepo path, while this repository is named TryQuiet/quiet, and only the developer setup link stays inside, pointing at packages/desktop/README.md. What the tree does contain is a lot of process: a c4 directory, a docs directory, PUBLISHING.md, RELEASE_NOTES_GUIDE.md, CONTRIBUTING.md, a changelog, a scripts directory, run-tests.sh, test.sh, and remtags.sh, plus a stray android_crash_logs.txt committed at the repository root next to the license file. Package manager setup is similarly split, with a package-lock.json, a .yarnrc.yml, and a pnpm install in one of the third-party builds.

Editorial conclusion

Treat Quiet as an experiment for a team that accepts an unaudited client, not as a home for anything where privacy and security are critical, which is the project's own stated limit. Before anyone adopts it, look at the three gaps that decide daily use, member removal, private channels, and joining a second community, then decide who will maintain the fork. The sync layer and the transport are built from in-tree copies, the publish hook commits and pushes on its own, and the documentation everyone is pointed at lives in the wiki of a differently named repository.

Frequently asked questions

Is Quiet audited for security?

No. The README carries a warning that Quiet is not audited and should not be used when privacy and security are critical, and it points to a threat model page held in the wiki of a repository named TryQuiet/monorepo rather than in this tree.

Can you remove someone from a Quiet community?

Not today. Removal is listed under planned but still-missing features, alongside direct messages, mentions, user profiles, message deletion and private channels, while appointing moderators and silencing users sits in the post-1.0 list.

How many people can be in one Quiet community?

The post-1.0 section says communities of 1000 members or more are planned and that the current limit is roughly 30 to 100 members. The separate promise of files without arbitrary limits is about transfers, not members.

Do you need an email address or phone number to use Quiet?

No. The feature list states that unlike Slack, Discord, WhatsApp, Telegram and Signal, no email address or phone number is required to create or join a community, and access comes from an invitation code handed out by the community owner.

Can you belong to more than one Quiet community at a time?

Not in the current client. Multiple Communities is on the planned but still-missing list, and the how-it-works section says each community is a separate network whose data never reaches devices in other communities.

How does Quiet sync messages without a central server?

The README credits OrbitDB, which it describes as a mashup of Git, a gossip protocol and BitTorrent that broadcasts new messages, syncs the latest ones and fetches files. The root manifest builds that OrbitDB from a copy in 3rd-party/orbitdb rather than installing it from a registry.

Official sources

  1. License: GPL-3.0
  2. Project website
  3. README
  4. Releases
  5. TryQuiet/quiet on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/tryquiet-quiet.svg)](https://hysenlabs.com/projects/tryquiet-quiet)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/tryquiet-quiet.svg)](https://hysenlabs.com/projects/tryquiet-quiet)

Was this useful?