Ross ROSS = Recommend OSS · open-source software intelligence for agents

dmotz/trystero

✨🤝✨ Build instant multiplayer webapps, no server required — Magic WebRTC matchmaking over BitTorrent, Nostr, MQTT, IPFS, Supabase, and Firebase observed · 2026-08-28

github.com/dmotz/trystero · homepage · TypeScript · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

94/100

  • Activity 93
  • Release rhythm 92
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 27
  • age_days: 2138
  • days_rel: 52
  • days_push: 42
  • n_releases_24m: 16

Full methodology

Adoption not part of the score

2705 stars · 157 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

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

library · maturity active

websocket serialization cryptography sdk web-development frontend networking microservices privacy browser bun cross-platform 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

3 sources

Member repositories

RepositoryRoleHealth v2
dmotz/trysteromain94

For agents

markdown · JSON · MCP: product_card(name="dmotz/trystero")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem