The Zero Trust Network Setup
A private network across your machines, running on a coordination server we build on hardware you own, with no subscription and nobody else holding the keys. Each group reaches only the ports you named, and we prove it by showing you an identity with no permission being refused.
A VPN gives everyone who gets through it the run of the place. The usual alternative hands your network's keys to a company you pay by the head, and asks you to trust that their outage is not your outage.
We build the third option: the coordination server on your own machine, running a network where each group reaches only the ports you named. No per-user fee, no seat count, and the policy sits on a disk you can walk up to. The printers and cameras that will never run this software stay reachable, through a machine on their network that speaks for them.
Our engineers have been building Linux servers since 2003, and the outcome they design hardest against is you losing the way into your own estate. So before we hand over, we switch the network off on one of your machines and reach it anyway, while you watch.
What's included
A coordination server on hardware you own, proved to answer from the outside world after a service restart and after a full reboot of the machine it sits on
No subscription and no seat count, because the part everyone else charges per user for is the part you now own
Each group reaching only the ports you named, so a stolen laptop reaches what that person reached and nothing else in the building
Printers, cameras and appliances still within reach, through a machine on their network that speaks for them. They will never run this software, and we say so before you pay rather than after
The restriction proved from the wrong side as well as the right one: something with no permission, refused a machine an allowed identity had reached a minute earlier, with the output handed to you
A way back in that you have watched work: the network switched off on one of your machines, that machine reached anyway in front of you, and a key you keep offline for the day nothing else works
Everything the next engineer needs written down: the version running, how the policy is edited, what the certificate expires, how to upgrade it safely, and the one line that opens the network up again
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
A Linux server of yours (Debian, Ubuntu, Rocky or AlmaLinux) with root or sudo access over SSH
A public name that already points at that server, port 443 open to the internet, and a certificate for that name or a reverse proxy of yours in front of it
Up to three groups with the people in each, and up to ten rules saying which group reaches which machine and port
Up to five machines to join, each with a way in that does not use the new network: a provider console, IPMI, an existing VPN or someone on site
The person who will hold the break-glass identity, and somewhere offline to keep its key
A time for the step that tightens the rules, with someone of yours on the call
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Zero Trust User Onboarding
One person and the machine they work on, put onto a zero-trust network you already run, with somebody on the call to do it with them. Their access proved from their own machine, both what they can reach and what they cannot.
The Zero Trust Device Addition
One machine onto a zero-trust network you already run, joined under a tag that already exists, and proved twice over: everything it should reach, reached, and one thing it should not, refused.
The Guacamole & Zero Trust Network
Your people sign in to one gateway, and that gateway is the only thing on your network allowed to reach the servers behind it. Every session is recorded and kept for a window you choose.
The Wazuh Server & Client Install
Wazuh watching up to 25 of your machines, with two documented tuning passes before handover so the alerts that reach you are worth reading.