Own Your Player
Architecture

How it works

Three components, each with a narrow job. The design goal: your music and your listening never need to sit on anyone else's server, and your home network never needs to accept inbound connections.

Library your PC, mini PC or NAS indexes · enriches · serves Gateway web player · sign-in rendezvous · STUN · relay Phone · tablet · PC any modern browser Car in-car browser outbound connection — direct, end-to-end encrypted audio    - - - signalling and fallback relay
1 · At home

The library

A small service next to your music. It reads the files in place, builds the index, finds missing artwork and lyrics, and answers requests from paired devices. It only ever makes outbound connections — exactly like a browser does.

2 · In the cloud

The gateway

Hosts the web player and the sign-in, and keeps an authenticated connection to your library. It introduces your devices to your library and, only when a direct link is impossible, streams the audio through in memory, without storing it.

3 · With you

The player

A progressive web app: installable on the home screen, integrated with lock-screen and car controls, with a local cache that keeps playback going through network drops.

A play, step by step

What happens when you press play

The player asks for a direct link

Your browser creates a WebRTC offer and sends it to the gateway, which forwards it to your library over the connection the library already holds open.

Both ends find a path

Using STUN, each side discovers how it is reachable from the internet. ICE then tries candidate paths — same local network, direct across the internet, or through NAT traversal — and picks the best one that works.

Audio flows directly

The track travels over an encrypted DTLS data channel from your library to your device. The gateway sees neither the audio nor which track it is.

Fallback, without fuss

On networks that block peer-to-peer traffic, such as some mobile carriers and corporate Wi-Fi, playback goes through the gateway instead: the library sends the track over its encrypted link to the gateway, which passes it on over HTTPS without keeping a copy. Because the gateway is software you run, that detour still stays within infrastructure you control.

The next song is already there

While a track plays, the next one downloads in the background and is kept on the device, so the hand-over is immediate and survives a lost signal.

No port forwarding

Why your router stays closed

Traditional home media servers ask you to forward a port, set up dynamic DNS and expose a service to the whole internet. Each of those is a maintenance task and an attack surface.

Here, the library dials out to the gateway and keeps that connection alive. Nothing on the internet can initiate a connection into your home; the only parties that can talk to your library are devices you paired with it.

Typical home serverOwn Your Player
Inbound port on the routerRequiredNone
Dynamic DNSUsuallyNot needed
Works behind carrier-grade NATRarelyYes
Audio path when possibleDirectDirect
Audio path when blockedFailsEncrypted relay