# dmotz/trystero

✨🤝✨ Build instant multiplayer webapps, no server required — Magic WebRTC matchmaking over BitTorrent, Nostr, MQTT, IPFS, Supabase, and Firebase

Repository: https://github.com/dmotz/trystero
Canonical: https://ross.abutalabs.com/products/trystero
Homepage: https://trystero.dev
Language: TypeScript
License: MIT
License Family: permissive
Topics: webrtc, p2p, peer-to-peer, chat, matchmaking, ipfs, bittorrent, webtorrent, serverless, firebase, javascript, signaling, signalling, realtime, decentralized, web3, mqtt, nostr, supabase
Last push: 2026-07-22T14:05:37+00:00

## Health v2 (maintenance only)
Score: 94/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 93, release rhythm 92, longevity 100
- inputs: {"age_days": 2138, "days_push": 42, "days_rel": 52, "gap_med": 27, "n_releases_24m": 16}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2705, forks 157 (observed 2026-08-28T04:07:11.554153+00:00)

## What it is
Trystero is a JavaScript/TypeScript library that adds serverless WebRTC peer discovery and communication to web apps, using BitTorrent, Nostr, MQTT, IPFS, Supabase, Firebase, or a self-hosted WebSocket relay as signaling strategies. It provides a simple rooms-and-actions API with automatic serialization, chunking, encryption, media streams, and React hooks, so apps can connect browsers directly without deploying matchmaking infrastructure.

## Use cases
- build a multiplayer web app without a backend server
- browser-to-browser file transfer
- add video or audio chat between peers
- sync collaborative cursors or shared state in realtime
- build a decentralized p2p chat room
- local-first data sync between browsers
- show realtime presence of connected users

## When to choose
- you want peer-to-peer WebRTC features without deploying or paying for a signaling server
- you prefer decentralized signaling via Nostr, BitTorrent, MQTT, or IPFS
- you need a simple unified API for data, file, and media streaming between browsers
- you want end-to-end encrypted direct connections where data never touches a server

## When to avoid
- you need guaranteed message delivery or a client-server architecture with central authority
- your app requires large-scale fan-out to many receivers (WebRTC mesh scales poorly)
- you need to support environments without WebRTC
- you require strict compliance where peer discovery via public relays is unacceptable

## Facets
- artifact type: library
- maturity: active
- function: websocket, serialization, cryptography, sdk
- domain: web-development, frontend, networking, microservices, privacy
- platform: browser, bun, cross-platform
- tags: webrtc, p2p, peer-to-peer, serverless, signaling, matchmaking, bittorrent, nostr, mqtt, ipfs, supabase, firebase, realtime, decentralized, chat, file-transfer, video-chat, react-hooks, real-time, nodejs, deno, javascript

## Member repositories
- dmotz/trystero (main) score 94

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:11.554153+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:15:50.912500+00:00, confidence not recorded.
  - readme: https://github.com/dmotz/trystero (fetched 2026-08-28T04:07:11.554153+00:00, sha 035e2d4e892b)
  - homepage: https://trystero.dev (fetched 2026-08-29T09:59:16.452267+00:00, sha 1c58bc6722e0)
  - site_page: https://trystero.dev/docs (fetched 2026-08-29T09:59:16.461615+00:00, sha 0f56aaa1b231)
- Data as of 2026-08-30T08:39:29.467469+00:00.