Browser & WASM
A peer that lives inside a tab.
A WASM build of beacons-core compiled to WebAssembly / WASI runs inside any web browser, any Worker, any Wasmtime / Wasmer host. WebRTC datachannels carry traffic when there is no native socket access. It is the universal target.
What you get.
- PWA — install from any browser, no extension required
- Chrome / Edge / Brave / Arc / Opera / Vivaldi extensions
- Firefox extension via WebExtensions
- Safari extension wrapping the same WASM core
- Cloudflare Workers · Fastly Compute@Edge · Vercel Edge — same WASM
Supported platforms
The full list.
| Platform | Tier | Implementation | Channel |
|---|---|---|---|
| PWA (any browser) | T3 | WASM beacons-core + WebRTC | Served from any web app |
| Chrome / Edge / Brave / Arc / Opera / Vivaldi | T2 / T3 hybrid | WebExtensions + WASM core + native messaging host for WG (when host OS supports) | Chrome Web Store · Edge Add-ons |
| Firefox | T2 / T3 hybrid | WebExtensions + WASM core + native messaging host | AMO |
| Safari | T2 / T3 hybrid | Safari Web Extension wrapping the same WASM core | Mac App Store bundling |
| Cloudflare Workers | T6 | WASM/WASI build, V8 isolate host | Workers registry |
| Fastly Compute@Edge | T6 | WASM/WASI build, Wasmtime host | Fastly publish |
| Vercel Edge Functions | T6 | WASM/WASI build | Vercel deployment |
| Wasmtime / WasmEdge / Wasmer | T6 | Same WASM module | Direct embed |
| Hives flight | T6 | WASM/WASI build of beacons-core inside Hives Wasmtime | Hives registry |