The Aero platform
One platform. Every layer of the building.
Aero is a complete building automation stack, with AeroNode at the edge, AeroServer on premises, AeroConnect in the cloud and AeroView everywhere, built on one shared core so every layer speaks the same language.
- Edge-first
- Outbound-only mTLS
- BACnet + Metasys N2
- HTML5 AeroView
- No point licensing
Architecture
The edge does the work. Everything else adds visibility.
AeroNodes run the building on their own. Supervisors and the cloud connect through a stream that each node opens itself, so the building never has to let anything in.
- 1
Operators
Any browser, on site or remote. AeroView is pure HTML5, with no Java and no thick client.
- 2
AeroServer · AeroConnect
On-premises supervisor and optional cloud relay for remote access.
- 3
Outbound mTLS
Every node dials out over one mutual-TLS stream. No inbound firewall rules.
- 4
AeroNode
Supervisory controllers that run logic, schedules, trends and alarms locally.
- 5
Field buses
BACnet MS/TP, BACnet/IP and Metasys N2 devices, including AeroStat thermostats.
AeroView
One interface, in any browser.
AeroView is the HTML5 application every AeroNode serves over HTTPS, and the same interface AeroServer uses for the whole station. There's no Java, no thick client and no engineering-workstation license.
- Dashboards with gauges, trends, alarm lists and floor plans
- Equipment graphics from 11 templates
- Network setup and device discovery
- Point manager with overrides and priority arrays
- Trends with multi-point charts and CSV export
- Alarms and alarm history
- Schedules with exceptions and month view
- Program sheets and reusable macros
- Virtual devices and AeroNet peers
- Users, network, BACnet server and firmware settings
Capabilities
What every AeroNode does out of the box.
No add-on modules, no feature licenses. Every capability below ships in the standard firmware.
Driver framework
Each field protocol runs as its own supervised driver process, so a misbehaving device or a hung serial port can't take down the controller. Every serial port is driver-agnostic, and new protocols arrive as signed firmware updates.
Program sheets
Drag-and-wire control logic with live values: about 40 blocks including PID, formula, delay, edge detection and alarm blocks. Package proven sequences as versioned macros and reuse them across jobs.
Schedules
Weekly schedules with date-range exceptions and a month view. Device schedules stay in sync with BACnet Schedule objects, and node schedules command points at the priority you choose.
16-level priority arrays
True BACnet command arbitration on every writable point: timed overrides, relinquish defaults, and priorities that survive a reboot. Schedules, logic and operators coexist predictably.
Trending on the edge
Interval or change-of-value logging with per-point retention, stored on the node itself. Multi-point charts and CSV export in any browser.
Alarm management
Point limit and state alarms with delays and deadbands, device-offline alarms and logic-driven alarms, with a full acknowledge/clear lifecycle that writes acknowledgements back to BACnet devices.
Dashboards & equipment graphics
Build dashboards from gauges, trends, alarm lists, setpoint adjusters and floor plans. Generate equipment graphics from 11 templates (AHU, VAV, RTU, FCU, boiler, chiller and more).
BACnet server
Publish Aero points as BACnet/IP objects so an existing front end, whether Niagara, Metasys or another BACnet workstation, can read and command them during a phased migration.
AeroNet peering
Pair nodes directly with a one-time code. Share points, and view a peer's alarms, schedules and trends with no server required.
BACnet time sync
Opt-in time synchronization for field devices, and it will not push the time if the node's own clock isn't synchronized.
Signed firmware, automatic rollback
Every firmware release is cryptographically signed and verified before it installs. If a new version fails to start, the node automatically restores the previous one.
Secure by design
Encrypted access on every node, protection against repeated failed logins, and authenticated, encrypted connections to supervisors. Nodes only dial out, so there are no inbound firewall ports to defend.
Commissioning that respects your time
A guided setup wizard, network changes that roll back automatically if you lose contact, device discovery, and point managers built for bulk work.
AeroConnect
Remote access without the VPN.
AeroConnect is HBT's cloud relay. Because every node already dials out, remote access needs no VPN appliance, no jump box and no port forwarding, just a browser.
AeroConnect is an optional subscription service. AeroNode and AeroServer work fully without it.
Per-session authorization
Every remote session is individually authorized and limited to a single node.
The node still decides
Remote sessions land on the node's own login, so its users and permissions apply unchanged.
Built for contractors
Organize nodes by company, invite team members, and grant customers access to just their own buildings.
Portfolio at a glance
See which nodes are online, when they were last seen, and their open alarms across every site.
Security
Secure by design, not by add-on.
Building systems are infrastructure. Aero's security model starts from one rule: nothing gets to reach into the building.
Outbound-only connectivity
Nodes dial out to AeroServer and AeroConnect. No inbound firewall rules, no port forwarding, no exposed controllers.
Authenticated, encrypted connections
Every connection between a node and its supervisor is mutually authenticated and encrypted with industry-standard cryptography.
Controlled enrollment
A node joins a supervisor only through a one-time enrollment step authorized by an administrator.
Signed firmware
Firmware is cryptographically signed and verified before it installs, so only genuine Aero releases run on a node.
Automatic recovery
If a new firmware version fails to start, the node restores the previous version on its own.
Encrypted access, protected logins
AeroView is served over HTTPS, with protection against repeated failed login attempts.
Protocols & drivers
Open protocols at the field level.
Every AeroNode serial port is driver-agnostic. Our goal is to support the open RS-485 and RS-232 protocols found in buildings through Aero drivers, delivered to installed controllers as signed firmware updates.
BACnet/IP
Full client: discovery, polling and COV, priority writes, foreign-device registration, device alarms and schedules.
ShippingBACnet MS/TP
Native RS-485 trunks on every AeroNode, with a frame log for troubleshooting.
ShippingMetasys N2
N2 Open supervision: address scan discovery, point reads, and output overrides with release.
ShippingBACnet server
Selected points published as BACnet/IP objects, plus global schedules as BACnet Schedule objects.
ShippingOn the driver roadmap
- Modbus RTU (RS-485) and Modbus TCP
- RS-232 serial device drivers
- Additional open RS-485 protocols
- BACnet Secure Connect (BACnet/SC) transport
Put Aero on your next project.
Authorized dealers design, install and support every Aero system. Find the dealer for your territory, or talk to us about becoming one.