Release notes
This section lists what changed in each Airgate release. Read it before you update an on-premises appliance, or to see what is new on Airgate Cloud.
- 2026 release notes: every change in 2026, newest first.
How releases work
Section titled “How releases work”| Deployment | How it is updated |
|---|---|
| Airgate Cloud | Airowire updates the service. You do not install anything. |
| On-premises appliance (VMware ESXi / vSphere) | A platform administrator installs an update file from Settings › Software update. See Software updates. |
| Airgate Edge connector appliance | Each build also ships a new connector appliance image. |
Every Airgate build produces three files, published together on the Airgate
releases page under the tag appliance-<version>:
| File | What it is for |
|---|---|
airgate-<version>.ova |
A new Airgate server appliance for ESXi / vSphere. Use it for new installations. |
airgate-update-<version>.tar |
An in-place update for a running Airgate appliance. Install it from Settings › Software update. |
airgate-edge-<version>.ova |
A new Airgate Edge site connector appliance. |
Each file has a matching .sha256 checksum file. A build that failed for
one of the appliances is published without that appliance’s files.
Version numbers
Section titled “Version numbers”Current builds are numbered 0.0.0-N, where N increases with every build
(for example 0.0.0-28). The update file for that build is
airgate-update-0.0.0-28.tar on the release appliance-0.0.0-28. A
versioned release (for example 1.2.3) uses its version number in the same
file names.
What every build goes through
Section titled “What every build goes through”Before a build is published, it is installed and tested automatically:
- The Airgate images are built and installed on a clean Ubuntu 24.04 LTS virtual machine.
- A smoke test runs the first-boot setup, starts every service, checks that the console and RADIUS answer, and backs up and restores the appliance.
- The appliance is sealed (its own machine ID and SSH keys on first boot) and packed as an OVA, which is then boot-tested.
- The update file is signed with the Airgate release key. An appliance accepts only updates signed with that key, so you cannot install a file that was changed after it was built.
Find the version you run
Section titled “Find the version you run”On an appliance, open Settings › Software update (platform administrators). The Installed card shows:
- Appliance version: the version the update agent installed.
- Console build: the version of the Airgate services you are using.
- Previous version: the version kept for a rollback, if any.
Over SSH, sudo airgate-update status shows the installed and previous
versions.
Current builds
Section titled “Current builds”| Build | Date | Highlights |
|---|---|---|
| 0.0.0-28 | November 19, 2026 | Entra ID lookups stay fast after quiet periods. |
| 0.0.0-27 | November 19, 2026 | Intune and SentinelOne devices are matched by Intune device ID, so devices with private Wi-Fi addresses are recognised. |
| 0.0.0-26 | November 19, 2026 | New look for the self-service onboarding (BYOD) portal; clearer macOS steps. |
| 0.0.0-25 | November 18, 2026 | AirEnroll for Windows finds its setup link on its own. |
| 0.0.0-24 | November 18, 2026 | AirEnroll apps for Android and Windows. |
| 0.0.0-23 | November 18, 2026 | Self-service device onboarding (BYOD portals). Server appliance only. |
| 0.0.0-22 | November 18, 2026 | Sign-in log explains each failure in plain language. |
| 0.0.0-21 | November 18, 2026 | Intune and SentinelOne conditions in access policies. Server appliance only. |
| 0.0.0-20 | November 18, 2026 | Edge connector appliance only. |
| 0.0.0-19 | November 18, 2026 | Searchable sponsor list on the guest portal. |
| 0.0.0-18 | November 18, 2026 | New Airowire guest portal skin. |
| 0.0.0-17 | November 18, 2026 | Not published (build failed). |
| 0.0.0-16 | November 18, 2026 | Guest portal login condition in access policies. |
| 0.0.0-15 | November 18, 2026 | Guest portal skins, Microsoft Teams sponsor delivery. |
| 0.0.0-14 | November 18, 2026 | Edge connector appliance only. |
| 0.0.0-13 | November 17, 2026 | Device details open correctly from the quick view. |
| 0.0.0-12 | November 17, 2026 | RADIUS picks up a new server certificate without a manual restart. |
| 0.0.0-11 | November 17, 2026 | Edge connector appliance only. |
| 0.0.0-10 | November 17, 2026 | Intune SCEP enrolment on Windows fixed for RSA certificate authorities. |
| 0.0.0-9 | November 17, 2026 | PEAP-MSCHAPv2 against Active Directory directly on the server appliance. |
| 0.0.0-8 | November 17, 2026 | Backups and restore; replace the root CA with your own. |
| 0.0.0-7 | November 17, 2026 | Edge connector appliance only. |
| 0.0.0-6 | November 16, 2026 | First build with an in-place update file. |
| 0.0.0-5 | November 16, 2026 | First Airgate Edge connector appliance. Server appliance without update file. |
| 0.0.0-4 | November 16, 2026 | The setup wizard creates your organisation. No update file. |
| 0.0.0-3 | November 10, 2026 | First Airgate server appliance (OVA). No update file. |
Builds 0.0.0-6 and later can update an appliance in place, except the builds marked “Edge connector appliance only” and 0.0.0-17, which have no update file. An appliance installed from build 0.0.0-3, 0.0.0-4 or 0.0.0-5 has no update agent yet: see the first-update steps in Software updates.