platforms

Windows, macOS and Linux, managed from one console

Development teams are mixed: MacBooks, Windows workstations, Linux laptops and build servers. Windows and macOS get native clients, and Linux has a client of its own.

consistency

One console for three systems

A policy that holds on one platform and quietly fails on another is not a policy. Windows, macOS and Linux each have a client with the things your security review cares about:

  • Routing by domain for Anthropic, Cursor, OpenAI and JetBrains; everything else goes direct.
  • Reliable leak protection: if the tunnel drops, traffic to the listed domains stops.
  • Signed self-updates, with a rollback when a version fails.
  • Diagnostics that name a conflicting VPN and repair the tunnel.
clients

Platform by platform

windows

Windows

A native client for the workstations most corporate fleets are built on,, with routing by domain and reliable leak protection.

macos

macOS

A native client for the MacBooks that many developers work on, managed from the same console as the rest.

linux

Linux

A Linux client for the laptops, workstations and servers your team runs on Linux.

reality

Why mixed fleets are the hard case

Few engineering teams standardise on one system. A designer-turned-frontend developer works on a Mac, the infrastructure engineer prefers Linux, the person who maintains the legacy product is on Windows, and the build servers are Linux again. A tool that treats one of them as a second-class citizen leaves a gap exactly where an AI tool is most likely to go out the wrong way.

With one client per system and one console above them, the administrator does not keep three sets of notes. The same list of devices shows them all, the same routing lists apply to them all, and the same signed updates keep them current. A question such as "who is still on the old version?" has one answer, not three. The audit log of administrator actions is likewise one log for the whole fleet.

rollout

Installing on a developer's machine

The developer installs the client and opens the profile link the administrator sent. That is the whole setup. After that, updates arrive on their own and are signed, so the fleet does not fall behind because someone skipped a notification.

The administrator sees every device in the console with its status and client version, whatever system it runs. A new hire gets a link on the first morning and has the same route as the rest of the team before the first commit.

scope

What about phones

The product is for the desktops and servers where AI coding tools run. It has no mobile clients, and we do not promise any. If your question is how to protect the laptops and build machines that talk to AI services, this is the right shape. If it is about phones, it is not.

faq

Questions

Which systems are supported?

Windows, macOS and Linux. All three are managed from the same console.

Is there a mobile client?

No. AI coding tools run on desktops and servers, and that is where the client runs.

Which features does each system have?

Windows, macOS and Linux each have a client with routing by domain, reliable leak protection and signed self-updates.

Can one person use two machines?

Yes. Each device gets its own profile, so a developer with a laptop and a workstation has two profiles, each visible in the console.

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.