Use cases/Self-hosters and home labs
A way in to what you run at home.
Your provider shares one address among many homes, so nothing in yours can be reached from outside. Your Fenris server has an address of its own. Open a port on it, and whatever calls that port comes down the tunnel to the machine at home.
The links you probably have
- Home fibreused all the time
- A 5G boxused all the time
The words on the right are the roles Fenris gives a link. You choose them.
One day, as it plays out.
A shelf at home with a media server, a camera recorder and a game server for friends. Fibre from a provider that gives no public address, and a 5G box that gives none either. One thing goes wrong today, and one thing is tried.
From a train, you open the camera recorder at home.
There is no address to call. People rent a relay, or run a second tunnel for this alone.
A port on your server leads to the recorder. Your phone calls the server’s address, and the call comes down the tunnel to the shelf.
- Fibreused all the time
- 5Gused all the time
Friends are on the game server when road work cuts the fibre. It stays out for nearly three hours.
A relay’s tunnel rode the fibre and falls with it. Everyone is thrown out, and nothing at home can be reached until the fibre is back.
The port is on your server, not on the fibre. Calls keep arriving there, and come down the 5G instead. The address your friends use never changed.
- 11:20Fibre went quiet. The other links carried its traffic.
- 14:10Fibre carries traffic again.
Someone runs a scan over your server’s address, as someone always does.
A server set up by hand answers on whatever was left open: a remote login, an old dashboard.
On the tunnel’s UDP port the scan gets no reply: your server answers only devices you enrolled. The ports you opened do answer, as they must, and each leads to one machine.
What Fenris does here
Each is a feature with its own page, where it says what it costs.
- A way in from outside
- Open a TCP or UDP port on your server to a device, or to a computer behind a router. It sees each caller’s own address.
- No company in the middle
- Your devices only ever talk to your own server. No Fenris server carries, sees or counts your traffic.
- A silent server
- Your server answers only devices you enrolled. A scan of its UDP port gets no reply.
- A link drops, the others carry it
- When the fibre goes quiet, what you serve comes down the other link, at the same address.
- A console that shows each link
- Each device with its links and its log, and an audit trail of who changed what.
- Updates you control
- Your server holds the release. Devices fetch it through their tunnels, and go back to the old version if the new one can’t reach the server.
What you need
- At home
- A router running OpenWrt or Linux in front of the shelf. Or Fenris on the Linux machine that does the serving.
- A server with an address
- A small Linux server in the cloud, with a public address of its own. That is the address the world calls.
- A data allowance
- Everything you serve passes out through your server. Pick a plan whose included transfer covers your month.
Where it stops
- The server has no public address.The Fenris server itself can’t sit behind a shared address. It lives where it has one of its own: a cloud region, or premises with a public address.
- What you open is yours to guard.Fenris leads a port to one machine. Keeping what answers on it up to date is still your job.
- Your server’s address is yours alone.Websites and callers see one address that doesn’t change. That is steadier than a shared one, and less anonymous.
- One link is left.It carries what it can. One link can’t be made faster.
Try it on your own links
Tell us which links you have, and we’ll write when a build for your links is ready. Free during early access.