All engineering notes
November 20, 2026·6 min read·Maizor Engineering

How We Built Send Files Anywhere: Zero-Storage P2P Relay Architecture

A deep dive into our ephemeral file transfer engine: WebRTC DataChannels, in-memory chunking, and zero persistent storage.

#WebRTC#Security#Architecture#P2P

The Problem with Conventional File Transfer

Most file-sharing services (WeTransfer, Google Drive, Dropbox) operate on an upload-and-store model. When you send a file, it is written to persistent cloud disks, scanned by indexing workers, and stored for days or weeks. Even services claiming 'ephemeral' transfers often retain data on multi-tenant disk volumes until scheduled cleanup cronjobs run.

For confidential documents, 4K production footage, and sensitive client assets, saving copies to third-party storage introduces unnecessary risk. We designed Send Files Anywhere around a fundamental principle: files should stream directly between devices, and if a relay is necessary, data must exist only in volatile server memory (RAM) while in-flight.

Direct Peer-to-Peer via WebRTC DataChannels

Whenever two devices can discover each other, Send Files Anywhere negotiates a direct WebRTC DataChannel using STUN/TURN signaling. Once the peer connection is established, file chunks stream directly over encrypted DTLS channels from the sender's browser to the receiver's browser.

Because the data never touches our servers in P2P mode, transfer speeds are limited only by the local network or internet connection between the peers. There are no arbitrary upload caps, no queueing delays, and zero storage overhead.

// WebRTC DataChannel initialization for chunked file streaming
const peerConnection = new RTCPeerConnection({
  iceServers: [{ urls: "stun:stun.l.google.com:19302" }]
});

const dataChannel = peerConnection.createDataChannel("file-transfer", {
  ordered: true
});

dataChannel.binaryType = "arraybuffer";
dataChannel.onopen = () => console.log("P2P encrypted tunnel active");

In-Memory Ephemeral Relay Fallback

In strict enterprise networks, symmetric NAT firewalls often prevent direct peer-to-peer hole-punching. Rather than failing the transfer, Maizor falls back to an ephemeral in-memory relay.

Unlike traditional file hosts, our relay does not write chunks to SSDs, NVMe drives, or persistent databases. Chunks are buffered in RAM buffers just long enough for the receiver's WebSocket or HTTP stream to consume them, and immediately deallocated. Once the room closes or the transfer finishes, all memory pointers are scrubbed.

Ephemeral Single-Use Rooms

Every session is encapsulated in a random 6-character room code. Rooms carry strict TTL (time-to-live) constraints: if no receiver connects within 10 minutes, or as soon as all queued files have been acknowledged as downloaded, the room is destroyed.

No user accounts, no email logs, and no persistent telemetry cookies are attached to the session. You generate a code, send the payload, and leave no trace behind.

Try the tool

Experience Send Files Anywhere

Transfer files securely between any two devices with zero disk retention.

Open tool
Maizor

AI-powered technology platform. In early development.

4 Sayat-Nova Ave, Yerevan 0070
Armenia

© 2026 Maizor. All rights reserved.