The current route is loading. No background authority or network action is implied by this state.
SEND is the universal device entry point. Choose a nearby or trusted destination, choose what should move, review the exact dispatch plan, then continue. BEAM remains the transfer technology; specialized engines keep their own security boundaries underneath.
Choose a device →SEND is the universal device entry point. Pick the destination first, choose what should move, review the dispatch plan, then continue explicitly. BEAM keeps the product experience unified while each existing transport keeps its own payload, limits, verification and acceptance rules.
No background presence. Trusted devices are stored only in this browser and reconnect only after explicit mutual proof.
No trusted devices are saved in this browser.
Create trust in SEND →Describe the job, not the transport. SEND chooses the narrow existing engine that already owns it.
SEND stages locally only after this explicit action, then opens the existing transport or trusted-device authentication flow.
Choose a destination first.
DEVICE / Choose a device · WHAT / Nothing selectedConnection metadata expires automatically. File bytes travel over the encrypted WebRTC channel.
Saved browser trust is optional. First trust uses ECDH plus a human verification code; later sessions use rotating rendezvous and mutual proof before a queued SEND action can continue. There is no background presence or cloud device list.
SEND does not collapse transfer semantics into a universal payload protocol. One file remains BEAM Safe Send, short text and URLs remain CLIP, larger supported text remains LINK, collections remain TRAY, workflow continuation remains CONTINUE, and current-view continuity remains a trusted pathname-only Device Hub action.
Direct P2P is preferred where the owning transport supports it. Receiver/open/continue actions remain explicit, and every specialized engine keeps its existing limits and verification behavior.
File Intelligence identifies the content, computes the complete SHA-256, counts metadata signals and scans supported files for credential plus deterministic PII patterns locally. High-risk privacy or structural signals require explicit sender review.
Either side can create the short-lived route. Signaling keeps only bounded session data; file name and MIME stay off signaling and move only after the protected peer channel exists.
Sender-first QR opens the receive flow. Receiver-first QR opens the send flow. Both contain only a temporary route/code and accept exactly one counterpart.
ICE negotiates the route. TURN is a transient network fallback, never a payload archive.
The receiver sees name, type and size before selecting a destination and allowing transfer.
Backpressure protects browser memory while progress, throughput and estimated time stay visible.
The receiver keeps the file only when its computed digest matches the sender’s final digest.
BEAM v1.5 has a strict 512 MB product limit and a ten-minute standard session lifetime; SCAN can request a bounded 30-minute receiver route for multi-page Phone Bridge work; SIGNPAD uses a bounded 20-minute route for handwriting capture. Safe Send now includes deterministic PII preflight, and WIPE can stage a verified copy locally for one-time same-browser handoff. Those limits are deliberate and visible.
Public availability still depends on deploying the supplied signaling endpoint and Coturn configuration, then completing cross-network device verification on the production host.