People who connect to many customers' VPNs every day.
IT consultants, integrators and support teams use one app instead of a client per firewall.
ICM VPN connects your Mac to the VPNs organizations use, from the menu bar. It supports Palo Alto GlobalProtect today, with Fortinet and others next. The interface stays simple, errors say what went wrong, and security comes first in every decision.
Free plan: 100 successful connections a day during the beta.
7 / 100connections todayFree plan · beta
Try it: click ConnectIllustrative preview
IT consultants, integrators and support teams use one app instead of a client per firewall.
Anyone whose company runs a supported VPN can connect with a simple, clear client.
Each organization or customer is a profile. A server address and a username are enough; everything else is under Advanced.
A list of profiles, a Connect button, the status. While connected you see your address and how long you have been connected. If the server limits the session, ICM VPN warns you before it ends.
It does not just say “Unreachable”. It tells you which step failed, why, and what to do: “The username or password was not accepted.”
It reconnects after your Mac wakes or the network changes. If its background service restarts, your session comes back without asking for your password.
Internal names resolve through the tunnel. Your Mac's own DNS settings are never rewritten. If a connection drops unexpectedly, your network settings are put back the way they were.
The server's certificate is checked by macOS itself, including the root certificates your organization installs. When macOS does not trust a certificate, you see:
You decide on every connection. If the certificate changes, ICM VPN warns you.
If you want, your password is kept in the macOS Keychain, on this Mac only. Logs and diagnostics never contain passwords or session details.
There is a log window and a one-click diagnostics bundle. You can send the bundle to your IT team or to support; it holds no passwords, no session details and none of your Mac's hardware addresses.
The interface comes in both languages; choose one in Settings.
Not yet: SAML/SSO sign-in and client certificates. Both are on the roadmap.
| VPN | Status |
|---|---|
| Palo Alto Networks GlobalProtect | Supported |
| Fortinet FortiGate SSL VPN | Next |
| Cisco Secure Client (AnyConnect) | Planned |
| Ivanti Connect Secure (Pulse Secure) | Planned |
| F5 BIG-IP | Planned |
| Array Networks | Planned |
| OpenVPN (.ovpn), Sophos SSL VPN, WatchGuard Mobile VPN with SSL | Planned |
| Check Point, IPsec/IKEv2, WireGuard | Planned |
On first launch, macOS asks you once to allow the background service that sets up the tunnel: System Settings → General → Login Items.
Choose the VPN type, then enter the server address and your username.
Click Connect and enter your password, and a code if asked. The status shows in the menu bar.
Only a small background service has them. It sets up the tunnel, routes and DNS, and does nothing else.
It takes commands only from the ICM VPN app, after checking its code signature.
Before it runs with administrator rights, the VPN engine is moved to a protected copy whose signature is checked.
Passwords, session details and one-time codes never appear on the command line, in log files or on disk in plain text.
The server's certificate is checked by macOS, including the server name. The tunnel is pinned to the full fingerprint of the certificate that was verified or that you approved.
Engines such as OpenConnect run as separate processes. Their versions are pinned, and they are built from sources whose signatures are verified.
The Free plan is built around a simple daily quota. During the open beta, it's generous on purpose.
Each successful connection uses one from your daily quota.
Your quota refills every day.
During the open beta, Free includes 100 connections a day. After the beta, Free continues with 3 a day, forever.
Licenses are billed yearly at an affordable price. Prices will be announced before launch.
$0
Forever
With a daily connection limit.
Join the open betaComing soon
Billed yearly
A license for unlimited connections.
Notify meComing soon
For teams, billed yearly
Licenses for teams and businesses.
Contact salesPrices for paid plans will be announced before they launch. Taxes may apply.
For supported VPNs, yes. ICM VPN connects to your organization's server with that VPN's own protocol; nothing changes on the server. Check with your IT team whether your organization allows other clients.
ICM VPN does not send a HIP report. If the gateway asks for one, ICM VPN says so on the connection screen. Organizations that limit access based on HIP reports may keep some resources out of reach.
Not supported yet; it is on the roadmap. On such a server, ICM VPN tells you clearly that it cannot connect.
Only if you ask, in the macOS Keychain. It stays on this Mac and can be used only while your Mac is unlocked. Otherwise, ICM VPN asks for it on each connection.
ICM VPN shows who issued the certificate, which names it is for and until when, and what the problem is. You decide whether to connect, and it asks again on every connection. If a certificate you connected with before changes, you see a red warning.
ICM VPN reconnects on its own.
By default, ICM VPN asks first and then disconnects. If “Stay connected when ICM VPN quits” is on in Settings, the tunnel stays up. When you open the app again, it shows the connection where it left off.
During the open beta, 100 successful connections a day. After the beta, 3 connections a day, forever. A license makes it unlimited.
ICM VPN is open to everyone while we polish it. Beta versions may change often, and your feedback directly shapes the product.
Apps on the Mac App Store must run in a sandbox. The background service that sets up ICM VPN's tunnel cannot be installed that way. So ICM VPN is distributed directly from this site.
It is planned.
Export a diagnostics bundle from the Logs window and send it to hello@icm.sh. It contains no passwords or session details.
Get the Free plan with 100 successful connections a day while the beta lasts.
ICM VPN uses these open-source components: OpenConnect (LGPL-2.1), OpenSSL (Apache-2.0), vpnc-script (GPL-2.0 or later) and cJSON (MIT). License texts and source code.