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
- 001Every link at onceWi-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
- 002Links found and followedPlug 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
- 003One download over every linkA single download, not only many at once, gets the links’ combined capacity, for every app on every device behind the router.Every device
- 004Each connection on its best linkCalls, games and name lookups each stay on the quickest link, spread over several only when one isn’t enough.Every device
- 005Kinds of trafficEach 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
- 006Downloads as good as uploadsYour server schedules what it sends back over your links with the same care as your device schedules what it sends.Every device · Server
- 007Slow-link guardA link far slower than the rest is kept from holding a download back. Turn the guard off and every link carries everything.Every device
- 008ProfilesBalanced, Max speed, Low latency or Data saver: one choice sets how your links are used.Every device
- 009Speed and Redundant modesSpeed uses every link at once. Redundant sends every packet on every good link, both ways, at about one link’s speed.Every device
- 010Steady lane for HTTP/3While two or more links are up, video sites that use QUIC fall back to TCP, which Fenris spreads over every link.Router
- 011Downloads give wayA big download yields to page loads on the same session, so a page doesn’t queue behind it.Every device
- 012Every core usedOn 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
- 013Weak uploads don’t choke downloadsDevices acknowledge less often, as the server asks, so a phone’s thin upload isn’t clogged by a fast download.Every device · Server
- 014Congestion control per linkEach link gets its own congestion control, so one bad link doesn’t slow the others.Every device
- 015Your rulesSend 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
- 016Rules by app or websitePick an app or a website, and choose its links or its exit.Router · Android · Windows · Linux
- 017Background trafficMark traffic as background and it takes the slowest link that isn’t metered, behind everything else.Every device
- 018Time-of-day policiesUse a link only at the hours you choose, such as 4G only during work hours.Every device
- 019Priority by traffic markA priority for each DSCP mark, and a fixed-delay option for live streams that prefer smooth to quick.Every device
- 020Shared-line warningWarns when two links share one upstream, such as two SIMs on one tower, so you know they can’t add up.Every device
- 021Copies of calls on a second linkA call’s packets also go on another link, and whichever arrives first is used.Every device
- 022Repairs for video callsFast 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
- 023Short queues while a call is onWhile 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
- 024Spare copies droppedOnce one copy arrives, copies still waiting are cancelled, so they don’t waste the link.Every device
- 025Copies within an allowanceOn a metered link, copies and repairs stop for the day once they have used the allowance you set.Every device
- 026Call and stream quality testA built-in test of a call’s or a stream’s quality, with what Fenris saved.Every device
- 027A link drops, the others carry itEach link’s health is watched both ways. When one goes silent, its traffic moves to the others and open connections carry on.Every device
- 028Links come back by themselvesA link that returns rejoins on its own. One that keeps flickering is held back a while.Every device
- 029Drops absorbed, countedThe app and the console count each time a link went quiet while the others carried on.Every device · Console
- 030Starlink’s 15-second beatA 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
- 031Dish and modem statsSignal and dish health, shown in the app and used by the scheduler. Restart a modem or stow a dish from the app.Router
- 032After sleepWhen a laptop or router wakes, Fenris checks its links at once and starts a fresh session beside the old one.Every device
- 033Speed test per linkMeasures each link alone against your own server, then all together, by hand or on a schedule. Metered links only if you ask.Every device
- 034Why each link is usedEvery link shows its role, its state and a plain reason, such as “used when the others are busy”.Every device
- 035Links with only IPv6A link with only IPv6, as some cellular modems and fibre lines have, still carries traffic, and reaches an IPv4 server through NAT64.Every device
- 036A backup serverA 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
- 037Link rolesAlways, 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
- 038Metered linksPhones and cellular modems are treated as metered by themselves: no copies or repairs unless you allow it, and quiet when idle.Every device
- 039Monthly cap and billing daySet 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
- 040Speed limits per linkHold a link to a speed each way, or keep downloads or uploads off it while another link works.Every device
- 041Usage, always countedWhat each link carried today, this week, this month and all time, through Fenris or not.Every device
- 042Caps in the consoleAdmins see each metered link against its cap, and where each device’s month is heading.Console
- 043Cost per linkA price per GB for each link, with spend estimates and budget alerts.Every device · Console
- 044A day’s boostRaise a cap for one day, or reset a link’s counters.Every device
- 045Captive portalsHotel 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
- 046Network profilesOn 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
- 047Trusted networksOn 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
- 048Direct while aloneWhile 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
- 049Bond only some trafficOnly traffic to destinations you list takes the tunnel. The rest leaves directly.Router · Windows · Linux
- 050Direct, outside the tunnelChosen devices on the LAN, destinations or whole domains go directly, outside the tunnel.Router · Windows · Linux
- 051Apps outside the tunnelPick apps that go direct, not through Fenris.Android · Windows · Linux
- 052Home devices stay reachableWith Fenris on, printers, casts and file shares at home still work.Every device
- 053Share a PC’s tunnelA Windows PC can share its bonded tunnel, for example through its Mobile Hotspot.Windows
- 054Outbound block rulesYour own block and allow rules, on the device.Every device
- 055QUIC on UDP 443The tunnel runs on the port most networks leave open.Every device · Server
- 056TLS on TCP 443 where UDP is blockedA 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
- 057Domain modeGive 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
- 058Console by nameIn domain mode, enrolled devices open the console at your server’s own name, through their tunnels.Console
- 059IPv4 and IPv6IPv6 goes through the tunnel when your server has it, and is refused at once otherwise, so it never leaks.Every device · Server
- 060Your server answers your DNSEvery 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
- 061Versions that agreeEach 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
- 062Post-quantum key exchangeThe tunnel’s keys are agreed with X25519MLKEM768, with no classical-only fallback. TLS 1.3 only, with no resumption.Every device · Server
- 063Keys that rollTraffic keys are replaced every 2 minutes or every gigabyte, whichever comes first.Every device · Server
- 064No certificate authoritiesEach device knows its server’s keys, and the server knows each device’s.Every device · Server
- 065A silent serverEvery 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
- 066Unlinkable first packetsAn observer can’t tell two connections of one device from two devices by the proof they carry.Every device · Server
- 067Connects without a synced clockA device whose clock is wrong or reset still connects. Nothing leaves outside the tunnel to set the clock first.Every device
- 068Keys made on the deviceA 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
- 069Device keys that renewA device’s keys are replaced on a schedule.Every device
- 070Join with a one-time linkA 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
- 071Root key kept offlineThe server’s master key can be sealed with a passphrase and taken off the server. Working keys renew every 30 days.Server · Console
- 072Rotate the device secretAfter a suspected compromise, the server’s token key is replaced and pushed to every device, with no enrolling again.Server
- 073Revoke in a clickCut a lost device off at once, one or many. Its sessions close within seconds and its number is never reused.Console
- 074Kill switch from bootWhile Fenris is on, nothing leaves outside the tunnel: not while connecting, not after a crash, not during an upgrade.Every device
- 075No leaksDNS is forced into the tunnel, and IPv6 your server can’t carry is refused.Every device
- 076Consent for weaker settingsA server can’t silently turn off a device’s kill switch or open a way around the tunnel.Every device
- 077Your server guards its own networkDevices can’t reach private networks, cloud metadata addresses or the server itself through it, unless you allow one.Server
- 078Signed releasesEvery release is signed with a yearly key that one of two offline root keys certifies. Devices refuse anything else.Every device · Server
- 079Updates from your own serverYour 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
- 080Supply chainA bill of materials with every program, every dependency vetted, and a check that a release builds to the same bytes.Every device · Server
- 081Checked by machinesFormal models of the silent proof and of enrolment, 17 fuzz targets over every parser, and conformance tests for the crypto profile.Every device · Server
- 082A locked-down consoleIt listens only on the server and the tunnel. Five wrong codes pause sign-in for 15 minutes, and risky actions ask again.Console
- 083Least privilegeThe services run sandboxed, with only the network capabilities they need.Router · Linux · Server
- 084No company in the middleYour devices only ever talk to your own server. No Fenris server carries, sees or counts your traffic.Every device · Server
- 085No telemetryNothing phones home, and crash records stay on the machine.Every device · Server
- 086Never written downYour server never records the sites you visit, the names you look up or what is inside your traffic.Server
- 087What your server keeps, in the appEvery app has a page that lists what the server it has joined keeps, item by item, with how long.Every device
- 088Bug reports that hide youOne file to send for help, with addresses and names replaced unless you ask for them.Every device
- 089Every device’s links, side by sideEach 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
- 090Devices by nameEvery 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
- 091Add a deviceMake a one-time link or QR code for a named device, and see or withdraw the ones not used yet.Console
- 092AlertsRaised 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
- 093Alerts where you areBy webhook to Slack, Mattermost and most chat tools, and by email, always encrypted.Console
- 094Alert rules and snoozePick which alerts fire, set their thresholds, and snooze one.Console
- 095Usage by deviceThe data each device received and sent, day by day.Console
- 096A full audit trailWhat 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
- 097Admins, sessions and API tokensSeveral admins, a list of who is signed in, and tokens for scripts, read-only or with changes.Console
- 098PasskeysAdmins sign in with a passkey, or a six-digit authenticator code when a passkey isn’t to hand.Console
- 099Roles and single sign-onOwner, admin, network admin, auditor and member, with sign-in through Google, Authentik or Keycloak.Console
- 100PoliciesSettings by group, drafted, previewed and deployed, with the ones you lock.Console
- 101Fleet analytics and bulk actionsHealth and drops across the fleet. Act on many devices at once, and export or import them as CSV.Console
- 102Enrolment keys with approvalOne key for a batch of devices, limited and expiring, each device approved by an admin.Console
- 103Managed device profilesShip Fenris’s settings to company devices through your device manager.Android · Windows · Mac
- 104Keys and backupA backup sealed with a passphrase, restored on a new server without enrolling devices again.Console · Server
- 105Port forwardingOpen 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
- 106ExitsEvery device’s traffic leaves through your server. Chosen devices, apps or destinations can leave through another server, or a device at home.Console · Server
- 107Device releaseSee the release your server offers and which devices run it. Devices update when they next connect.Console
- 108Server at a glanceIts name and place, certificate and addresses, and the host’s CPU, memory, disk and monthly traffic.Console
- 109Prometheus and GrafanaMetrics on the server itself, and ready-made dashboards for server and client.Server
- 110A pool of serversSeveral servers share one identity, so a device moves between them without enrolling again.Server
- 111One console for many serversManage several servers and exits from one place.Console
- 112Site-to-siteRoute between the LAN behind a router and your server’s networks.Router · Server
- 113Move a serverRestore the sealed backup on a new machine, and every device follows.Server
- 114Router UIOn your LAN: Home, Links, Activity, Usage, Servers, Rules, Diagnostics and Settings, in light and dark, sized for a phone too.Router
- 115OpenWrt packageFor OpenWrt 25.12 and later, with a LuCI page. Every WAN is bonded, and settings survive a sysupgrade.Router
- 116Linux routerA Raspberry Pi or any Linux box bonds every interface that has a default route, for the LAN behind it.Router
- 117Android appJoin by QR code. Wi-Fi and mobile data bonded at once, a notification with what Fenris carries, and a quick-settings tile.Android
- 118Windows appA service with its own installer and a tray. Connections are named by program.Windows
- 119Mac app and command lineThe app with the same screens, or one line in Terminal that runs Fenris from boot.Mac
- 120Linux appdeb and rpm packages with the service and a tray, updated by your package manager.Linux
- 121TrayConnected, Connecting, Holding traffic or Off, at a glance. Quitting the tray leaves you protected.Windows · Mac · Linux
- 122The fenris command linestatus, top, links, flows, speedtest, check and more, with JSON for scripts.Router · Windows · Mac · Linux
- 123One command for a serverThe 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
- 124One line for a deviceOne line installs Fenris on a Mac or on Linux and asks for the invite link.Mac · Linux
- 125Store and package channelsGoogle Play, F-Droid, Homebrew and winget.Android · Windows · Mac
- 126Lower idle powerLess 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.