Skip to content

Deployment options

Airgate runs the same software everywhere: as a multi-tenant cloud service operated by Airowire, or as a virtual appliance in your own data centre. Site connectors extend either one into sites whose network devices cannot reach it directly. This page helps you choose.

Option Who runs it Status
Airgate Cloud Airowire Available
On-premises appliance for VMware ESXi / vSphere (OVA) You Available
Airgate Edge site connector You (at each site), with Cloud or the appliance Available
Microsoft Hyper-V image You Planned
Microsoft Azure Marketplace You, in your Azure subscription Planned
AWS Marketplace You, in your AWS account Planned
Clustering and high availability of on-premises appliances You Planned
Policy sync to site connectors (connector-based local decisions) You Planned

Airgate Cloud is the multi-tenant service. Your organisation is a tenant: its policies, directories, devices, certificates and logs are separated from every other tenant’s.

  • What you run: nothing on premises for sites that can reach the cloud. Your switches, access points and wireless controllers send RADIUS straight to Airgate, or RadSec (RADIUS over TLS, TCP 2083) for an encrypted path.
  • How Airgate knows your devices: a request belongs to your tenant through the network device that sent it: by its public source address, or by the RadSec client certificate it presents. The address ranges of different tenants may not overlap, so devices behind a shared or overlapping NAT address must use RadSec or a site connector.
  • Updates and backups: Airowire updates, backs up and monitors the platform. You do not use Settings › Software update or Settings › Backups; those are for the appliance.
  • Console: you sign in at the address Airowire gives you, with a password or through your own identity provider (console single sign-on).

Use a site connector when your network devices use private addresses that the cloud cannot see, cannot do RadSec, need Change of Authorization (CoA) from the cloud, or when you check Active Directory passwords with PEAP-MSCHAPv2.

The Airgate appliance is a ready-to-run virtual machine for VMware ESXi and vCenter: Ubuntu 24.04 LTS with the whole Airgate stack (database, console and API, RADIUS, TACACS+) installed. It needs no internet access to deploy.

File airgate-<version>.ova with airgate-<version>.ova.sha256
Hypervisor ESXi or vCenter 6.7 or later (virtual hardware version 14)
Default size 4 vCPU, 8 GB RAM, 60 GB thin-provisioned disk, one VMXNET3 network adapter
Updates Signed update files installed from Settings › Software update
Backups Encrypted daily backups, optional copy to an SFTP server

Choose the appliance when policy, logs and certificate authorities must stay in your own data centre, or when network devices must not send RADIUS over the internet. A single appliance serves every site that can reach it; one appliance can also hold several tenants.

See Install the appliance on VMware ESXi.

A site connector is a small service at a site, next to the network devices. It only connects out to Airgate (HTTPS, and RadSec on TCP 2083 when allowed), so you open no inbound firewall ports. It works with Airgate Cloud and with the appliance.

What it does for the site:

Function What happens
RADIUS relay Switches and access points send ordinary RADIUS (UDP 1812/1813) to the connector, which forwards it over RadSec or an HTTPS tunnel, with the device’s original address
CoA relay Change of Authorization and Disconnect requests from Airgate reach devices behind NAT (UDP 3799)
TACACS+ tunnel Device administration logins (TCP 49) are tunnelled to Airgate’s TACACS+ service
DHCP fingerprinting The connector is an extra DHCP helper address; it never answers DHCP, it only reads fingerprints for device profiling
Active Directory password checks A domain-joined connector checks PEAP-MSCHAPv2 passwords against your domain controllers (ntlm_auth)
Offline MAC authentication During a WAN outage it answers known MAB devices from a local cache

It ships as its own small appliance, airgate-edge-<version>.ova (2 vCPU, 2 GB RAM, 16 GB disk), or as the nac-edge program for a Linux host of your own.

See Install a site connector.

These options are on the roadmap and are not available yet. Do not plan a production deployment on them.

  • Microsoft Hyper-V image (Planned): the appliance as a Hyper-V virtual machine.
  • Microsoft Azure Marketplace (Planned): deploy Airgate into your own Azure subscription.
  • AWS Marketplace (Planned): deploy Airgate into your own AWS account.
  • On-premises clustering and high availability (Planned): several appliances serving the same tenants with automatic failover.
  • Connector-based policy sync (Planned): site connectors that hold a copy of the policy and decide locally. Today a connector relays requests; only known MAB devices are answered locally during an outage.
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security