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.
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.
Every step is a fixed price with its own deadline. You can stop after any of them and owe nothing further.
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.
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.
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.
9 weekday hours
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.
7 weekday hours
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.
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.
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.
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.
Wazuh watching up to 25 of your machines, with two documented tuning passes before handover so the alerts that reach you are worth reading.
Somebody outside your team reads your Wazuh alerts every month, writes down what each one was, and keeps tuning out the noise your install was never running long enough to see.
Prices stay fixed because the edges are drawn before you book, not after.
Describe your situation and we will tell you which of these steps you need and which you can skip.