An operating system for network hardware

Airfy OS. One operating model for network hardware.

The software layer for network hardware. Linux underneath, AI agents on top, manufacturer-independent. Hardware was the moat for thirty years. The moat just broke.

Supported network hardware running one operating model

Your homelab on the same operator console

No toy dashboard. The same one production runs on.

Live event log stream

Same operator console as production.

Your homelab streams to the same operator console used for production deployments. No toy version.

What is Airfy OS

An OS for network hardware. Six layers. One platform.

We built it the way Apple built iOS or Android built AOSP, except for routers, access points, and edge boards instead of phones. The same operating system runs on every supported piece of hardware. The same APIs. The same agents. The same upgrade path.

Hardware-agnostic core

Runs on supported router, access point, and edge board families. One operating model, one toolset, with hardware support confirmed per release.

supported boardsvendor choicerelease-scoped

Linux foundation

Built on a hardened Linux base with release-scoped firmware evidence and component-level source availability. No black-box platform promise without a matching release note.

Linuxrelease evidenceauditable

AI agents built in

Every Airfy OS device ships with a Model Context Protocol server and MCP tool surface. Voice, chat, and agent control out of the box. No bolt-on integrations.

MCPMCP tool surfacevoice

Network stack

VLANs, WPA3, 802.1X, firewall, DHCP, DNS filtering, identity. Enterprise-grade primitives, applied uniformly across whichever hardware you ship them on.

VLANsWPA3identity

VPN and tunnel layer

WireGuard, mesh VPN, zero-trust tunnels, NAT traversal. Site-to-site connectivity ships with the OS, not as a separate product line.

WireGuardmesh VPNzero-trust

Cloud and API surface

REST, MQTT, WebSocket. Self-hostable end to end, or use the Airfy cloud. Same APIs either way. No license bricks if your subscription lapses.

RESTMQTTself-hostable

Who runs Airfy OS

A platform layer, not a product.

Hardware manufacturers embed Airfy OS in the box. Service partners deploy it on customer hardware. Enterprises self-host it inside their own infrastructure. Individual operators run it on whatever board they have. Same OS, four audiences.

Manufacturers embed Airfy OS in their hardware

Embed Airfy OS in your hardware and ship a router, AP, or industrial board with app, desktop, chat control, and AI agents already inside. Your name on the box, your warranty, our software underneath. The same model Android did for phones, applied to network hardware.

Hardware as a chip with software around it

Why now

Hardware was the moat. Software is the moat now.

For thirty years, network hardware vendors used proprietary firmware as a wall around their customers. The chip inside their router was the same chip everyone else used; the lock-in lived in the software the customer was not allowed to replace.

That wall is weakening. Buyers are asking for serviceable devices, transparent firmware, and deployment evidence before they standardize on a fleet. The walls around proprietary hardware are coming down buyer by buyer, policy by policy.

WiFi hardware was always a chip with plastic around it. From now on the software running on the chip is the asset. Airfy OS is the operating system that takes that asset seriously.

FAQ

An operating system for the next thirty years of network hardware.

Manufacturer-independent. Linux core. AI built in. Talk to our team about embedding it, deploying it, or running it yourself.