The Zero Trust Offboarding
One person taken off the zero-trust network you already run, with proof they are off: their own live connection cut while you watch, and the joining key they still hold refused when we try it. Priced per person, so you buy one the day somebody leaves.
Somebody resigned on Thursday afternoon. You take them out of the access rules and the job feels finished. A rule change stops new connections and leaves the ones already open running, so the person you removed is still working.
We find everything the network holds in their name — the desktop you had forgotten about, the joining key sitting in their password manager — and take it away in an order that cannot leave a door open. Then we show you a connection of theirs dying, and we try to get back on with the credential they still hold so you can see the refusal.
Our engineers build these networks, so they know the failure that looks like success: a tidy policy file and a leaver still connected. You get a dated record of what came off, when, and how each part was proved, plus the doors that were never ours to close. You pay per leaver: buy one the day somebody goes, or buy a few now and use one each time a person leaves.
What's included
Everything the network holds in their name, found before we touch any of it — including the joining keys nobody remembers issuing
Their open connections ended. Removing somebody from the rules leaves whatever they had running still running, and it is taking their machines off the network that stops it
A connection of theirs shown dying while you watch, and their joining key refused when we try to use it, because taking somebody off and proving they cannot get back are two different claims
Everybody else proved untouched. Before we delete anything we check whether one of their machines was carrying access for the rest of you, and if it was, we stop and tell you who would have lost what
Nothing done to a device that is not yours to hand us. They can keep the software; the network no longer knows that machine, and we show you that rather than telling you
A dated record of what came off, when, and how it was proved — the thing you reach for six months later when somebody asks
The doors that were never ours to close, listed with the exact action for each: your identity provider, and the shared password they know
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
Administrator access to your Headscale or Tailscale network for our engineer, or a scoped API key
The leaver's sign-in identity as your control plane shows it, and the date and time their access ends
What should happen to each of their machines, and whether any of them is a server or route other people rely on
A second way into every machine that must stay reachable: a provider console, IPMI, an existing VPN or someone on site
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 Policy Change
One change to the access rules on the zero-trust network you already run — up to three rules on one group, granted or taken away. You see who loses what before we touch anything, and we run the way back before we need it. Priced per change, so you buy one whenever a rule needs to move.
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 Password Manager Rollout
Your company logins out of the spreadsheet and into 1Password or Bitwarden for up to 50 people: vaults built, sign-on connected, staff trained live, and a locked-out account recovered in front of you before we hand over.