Magic Portal transfer engine

Move giant files directly between devices. No cloud staging.

Native gives prosumers a serverless P2P transfer rail built on WebRTC. The one-way Magic Portal watches your source folder and pushes only new or changed files in efficient 64KB chunks, with flat memory usage even on 50GB+ sends.

Get on GitHub See transfer flow

AES-GCM at rest in transit Ephemeral signaling IDs TURN fallback for strict NAT

One-way by design

No bidirectional sync conflicts and no battery-heavy indexing loops.

Direct P2P payload path

Signaling only brokers session metadata. File bytes stay device-to-device.

Massive-file stability

Chunked streaming keeps RAM flat while pushing large multi-GB archives.

Self-host ready

Run your own signaling layer when compliance or residency rules demand it.

How it works

Native keeps the transfer model intentionally narrow: fast, one-way delivery with no sync graph and no hidden cloud persistence.

Step 01

Ephemeral handshake

A lightweight signaling backend exchanges short-lived connection metadata, then removes stale IDs automatically.

Step 02

Secure direct channel

Devices establish a WebRTC data channel with encrypted transport and no middlebox payload inspection.

Step 03

Streamed chunk transfer

Files are pushed in 64KB segments with resumable progress, preserving memory and reliability on large sends.

Built for developers and privacy-first teams

Run Native as a desktop utility or integrate the protocol into your own stack with configurable signaling and TURN strategy.

Developer workflow

Embed transfer primitives in Tauri, Electron, or browser tooling with minimal client-side ceremony.

Ops and compliance

Self-host signaling and audit connection events without storing payload content or cloud file copies.

Open source core

MIT licensed and designed for inspectability, from signaling flow to transfer pipeline behavior.