# Your server, your fleet.

A shop, a clinic, a van or an event desk rarely has only one way online. Fenris keeps each of them on every link it has, and you run all of them from one console on a server you own.

[See the console](#console)[Talk to us](#talk)

_Example:_ 

An example fleet: each device sends its traffic over every link it has to one server you own. Your server reaches the internet from its own address. No company's server is in the path.

Four made-up fleets. Each device brings its own links, and all of them meet at one server. A site’s router or a single phone counts the same: one device in your console.

## One console for all of them.

It runs on your server and opens only for devices that have joined. Every page does one job. These are its own screens.

Every device by name, with its links: carrying, on standby or missing. Its links side by side, by their share of the traffic. One is missing here, and the other two carry on. Raised when a device stays offline or runs short of its usual links, naming the missing one. Sent by email or webhook. Who did what, how they signed in, from which address, and how it ended. Device sessions too. A one-time link or QR code for a named device. It works once.

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

The console’s page for one device, the home router: its links side by side by their share of the traffic, with one of the three missing.

The console’s Alerts page: the alerts that are open, each naming its device and the link that is missing.

The console’s Audit log: one row for each action, with who did it, how they signed in, from which address, and how it ended.

The console’s Add a device page: a one-time link and its QR code for a named device.

**The console** Its own pages, with example data. The others: Overview, Live, Usage, Routing, Server, Access, Keys & backup.

## Add a device, cut one off

No accounts to hand out and no passwords to share. A device joins with a link that works once, and leaves the moment you say so.

1. You name the device in the console and get a one-time link, or its QR code. It works once, for 24 hours unless you choose otherwise.
2. The device opens the link and makes its own keys. They never leave it.
3. Both sides show the same short code. Carry on only if they match.
4. A lost device is revoked in a click. Its sessions close within seconds, and its number is never used again.

fenris://203.0.113.7/KQ2XM-4P9TB-N3VWA-6HFJZ

**Example** What a one-time link looks like. For a batch of devices, one key can enrol many: limited, expiring, and each device approved by an admin.

## What an admin can see

[Everything your server keeps](https://fenris.network/privacy#kept)

Tell your people this before they join. Every app shows the same list, for the server it has joined.

**Seen** Each device’s name, what it runs, its links and the public address of each, when it connected, and how much data it used each day.

**Never recorded** The websites anyone visits, the names they look up, or what is inside their traffic. Usage is counted by device, never by website or app.

**Not ours to see** No Fenris server is in the path, and there is no account with us. The only server is yours.

## Running a fleet

**Alerts where you are**

By webhook to Slack, Mattermost and most chat tools, and by email, always encrypted. They resolve by themselves.

**Sign-in**

A passkey, or a six-digit authenticator code. Five wrong codes pause sign-in for 15 minutes. Or your own single sign-on.

**Roles**

Owner, admin, network admin, auditor and member, so the person who reads the audit log need not be able to change anything.

**Policies**

Settings by group, with the ones you choose locked. Drafted, previewed, then deployed.

**Updates you control**

Your server holds the release. Devices fetch it through their tunnels, install it at a quiet moment, and go back to the old version if the new one can’t reach the server.

**A backup server**

A second server takes over when the first has not answered for 10 seconds. Open connections end at each change, as traffic then leaves from another address.

**Moving house**

Restore the sealed backup on a new machine and every device follows, without joining again.

**Scripts and monitoring**

API tokens, read-only or with changes, shown once and kept only as hashes. Prometheus metrics, with ready-made Grafana dashboards.

## Who runs what

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

**The server** You do. A small Linux server in a cloud region near you, or a machine on your premises with a public address.

**Each site** A router running OpenWrt or Linux bonds everything behind it. A van’s router is a site like any other.

**Each person** The app on a computer or a phone bonds that device’s own links.

**The price** Free during early access.

## Talk to us

Tell us how many places, which links, and what has to stay up. A person reads it and replies.

[hello@fenris.network](mailto:hello@fenris.network)

 Stored 

Thanks. We’ve got it.

A person reads it and replies, from hello@fenris.network.
