auto-update

VPN clients that update themselves, and a live view of every device

Nobody chases developers to install a new version. The administrator publishes it, the clients pick it up, and the console shows who is on which version.

the problem

Why updates are a problem for a VPN

A client that is out of date is the one that breaks. Asking forty developers to update by hand does not work: some do it the same day, some in a month, and the support questions come from the ones in between.

A VPN client has a second constraint. An update that fails must not leave a machine without its tunnel, because then the developer is cut off from the AI tools. Updates have to be automatic, checked and reversible.

how it works

How an update reaches a device

  1. The administrator publishes a version in the console.
  2. The client checks a signed manifest and verifies the signature before it installs anything.
  3. The client installs the new version.
  4. If the new version fails to start, the client goes back to the previous one.

The signature means a client installs only what came from your installation. The rollback means a release that fails to start is replaced by the previous version.

live status

What the console shows

The console shows the live status of every device and every node. For updates, that answers the question you actually have.

  • Every device with its status and client version.
  • The last connection of each device.
  • The devices that are still on an older version.
  • The same view for the nodes.
day to day

What this saves the administrator

Without self-updating clients, every release is a small project: a message to the team, a reminder a week later, a list of people who still have the old build. With them, a release is one action in the console.

  • No install instructions to send around for each version.
  • The console shows which machines are still on an older build.
  • No guessing: the console shows which devices have taken the update and which have not.
  • A release that fails to start is rolled back by the client.

The administrator publishes, the client installs and checks the result, and the console shows the outcome. The client does this itself, with no mailing list and no manual step on each machine.

platforms

On every platform

windows

Windows

The native client takes the update from the signed manifest and rolls back if it fails.

macos

macOS

The native client follows the same update path as on Windows.

linux

Linux

The Linux client updates the same way, so one routine covers the whole team.

signed

Trust the update, not the download link

Updating software is the moment a client is most exposed, so the client does not take it on faith. It reads the signed manifest, checks that the signature is valid, and only then installs. A file that did not come from your installation is not installed.

For a security reviewer this is a short answer to a common question: who decides what runs on a developer’s laptop? The administrator does, through the console, and the client verifies it.

faq

Questions

Can a developer refuse or postpone an update?

The administrator decides when a version goes out. Updates are published in the console and installed by the client, so nobody has to remember to do it.

What happens if an update fails?

The client goes back to the previous version, so the machine keeps its tunnel.

How do we know an update is genuine?

The manifest and the update are signed, and the client checks the signature before it installs anything.

Can we see which devices are behind?

Yes. The console shows the client version of every device, so the ones still on an older version are easy to find.

request

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.