Skip to the page
FenrisEarly access

No company in the middle.

Your devices only ever talk to a server you run. No Fenris server carries, sees or counts your traffic, and there is no account to sign in to.

Every deviceYour server

Who is in the path
Fig. 1Either way a server opens the tunnel. The difference is whose it is.

What happens

  1. You rent or own a small Linux server, and install Fenris on it with one command.
  2. Each device joins it with a one-time link. The keys are made on the device and on your server. No company holds a copy.
  3. Every link’s traffic goes to your server, sealed, and nowhere else.
  4. Your server reaches the internet as you. Websites see its address, the same one whichever link carried the traffic.
  5. Nothing phones home. No telemetry and no account, and crash records stay on the machine.

What it costs

It is yours, so running it is yours too.

Your time
You set it up once and keep it running. It is like any small cloud server: make a machine, open a port, run the installer.
Its bill
You pay whoever hosts it. Watch the data allowance more than the processor: everything you download leaves your server towards you.
One address
An address that is yours alone is less anonymous than a VPN’s shared one. Fenris is for steadiness and speed, not for hiding who you are.
If it stops
With one server, the kill switch holds your traffic until it answers. List a second, and devices move to it after 10 seconds.

Turn it on

Run a server, then join each device to it.

ToCommand lineThe console and the app
Install your servercurl -fsSL https://dl.fenris.network/get.sh | sh -s -- --address <public IP>:443 --admin <your name>On your server
Make a one-time link for a devicefenris-server invite --state /var/lib/fenris-server --address <public IP>:443The console, Add a device
Join a devicefenris join '<invite link>'The app: paste the link, or scan its QR code
See which server a device has joinedfenris statusThe app, Servers
Move your server to a new machinefenris-server backup --state /var/lib/fenris-server --out <file>The console, Keys & backup

Where to find it

The consoleAdd a device. A one-time link for one named device.

The appHome. Protected, through a server of your own.

The consoleA device’s page, on your server and nowhere else.

The productThree of its own screens, with example data.

What it keeps

What a server must, and only on your server: that a device is enrolled, its links, each session in the audit log for a year, and daily usage for about 400 days. None of it reaches us.

Where it stops

Whoever hosts it
Whoever hosts your server can see what leaves it, as an internet provider does today. No company sits in the path, but that is not the same as nobody being able to look.
A public address
Your server needs a public address of its own, with UDP 443 open. Behind a provider’s shared address it can’t be reached.
Sites that distrust it
Some banks and streaming services distrust addresses that belong to a hosting provider. Such a site can be set to go direct, and then it gets no bonding.
What you still trust
The Fenris programs you run, and the keys that sign them.