Integrations
One Tagnect, many vendors.
Tagnect doesn't sell radios or require a vendor: it manages access on the equipment already installed. Ubiquiti UniFi, TP‑Link Omada, Cisco Meraki, MikroTik RouterOS and OpenWrt today; Juniper Mist and HPE Aruba in development. For integrators and regional ISPs, that means serving different networks with a single product.
How Tagnect connects
Three integration modes, one experience
Through the vendor cloud
On Cisco Meraki, Tagnect uses the Meraki cloud API with the customer's key. Nothing is installed on site.
Inside the router itself
On MikroTik RouterOS and OpenWrt, the Tagnect connector runs on the router and talks to the cloud over outbound connections only. No computer on site.
Through the controller API
On UniFi and Omada, Tagnect drives the customer's controller through its API, via the Tagnect connector on the local network.
Vendors
What each integration delivers
On every available platform, Tagnect applies the same rules: rotating per‑group password, session duration, time windows, grace period and OTP. Traffic controls follow what each device offers.
Ubiquiti UniFi
Per‑group private PSK (PPSK) on the UniFi Network controller, with per‑group VLAN and the controller's traffic controls.
Integration: controller API, via the Tagnect connector.
Status: available.
TP‑Link Omada
Per‑group PSK and the Omada controller's access policies (OpenAPI), including bandwidth, VLAN and isolation.
Integration: controller API, via the Tagnect connector.
Status: available.
Cisco Meraki
Identity PSK (iPSK) without RADIUS and Meraki group policies for bandwidth, VLAN and content filtering.
Integration: Meraki cloud API, no connector.
Status: available.
MikroTik RouterOS
Multiple PSKs per SSID (multi‑passphrase) and isolated networks for guests, staff and devices, created automatically on every radio.
Integration: connector inside the router; one‑line install in the terminal.
Requirements: RouterOS 7.17+ with the wifi package (e.g. hAP ax).
Status: available.
OpenWrt
Rotating PSK with multiple keys in hostapd, rotation without dropping connected clients, and device disconnection.
Integration: connector inside the router, with signed updates.
Requirements: certified models.
Status: available.
Juniper Mist / HPE Aruba
Per‑user PSK with native rotation (Mist PSK) and MPSK (Aruba).
Integration: vendor cloud.
Status: in development.
For integrators and regional ISPs
Why hardware‑agnostic matters
Single‑vendor solutions make the customer replace equipment before signing up. Tagnect does the opposite: it moves into the installed base and grows with it.
- No equipment replacementThe customer subscribes without buying new radios; the investment already made keeps its value.
- Mixed portfolios in one consoleUniFi at one customer, MikroTik at another, Meraki at a third: same rules, same app, same console.
- Regional ISPs on MikroTikISPs that already deliver MikroTik routers to subscribers add managed guest Wi‑Fi, in many cases without a site visit.
- Freedom to switch vendorsIf the customer changes equipment later, the tags, groups and rules stay in Tagnect.
Confirm your equipment
Tell us the vendor, model and firmware of the controller or router. We confirm compatibility and the available controls before deployment.