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.
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
| Option | What it is | Status |
|---|---|---|
| Airgate Cloud | Airowire runs the multi-tenant service. You add switches, directories and rules from the console; updates and backups are handled for you. | Available |
| Site connector | A 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 appliance | The whole platform as an OVA on your own hosts, with software updates and backups from the console. | Available |
| Microsoft Hyper-V appliance | The same appliance for Windows Server environments. | Planned |
| Azure and AWS Marketplace | Airgate deployed into your own Azure subscription or AWS account. | Planned |
| On-prem clusters | Several 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 is decided by Airgate's policy engine: which tenant and policy apply, which directory to ask, whether the device is managed and compliant, accept or refuse, and which VLAN or role. 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.
