Airgateby Airowire

Deployment

Airgate makes every decision in one place: Airowire's cloud or your own appliance. Your switches and access points reach it directly over RadSec, or through a site connector that also gives it a path to on-prem Active Directory and to devices behind NAT.

YOUR SITESwitches and APsany RADIUS deviceActive Directorydomain controllersLaptops, phones, IoTwired, Wi-Fi, VPNSite connectorRadSec to AirgateCoA relayPEAP / NTLM relayoffline MAB cache802.1X / MABRADIUSNTLMAIRGATE (CLOUD OR APPLIANCE)RADIUS · RadSec · TACACS+EAP-TLS, PEAP, TTLS, MABPolicy enginepolicies, rules, resultsdiagnosis and tracePKI · guests · BYODSCEP, OCSP, portalsIdentityEntra ID, Okta, GoogleDevice stateIntune, JamfSentinelOne, CrowdStrikeOut toTeams, SIEM, firewallsRadSec · TLS 2083control channel · HTTPS

Both connections from the site connector are outbound and mutually authenticated; nothing at the site needs an inbound firewall rule. Ports and firewall lists every port.

Where Airgate runs

OptionWhat it isStatus
Airgate CloudAirowire runs the multi-tenant service. You add switches, directories and rules from the console; updates and backups are handled for you.Available
Site connectorA small service on a VM or mini-PC at each site. It carries RADIUS to the cloud over RadSec, relays disconnects and re-authorisations through NAT, relays PEAP to on-prem Active Directory, and keeps answering for known MAC-authenticated devices if the internet link drops.Available
VMware ESXi / vSphere applianceThe whole platform as an OVA on your own hosts, with software updates and backups from the console.Available
Microsoft Hyper-V applianceThe same appliance for Windows Server environments.Planned
Azure and AWS MarketplaceAirgate deployed into your own Azure subscription or AWS account.Planned
On-prem clustersSeveral appliances working as one, with shared state and failover.Planned

How a sign-in is decided

FreeRADIUS terminates RADIUS, RadSec and EAP and does the credential checks. Everything else — which tenant and policy apply, which directory to ask, whether the device is managed and compliant, accept or refuse, and which VLAN or role — is decided by Airgate's policy engine, so there is one place to read and change policy.

The policy service keeps no state of its own: it scales out over a shared database, and configuration changes reach every node through an event relay. Each sign-in record keeps the full trace of how it was decided.

How Airgate works · High availability and sizing