Skip to the page
FenrisEarly access

Updates you control.

Every release is signed, and your devices take updates only from your own server, through the tunnel. A device that can’t reach your server on the new version goes back to the old one.

Every deviceYour serverOn by default

One update, on one device

The device waits for the call to end, then installs.

The new version can’t reach your server, so the device goes back to the old one by itself.

Fig. 1Not to scale. The offer comes through the tunnel, from your own server.

What happens

  1. Every release is signed with a yearly key, which one of two offline root keys certifies. Every device has the roots built in.
  2. Your server fetches a release when you tell it to, checks every signature and every file, and holds it.
  3. Devices are offered it in their sessions, and fetch it through the tunnel. They refuse anything unsigned, an older version, or an offer that has run out.
  4. A device installs it at a quiet moment. It waits out a call.
  5. If the new version can’t reach your server, the device goes back to the old one.

What it costs

You decide when, so an update waits for you.

Your part
A new release reaches your devices only once your server holds it. Until you fetch it, they stay on the one they have.
Data
Each device downloads the release through the tunnel, over its own links. On a metered link, that is plan data.
A pause
Installing restarts Fenris on that device. It picks a quiet moment, and the kill switch holds through it.

Turn it on

Devices update by themselves once your server holds a release. These are your part.

ToCommand lineThe console and the app
Fetch the latest release to your serverfenris-server release fetch --state /var/lib/fenris-serverThe console, Server, Device release
See the release your server holdsfenris-server release show --state /var/lib/fenris-serverThe console, Server, Device release
See which devices are due an updatefenris-server devices --state /var/lib/fenris-serverThe console, Devices, Update due
On a device, see what your server offersfenris update --checkThe app, Settings, About Fenris

Where to find it

The consoleDevices. Each device’s version, and which are due an update.

The productOne of its own screens, with example data.

What it keeps

The release itself, and the version each device runs: the latest only, until the device is revoked. A line goes in the device’s log each time it is updated.

Where it stops

The first install
It comes from a download, not from your server. The installer checks each file against the same built-in keys before anything runs.
Stores and packages
An app from a store, and a Linux package, are updated by the store or the package manager, not by your server.
Holding back
Signatures stop your server, or anyone who takes it over, from handing devices a program Fenris did not release. They can’t stop it from withholding an update.
Who you trust
You still trust the keys that sign the releases. Every dependency is vetted, and a release is checked to build to the same bytes.