Community

Source, support, and who's behind BridgeSwarm

BridgeSwarm is source-available under AGPL-3.0, self-hosted on Gitea, and built by a small team that also uses it daily.

Source

Source repository

The full history, issues, and CI pipeline live on our self-hosted Gitea instance — not GitHub.

git.ssh.surf/snxraven/BridgeSwarm

Extension, native host, examples, branding package, and documentation — one monorepo.

git clone https://git.ssh.surf/snxraven/BridgeSwarm.git

Contributing

Set up a dev environment

Get running

git clone https://git.ssh.surf/snxraven/BridgeSwarm.git
cd BridgeSwarm
npm run setup
# Load unpacked: extension/

Run npm run examples to serve the demo gallery at 127.0.0.1:4173, and npm run sync:examples after editing anything under examples/.

Where changes tend to land

  • extension/ — MV3 background, content script, Control Center UI
  • native-host/ — host.js, messenger.js, capability packs
  • examples/ — source of truth for every demo
  • docs/ — architecture, API, data, capabilities, Protomux, HRPC references

Please open an issue before a large change — especially anything touching the native messaging protocol, extension IDs, or the install scripts, since those have hard-coded coexistence checks against other tools. Build/verification commands and CI behavior are documented in the repository README.

Support

Get support

Live chat

Discord

Live help and discussion on the Discord-Linux server — the fastest way to reach a real person.

 Tracker

Gitea Issues

Bug reports and feature requests, tracked against the actual codebase.

 Self-serve

Troubleshooting guide

Common install issues — native host exits, extension ID mismatches, missing HRPC spec.

Publisher

HoneyPeer, LLC

BridgeSwarm is owned and engineered by HoneyPeer, LLC, based in DeKalb County, Georgia, USA. For legal, licensing, or press inquiries, reach us at legal@honeypeer.com.

License

AGPL-3.0

§

BridgeSwarm is released under the GNU Affero General Public License v3.0. In practice, that means:

  • You can use, study, modify, and redistribute BridgeSwarm freely.
  • If you modify BridgeSwarm and let others interact with it over a network — the AGPL's key difference from plain GPL — you must make your modified source available to those users (AGPL §13).
  • Derivative works must remain under AGPL-3.0; there's no proprietary-relicensing path for forks.
  • Branding assets ship under the same license as the rest of the project.

This is a summary, not legal advice — read the full license text before shipping a modified deployment, and contact legal@honeypeer.com with licensing questions specific to your use case.

Join the swarm

Install it, break it, tell us on Discord — or send a patch.

Install BridgeSwarm Join Discord