Web Mode
Best for quick starts in browser-compatible swarms and lightweight handoffs.
Route-aware transfer UI.
Static UI. Local transfers. No relay.
Plan each transfer route before you start. Keep records in your browser, connect local or remote infrastructure only when you choose, and run without central payload relay.
Web Mode is for WebRTC-compatible swarms. For classic TCP/UDP BitTorrent paths, use Local Bridge or Remote Node.
Runtime model
Best for quick starts in browser-compatible swarms and lightweight handoffs.
Best when your own machine should run the transfer path and policy controls.
Best for persistent remote execution on infrastructure you already own.
Live interface
Transfer Library
Web Mode
Web Mode uses WebRTC-compatible swarms. Classic TCP/UDP BitTorrent requires Local Bridge or Remote Node.
Route Model
Local Bridge
Remote Node
The remote node operator controls the node. Veilo ships with no default node and never routes through veilo.quest.
Shortlinks
Privacy & Compliance
Library data and local shortlinks stay in this browser with IndexedDB and localStorage fallback.
Contact and compliance endpoints enforce CSRF checks, rate limits, and strict validation.
Audit submissions are explicit and privacy-preserving with truncated and HMAC-hashed network data.
FAQ
No. Veilo hosts the interface, docs, and compliance endpoints. Transfers run via browser, local bridge, or your own remote node.
No. Web Mode supports WebRTC-compatible swarms through WebTorrent. Classic TCP/UDP BitTorrent requires Local Bridge or Remote Node.
No. Route choice changes exposure, but Veilo does not guarantee anonymity, availability, or peer connectivity.
Contact / Compliance