Links drop. Fenris is built for it.
Why it exists
A phone has Wi-Fi and mobile data. A home has fibre and a 5G box. A shop has a broadband line and the owner’s hotspot. Each of them picks one link, stays on it, and leaves the rest idle until the first one fails. Then everything that was open breaks, and somebody goes looking for the hotspot.
The links were never the problem. Two ordinary links seldom fail at the same moment, because they fail for different reasons: a cable is cut, the power goes, a tower is crowded. What was missing is something that uses them together, and keeps one address to the world while they come and go.
That takes a server at the far end, to put the pieces back together. Other products run that server for you, which puts a company in the path of everything you do. We wanted the other arrangement: the server is yours, and we are not in the path at all.
So Fenris is software and nothing else. It runs on your router, your computers and your phone, and on one small server that you own. It is made in India, for the internet people here actually have, and it works the same wherever links come in twos and threes.
Fenris
How it is made.
Five rules we hold ourselves to. Each one costs something, and each one shows up in the product, where you can check it.
- 01
Never add a delay we can avoid.
Fenris sits in the path of everything you do, so a wait it adds is felt everywhere. Speed is decided flow by flow, never traded away for a tidier design.
In the productWhile only one link works, new connections can go straight out of it, since the detour gains nothing. The setting is called Direct while alone.
- 02
Say only what the code does.
Every sentence on this site is checked against the code before a release. Where the product stops, the page says so in the same breath.
In the productEvery link says why it is used or not, in words: used when the others are busy. No hidden rule decides for you.
- 03
Your server, your data.
No company in the path, no account with us, and nothing that phones home. We would rather not hold what we could be asked to hand over.
In the productEvery app has a page that lists what your server keeps, item by item, each with how long. The same list is here.
- 04
One place for every setting.
Nothing can be set in two places, and no page does two jobs. A summary links to the page that owns the subject.
In the productThe console is one flat menu of ten pages, with no groups and no second way in. See its screens.
- 05
Plain words.
Links carry, go quiet and come back. If a sentence needs a glossary, we write it again.
In the productThe Activity page reads: Fibre went quiet. The other links carried its traffic.
What we won’t tell you
Things other sites in this field say, and why this one doesn’t.
- That it never drops.If every link fails at once you are offline until one returns. Fenris then reconnects by itself.
- That it adds your speeds up.Together your links give close to their sum, less a little for the tunnel. One link alone is not made faster.
- That it makes you anonymous.Websites see your server’s address, and it is yours alone. Who can see what
- That it has been audited.It has not. What is checked, and how
Write to us
- About anything
- hello@fenris.network. A person reads it and replies.
- About a flaw
- security@fenris.network, privately. How we handle reports
- To try it
- Ask for early access. Free during early access.