VPN nodes that set themselves up and stay in shape
Running your own VPN usually means someone looks after the servers by hand. Here the console does the routine work, and the administrator decides when it happens.
The usual cost of running your own VPN
The first server is set up carefully. The second is set up from memory. By the time there is a third, nobody is quite sure how the first one was configured, a small fix made at midnight lives only on one machine, and the updates wait for the person who has an hour to spare.
None of this is dramatic. It is the slow drift that turns a tidy installation into a set of servers that each behave a little differently, and it lands on the one engineer who knows the details.
Provisioned the same way every time
Point the console at a clean server and it sets up the node: the same steps, in the same order, on every server. Running the procedure again is safe. It changes only what is not already right and leaves the rest alone, so a repeat is a check as much as a setup.
That is what makes a node something you can rebuild rather than something you have to remember. The configuration lives in the procedure, not in someone's head.
Drift found and fixed
Checked against the expected state
Each node is compared with the state it should be in. If something differs, the node is repaired and brought back to that state.
Failed steps are tried again
A step that fails, because a network hiccup or a busy server got in the way, is retried instead of leaving the node half done.
The state is visible
The console shows the live status of every node, so the answer to "is node two healthy?" is a glance, not a login.
Maintenance in your window
Updates and the reboot that sometimes comes with them run in a window the administrator sets. Pick the hours when your developers are away, and the nodes are patched then.
The team is not interrupted in the middle of a working day, and the administrator does not have to stay up to do it. Each action an administrator takes in the console is recorded in the audit log.
Adding the next node
A new node is added from the console with the same procedure as the first. Node five is set up like node one, and it is maintained in the same window. The capacity view shows the load on each node, so you can see when another one is worth adding.
Questions
Does the console need access to our servers?
Yes. You give the console a server and access to it. The console sets the node up and keeps it in the expected state.
When do updates happen?
In the maintenance window the administrator sets. Updates, and a reboot when one is needed, wait for that window.
What if someone changes a node by hand?
The change shows up as drift from the expected state, and the node is brought back to it.
Can we see what changed on a node?
The console shows the live status of every node. Actions of administrators are recorded in the audit log.
Request a demo or a pilot
Tell us about your team, and we will come back with a time for a call and a plan for a pilot.