# One connection over every link you have.

Fenris joins your fibre, your 5G and your phone into one connection, through a server you run. A download uses all of them. A link drops, the others carry it.

[How it works](https://fenris.network/how-it-works)

An example home with three links: fibre, a 5G box and a phone. Each carries a share of one bonded connection to your server. A call rides the fibre with a copy on the 5G, and a download is spread over every link. Switch a link off and the others carry its traffic.

_Three links of one home. A lane’s width is its share of the traffic. Nothing here is a measurement._

## One at a time.

Today a device picks one link and leaves the rest idle. A failover router does the same: it waits for that line to die, then switches, and everything you had open starts again.

Three links: the fibre is in use; the 5G and the phone are idle.

## Every link at once.

With Fenris every link carries traffic, all the time. Together they are one connection, so when one goes quiet the others carry on with what was open.

Three links: the fibre, the 5G and the phone are all in use.

[Bonding, failover and load balancing, compared](https://fenris.network/compare/bonding-failover-load-balancing)

## Each kind of traffic, its own way

A download wants as much as it can get. A call wants every packet on time. Fenris sorts each connection on your device and treats it on its own terms.

So a download is spread over every link, and a call stays on the quickest one, with a copy on a second. One link alone is never made faster.

[How each kind is handled](https://fenris.network/how-it-works#kinds)

A download is spread over every link. A video call stays on the quickest link, here the fibre, with a copy on a second, here the 5G. A game takes the quickest link, here the fibre. A backup, marked as background, takes the slowest link that is not metered, here the 5G.

**Example** Three links. Which one is quickest changes as they run.

## Your server, not ours.

Your devices only ever talk to a server you run. Fenris has no server between you and the internet, and no account to sign in to.

Your devices reach your server through one encrypted tunnel over every link. Your server reaches the internet from its own address. No company's server is in the path.

The server is a small Linux machine you rent or own, set up with one command. You run it, so whoever hosts it can see what leaves it, as your provider does today. We never see your traffic.

[Run your server](https://fenris.network/download#server)

## Made for the internet you actually have.

Say it is 7:40 on a weekday evening and the power goes. Your router stays up on the inverter, but the fibre goes quiet: the equipment down the street has lost power too.

The 5G takes a different road, and it was already carrying traffic. The class on video carries on. The phone was set as a backup, so its data pack is left alone.

Towers lose power too. Two links that fail for different reasons seldom fail together, and that is what bonding needs.

An example evening from 7 to 9 pm. At 7:40 the power goes and the fibre goes quiet until 8:25\. The 5G carries everything in between. The phone, set as a backup, is not used. The one connection never breaks.

**Example** One evening in a home with fibre, a 5G box and a phone. The times are made up.

The same idea, wherever links are shaky

## Where it runs

On the router, for the whole home or office, or on each device by itself.

[Download](https://fenris.network/download)

**A router**

OpenWrt 25.12 or newer, or a Linux box such as a Raspberry Pi. 64-bit ARM or x86.

**Android**

Android 10 or newer.

**Windows**

Windows 10 or 11, 64-bit.

**Mac**

The app, or the command line from one line in Terminal.

**Linux**

Ubuntu 22.04, Debian 12 or Fedora, and newer.

**Your server**

Linux 5.15 or newer, a public address, UDP 443 open.

## Every device, from one console

[Teams](https://fenris.network/teams)

A shop, an office, a few vans. Each device by name, its links side by side, on a server that is yours.

The console’s Devices page, with example data: six devices by name, each with its state, its links, its throughput, its use today and its version.

**The console** Its Devices page, with example data.

## Security in four facts

[Security](https://fenris.network/security)

**Post-quantum keys** The tunnel’s keys are agreed with a post-quantum exchange, with no classical-only fallback, and replaced every 2 minutes.

**A silent server** Your server answers only devices you enrolled. A scan of its UDP port gets no reply.

**Keys stay on the device** Each device makes its own keys, and they never leave it. Revoke a lost device and its sessions close within seconds.

**Kill switch from boot** While Fenris is on, nothing leaves outside the tunnel: not while it connects, not after a crash, not during an upgrade.

## What it won’t do

[Questions and answers](https://fenris.network/faq)

1. It won’t make one link faster.Bonding uses the links you have. With a single link, Fenris is an encrypted tunnel to your server and nothing more.
2. Wi-Fi and Ethernet to the same router are one line.They share the one connection behind it, so together they add nothing. Links must reach the internet by different roads.
3. It needs a server, and you run it.The pieces of a download have to meet again somewhere. That place is yours, not ours.
