# Everything Fenris does.

One list, in the order the idea unfolds: links, traffic, staying up, data, awkward networks, security, privacy, fleets, devices. Filter it by what you need, or by where it runs.

Need 

Runs on 

1. 001 [Every link at once](https://fenris.network/features/every-link-at-once)Wi-Fi, Ethernet, 4G and 5G modems and tethered phones all carry traffic together, up to 8 links a device, in one encrypted session to your server. Every device [](https://fenris.network/features/every-link-at-once)
2. 002 Links found and followed Plug in a phone or a modem and it joins; unplug it and the rest carry on. Bridges, Docker and other VPNs are never taken for internet links. Every device
3. 003 [One download over every link](https://fenris.network/features/one-download)A single download, not only many at once, gets the links’ combined capacity, for every app on every device behind the router. Every device [](https://fenris.network/features/one-download)
4. 004 Each connection on its best link Calls, games and name lookups each stay on the quickest link, spread over several only when one isn’t enough. Every device
5. 005 Kinds of traffic Each connection is sorted on the device into calls and live video, interactive, downloads or background. The server is told, so what comes back follows the same plan. Every device · Server
6. 006 Downloads as good as uploads Your server schedules what it sends back over your links with the same care as your device schedules what it sends. Every device · Server
7. 007 Slow-link guard A link far slower than the rest is kept from holding a download back. Turn the guard off and every link carries everything. Every device
8. 008 Profiles Balanced, Max speed, Low latency or Data saver: one choice sets how your links are used. Every device
9. 009 Speed and Redundant modes Speed uses every link at once. Redundant sends every packet on every good link, both ways, at about one link’s speed. Every device
10. 010 Steady lane for HTTP/3 While two or more links are up, video sites that use QUIC fall back to TCP, which Fenris spreads over every link. Router
11. 011 Downloads give way A big download yields to page loads on the same session, so a page doesn’t queue behind it. Every device
12. 012 Every core used On a multi-core router or PC, a busy session spreads its downloads over up to four extra connections, each on its own core. Router · Windows · Linux
13. 013 Weak uploads don’t choke downloads Devices acknowledge less often, as the server asks, so a phone’s thin upload isn’t clogged by a fast download. Every device · Server
14. 014 Congestion control per link Each link gets its own congestion control, so one bad link doesn’t slow the others. Every device
15. 015 Your rules Send traffic to chosen addresses, ports, protocols or marks over chosen links, as a chosen kind, with or without copies. The first match wins. Every device
16. 016 Rules by app or website Pick an app or a website, and choose its links or its exit. Router · Android · Windows · Linux
17. 017 Background traffic Mark traffic as background and it takes the slowest link that isn’t metered, behind everything else. Every device
18. 018 Time-of-day policies Use a link only at the hours you choose, such as 4G only during work hours. Every device
19. 019 Priority by traffic mark A priority for each DSCP mark, and a fixed-delay option for live streams that prefer smooth to quick. Every device
20. 020 Shared-line warning Warns when two links share one upstream, such as two SIMs on one tower, so you know they can’t add up. Every device
21. 021 [Copies of calls on a second link](https://fenris.network/features/calls)A call’s packets also go on another link, and whichever arrives first is used. Every device [](https://fenris.network/features/calls)
22. 022 [Repairs for video calls](https://fenris.network/features/calls)Fast real-time traffic gets repair data on another link that rebuilds lost packets without a resend: up to 8 repairs for a group of 20. Every device [](https://fenris.network/features/calls)
23. 023 [Short queues while a call is on](https://fenris.network/features/calls)While a call, a game or a name lookup is running, busy links keep a shorter queue where that cuts the wait behind a download. Every device · Server [](https://fenris.network/features/calls)
24. 024 Spare copies dropped Once one copy arrives, copies still waiting are cancelled, so they don’t waste the link. Every device
25. 025 Copies within an allowance On a metered link, copies and repairs stop for the day once they have used the allowance you set. Every device
26. 026 Call and stream quality test A built-in test of a call’s or a stream’s quality, with what Fenris saved. Every device
27. 027 [A link drops, the others carry it](https://fenris.network/features/failover)Each link’s health is watched both ways. When one goes silent, its traffic moves to the others and open connections carry on. Every device [](https://fenris.network/features/failover)
28. 028 Links come back by themselves A link that returns rejoins on its own. One that keeps flickering is held back a while. Every device
29. 029 Drops absorbed, counted The app and the console count each time a link went quiet while the others carried on. Every device · Console
30. 030 [Starlink’s 15-second beat](https://fenris.network/features/starlink-beat)A link whose delay jumps every 15 seconds, as a Starlink dish’s does, is known from its own round trips, and calls step around each jump. Every device · Server [](https://fenris.network/features/starlink-beat)
31. 031 Dish and modem stats Signal and dish health, shown in the app and used by the scheduler. Restart a modem or stow a dish from the app. Router
32. 032 After sleep When a laptop or router wakes, Fenris checks its links at once and starts a fresh session beside the old one. Every device
33. 033 Speed test per link Measures each link alone against your own server, then all together, by hand or on a schedule. Metered links only if you ask. Every device
34. 034 Why each link is used Every link shows its role, its state and a plain reason, such as “used when the others are busy”. Every device
35. 035 Links with only IPv6 A link with only IPv6, as some cellular modems and fibre lines have, still carries traffic, and reaches an IPv4 server through NAT64. Every device
36. 036 A backup server A second server takes over once the first hasn’t answered for 10 seconds, and the first takes back as soon as it answers. Every device · Server
37. 037 [Link roles](https://fenris.network/features/link-roles)Always, Secondary, Backup or Never: a link is used all the time, when the others are busy, only if they fail, or not at all. Every device [](https://fenris.network/features/link-roles)
38. 038 [Metered links](https://fenris.network/features/link-roles)Phones and cellular modems are treated as metered by themselves: no copies or repairs unless you allow it, and quiet when idle. Every device [](https://fenris.network/features/link-roles)
39. 039 [Monthly cap and billing day](https://fenris.network/features/link-roles)Set a cap and the day the plan renews. At the cap the link turns off, or keeps 1 Mbit/s if you choose. Every device [](https://fenris.network/features/link-roles)
40. 040 Speed limits per link Hold a link to a speed each way, or keep downloads or uploads off it while another link works. Every device
41. 041 Usage, always counted What each link carried today, this week, this month and all time, through Fenris or not. Every device
42. 042 Caps in the console Admins see each metered link against its cap, and where each device’s month is heading. Console
43. 043 Cost per link A price per GB for each link, with spend estimates and budget alerts. Every device · Console
44. 044 A day’s boost Raise a cap for one day, or reset a link’s counters. Every device
45. 045 [Captive portals](https://fenris.network/features/awkward-networks)Hotel or airport Wi-Fi stuck at a sign-in page is found and kept out of the bond. One device gets through to sign in, then the link joins. Router · Windows · Mac · Linux [](https://fenris.network/features/awkward-networks)
46. 046 Network profiles On a given Wi-Fi or wired network, Fenris changes the profile and link roles by itself, such as marking a phone’s hotspot as metered. Every device
47. 047 Trusted networks On wired networks you list, traffic goes direct if your server can’t be reached for 30 seconds, instead of staying blocked. Router · Windows · Mac · Linux
48. 048 Direct while alone While only one link works, new connections go straight out of it, since the detour gains nothing. The tunnel returns when a second link does. Every device
49. 049 Bond only some traffic Only traffic to destinations you list takes the tunnel. The rest leaves directly. Router · Windows · Linux
50. 050 Direct, outside the tunnel Chosen devices on the LAN, destinations or whole domains go directly, outside the tunnel. Router · Windows · Linux
51. 051 Apps outside the tunnel Pick apps that go direct, not through Fenris. Android · Windows · Linux
52. 052 Home devices stay reachable With Fenris on, printers, casts and file shares at home still work. Every device
53. 053 Share a PC’s tunnel A Windows PC can share its bonded tunnel, for example through its Mobile Hotspot. Windows
54. 054 Outbound block rules Your own block and allow rules, on the device. Every device
55. 055 QUIC on UDP 443 The tunnel runs on the port most networks leave open. Every device · Server
56. 056 [TLS on TCP 443 where UDP is blocked](https://fenris.network/features/awkward-networks)A link whose UDP gets no answer in 3 seconds runs as TLS on TCP 443, still part of the same session, and tries UDP again every 5 minutes. Every device · Server [](https://fenris.network/features/awkward-networks)
57. 057 Domain mode Give your server a name: it gets and renews its own certificate, devices pin its key, and anyone else sees an ordinary website you choose. Server
58. 058 Console by name In domain mode, enrolled devices open the console at your server’s own name, through their tunnels. Console
59. 059 IPv4 and IPv6 IPv6 goes through the tunnel when your server has it, and is refused at once otherwise, so it never leaks. Every device · Server
60. 060 Your server answers your DNS Every device’s lookups go to your server, which can ask its upstream over TLS, QUIC or HTTPS. Answers are kept in memory only. Every device · Server
61. 061 Versions that agree Each end says which versions it speaks. A mismatch names the side to update, and an old device still gets a session to update itself. Every device · Server
62. 062 [Post-quantum key exchange](https://fenris.network/features/post-quantum-keys)The tunnel’s keys are agreed with X25519MLKEM768, with no classical-only fallback. TLS 1.3 only, with no resumption. Every device · Server [](https://fenris.network/features/post-quantum-keys)
63. 063 [Keys that roll](https://fenris.network/features/post-quantum-keys)Traffic keys are replaced every 2 minutes or every gigabyte, whichever comes first. Every device · Server [](https://fenris.network/features/post-quantum-keys)
64. 064 No certificate authorities Each device knows its server’s keys, and the server knows each device’s. Every device · Server
65. 065 [A silent server](https://fenris.network/features/silent-server)Every connection’s first packet must carry a one-use proof only that device can make. Scanners, replays and revoked devices get no reply on the UDP port. Server [](https://fenris.network/features/silent-server)
66. 066 Unlinkable first packets An observer can’t tell two connections of one device from two devices by the proof they carry. Every device · Server
67. 067 Connects without a synced clock A device whose clock is wrong or reset still connects. Nothing leaves outside the tunnel to set the clock first. Every device
68. 068 Keys made on the device A device makes its own keys, and they never leave it. They are held in the system’s keystore, or in hardware where the device has it. Every device
69. 069 Device keys that renew A device’s keys are replaced on a schedule. Every device
70. 070 Join with a one-time link A short code or its QR code, good once and for 24 hours. Both sides show the code, so you can check that they match. Every device · Console
71. 071 Root key kept offline The server’s master key can be sealed with a passphrase and taken off the server. Working keys renew every 30 days. Server · Console
72. 072 Rotate the device secret After a suspected compromise, the server’s token key is replaced and pushed to every device, with no enrolling again. Server
73. 073 Revoke in a click Cut a lost device off at once, one or many. Its sessions close within seconds and its number is never reused. Console
74. 074 [Kill switch from boot](https://fenris.network/features/kill-switch)While Fenris is on, nothing leaves outside the tunnel: not while connecting, not after a crash, not during an upgrade. Every device [](https://fenris.network/features/kill-switch)
75. 075 [No leaks](https://fenris.network/features/kill-switch)DNS is forced into the tunnel, and IPv6 your server can’t carry is refused. Every device [](https://fenris.network/features/kill-switch)
76. 076 Consent for weaker settings A server can’t silently turn off a device’s kill switch or open a way around the tunnel. Every device
77. 077 Your server guards its own network Devices can’t reach private networks, cloud metadata addresses or the server itself through it, unless you allow one. Server
78. 078 [Signed releases](https://fenris.network/features/updates-you-control)Every release is signed with a yearly key that one of two offline root keys certifies. Devices refuse anything else. Every device · Server [](https://fenris.network/features/updates-you-control)
79. 079 [Updates from your own server](https://fenris.network/features/updates-you-control)Your server holds a release and offers it. Devices fetch it through the tunnel, install at a quiet moment, and go back if the new one can’t reach the server. Every device · Server [](https://fenris.network/features/updates-you-control)
80. 080 Supply chain A bill of materials with every program, every dependency vetted, and a check that a release builds to the same bytes. Every device · Server
81. 081 Checked by machines Formal models of the silent proof and of enrolment, 17 fuzz targets over every parser, and conformance tests for the crypto profile. Every device · Server
82. 082 A locked-down console It listens only on the server and the tunnel. Five wrong codes pause sign-in for 15 minutes, and risky actions ask again. Console
83. 083 Least privilege The services run sandboxed, with only the network capabilities they need. Router · Linux · Server
84. 084 [No company in the middle](https://fenris.network/features/your-own-server)Your devices only ever talk to your own server. No Fenris server carries, sees or counts your traffic. Every device · Server [](https://fenris.network/features/your-own-server)
85. 085 No telemetry Nothing phones home, and crash records stay on the machine. Every device · Server
86. 086 [Never written down](https://fenris.network/features/privacy-you-can-read)Your server never records the sites you visit, the names you look up or what is inside your traffic. Server [](https://fenris.network/features/privacy-you-can-read)
87. 087 [What your server keeps, in the app](https://fenris.network/features/privacy-you-can-read)Every app has a page that lists what the server it has joined keeps, item by item, with how long. Every device [](https://fenris.network/features/privacy-you-can-read)
88. 088 Bug reports that hide you One file to send for help, with addresses and names replaced unless you ask for them. Every device
89. 089 [Every device’s links, side by side](https://fenris.network/features/the-console)Each device’s links with their share of the traffic, charted under the bonded total, second by second and over the last day or week. Console [](https://fenris.network/features/the-console)
90. 090 [Devices by name](https://fenris.network/features/the-console)Every device with what it runs, where it connects from, its links and its log. Filter by online, offline, needs attention or due an update. Console [](https://fenris.network/features/the-console)
91. 091 Add a device Make a one-time link or QR code for a named device, and see or withdraw the ones not used yet. Console
92. 092 Alerts Raised when a device stays offline or runs short of its usual links, a key is about to run out, or the server runs short of CPU or disk. Console
93. 093 Alerts where you are By webhook to Slack, Mattermost and most chat tools, and by email, always encrypted. Console
94. 094 Alert rules and snooze Pick which alerts fire, set their thresholds, and snooze one. Console
95. 095 Usage by device The data each device received and sent, day by day. Console
96. 096 [A full audit trail](https://fenris.network/features/the-console)What happened, who did it and how they signed in, from which address, and what changed, field by field. Export it, or stream it to syslog. Console [](https://fenris.network/features/the-console)
97. 097 Admins, sessions and API tokens Several admins, a list of who is signed in, and tokens for scripts, read-only or with changes. Console
98. 098 Passkeys Admins sign in with a passkey, or a six-digit authenticator code when a passkey isn’t to hand. Console
99. 099 Roles and single sign-on Owner, admin, network admin, auditor and member, with sign-in through Google, Authentik or Keycloak. Console
100. 100 Policies Settings by group, drafted, previewed and deployed, with the ones you lock. Console
101. 101 Fleet analytics and bulk actions Health and drops across the fleet. Act on many devices at once, and export or import them as CSV. Console
102. 102 Enrolment keys with approval One key for a batch of devices, limited and expiring, each device approved by an admin. Console
103. 103 Managed device profiles Ship Fenris’s settings to company devices through your device manager. Android · Windows · Mac
104. 104 Keys and backup A backup sealed with a passphrase, restored on a new server without enrolling devices again. Console · Server
105. 105 [Port forwarding](https://fenris.network/features/port-forwarding)Open a TCP or UDP port on your server to a device, or to a computer behind a router. The device sees each caller’s own address. Router · Console · Server [](https://fenris.network/features/port-forwarding)
106. 106 Exits Every device’s traffic leaves through your server. Chosen devices, apps or destinations can leave through another server, or a device at home. Console · Server
107. 107 [Device release](https://fenris.network/features/updates-you-control)See the release your server offers and which devices run it. Devices update when they next connect. Console [](https://fenris.network/features/updates-you-control)
108. 108 Server at a glance Its name and place, certificate and addresses, and the host’s CPU, memory, disk and monthly traffic. Console
109. 109 Prometheus and Grafana Metrics on the server itself, and ready-made dashboards for server and client. Server
110. 110 A pool of servers Several servers share one identity, so a device moves between them without enrolling again. Server
111. 111 One console for many servers Manage several servers and exits from one place. Console
112. 112 Site-to-site Route between the LAN behind a router and your server’s networks. Router · Server
113. 113 Move a server Restore the sealed backup on a new machine, and every device follows. Server
114. 114 [Router UI](https://fenris.network/features/whole-home-from-one-router)On your LAN: Home, Links, Activity, Usage, Servers, Rules, Diagnostics and Settings, in light and dark, sized for a phone too. Router [](https://fenris.network/features/whole-home-from-one-router)
115. 115 [OpenWrt package](https://fenris.network/features/whole-home-from-one-router)For OpenWrt 25.12 and later, with a LuCI page. Every WAN is bonded, and settings survive a sysupgrade. Router [](https://fenris.network/features/whole-home-from-one-router)
116. 116 [Linux router](https://fenris.network/features/whole-home-from-one-router)A Raspberry Pi or any Linux box bonds every interface that has a default route, for the LAN behind it. Router [](https://fenris.network/features/whole-home-from-one-router)
117. 117 Android app Join by QR code. Wi-Fi and mobile data bonded at once, a notification with what Fenris carries, and a quick-settings tile. Android
118. 118 Windows app A service with its own installer and a tray. Connections are named by program. Windows
119. 119 Mac app and command line The app with the same screens, or one line in Terminal that runs Fenris from boot. Mac
120. 120 Linux app deb and rpm packages with the service and a tray, updated by your package manager. Linux
121. 121 Tray Connected, Connecting, Holding traffic or Off, at a glance. Quitting the tray leaves you protected. Windows · Mac · Linux
122. 122 The fenris command line status, top, links, flows, speedtest, check and more, with JSON for scripts. Router · Windows · Mac · Linux
123. 123 One command for a server The installer checks the release’s signatures down to the built-in roots, installs the service and the console, and prints the first invite link. Server
124. 124 One line for a device One line installs Fenris on a Mac or on Linux and asks for the invite link. Mac · Linux
125. 125 Store and package channels Google Play, F-Droid, Homebrew and winget. Android · Windows · Mac
126. 126 Lower idle power Less waking when idle, for devices on battery. Android · Windows · Mac · Linux

of 126 capabilities

## Not on the list?

Then Fenris doesn’t do it. Some of what it leaves out is on purpose: it won’t make one link faster, it isn’t built to get around censorship, and it needs a server you run.

[How it works](https://fenris.network/how-it-works)[Questions and answers](https://fenris.network/faq)[hello@fenris.network](mailto:hello@fenris.network)
