Solutions

Replace your VPN with access you can prove, and that ends the day somebody leaves

We build you a private network where each person reaches the machines they need and nothing else. When somebody goes, we end their sessions and send you the evidence: the timestamp, their absence from a colleague’s network, and their old key refused when we try it.

What a VPN does not do

A VPN puts a laptop on your network and then stops watching. Everything on that network is reachable from it, and nothing records which of it somebody actually opened.

Removing them from a group later stops new connections. It does not close the session already running, and most businesses never find out which of the two happened.

The alternative grants one person access to one machine, records it, and can show you the day it ended.

How it goes, step by step

Every step is a fixed price with its own deadline. You can stop after any of them and owe nothing further.

  1. 1

    Build the network

    A control plane on hardware you own, your access rules written from a template, seed machines joined, and a break-glass route proved by switching the network off and reaching a server anyway.

  2. 2

    Put people and machines on it

    One person or one device at a time, bought in packs and drawn down at your pace. A person gets a scheduled session and a connectivity test against the resources they actually need.

  3. 3

    Broker the sessions you need to prove

    If you want it

    Your people reach servers through one gateway, and that gateway is the only thing on the network permitted to reach them. Every session is recorded and kept for a window you choose.

  4. 4

    Change the rules without locking yourself out

    Before a character is edited you get a written statement of who reaches what today, who does afterwards, and what keeps working. The revert is written and run before the change goes near production.

  5. 5

    Take people off

    Keys first, then group membership, then the machines themselves, because deleting the node is what actually ends the session. Proved three ways and recorded with a date.

The steps above that are not marked optional come to US$289 before any per-person or per-machine work, which is priced per unit and shown on each task page.

What happens afterwards

The network needs somebody to move the version forward, watch the key expiry dates and answer the routine requests. Left alone, the first symptom is a machine that used to connect and now does not.

Watching for the things a network cannot tell you about itself, such as a run of failed logins at two in the morning, is a separate job.

Where this stops

Prices stay fixed because the edges are drawn before you book, not after.

  • Tightening a rule stops new connections. It does not tear down a session already open, which is why offboarding deletes the machine rather than editing the policy.
  • Every device that connects must be a member of the network. There is no version of this where a contractor reaches your servers with nothing installed.
  • We add permissions and never remove them by surprise. Where an existing rule already grants access, you get the exact line that would close it and the decision stays yours.
  • We do not respond to incidents under any of these tasks. We can show you what happened and hand it over.

Questions people ask first

Tell us what you are running

Describe your situation and we will tell you which of these steps you need and which you can skip.

Support Resort assistant
Enter to send · Shift + Enter for a new line