Four protocols. One platform. Zero translation layer.
Buildings do not run on a single protocol, and pretending they do is how integration budgets disappear. xSERVA was built from the ground up to speak BACnet, KNX, MQTT, and Modbus natively, so every device on site — regardless of how it talks — lands in the same dashboard, the same alarm queue, and the same energy model.
Book a DemoWhy interoperability matters
A modern commercial building typically layers HVAC controllers speaking BACnet, lighting and blinds wired for KNX, a growing fleet of MQTT-connected sensors, and legacy meters or generators still running Modbus. Historically, unifying that mix meant stacking a separate head-end for each protocol, then bolting on custom middleware just so the systems could exchange a single data point. Every bridge added a point of failure, every vendor added a support contract, and every renovation meant re-engineering the handoffs again.
xSERVA removes the translation layer entirely. Instead of treating BACnet, KNX, MQTT, and Modbus as four separate integrations bolted together after the fact, the platform normalizes all four into one internal data model at the point of ingestion. A BACnet air-handling unit, a KNX lighting scene, an MQTT temperature sensor, and a Modbus energy meter all resolve to the same kind of point object inside xSERVA — which means monitoring, alarming, scheduling, energy analysis, and AI-driven insight all run against a single consistent dataset, not four disconnected ones. For system integrators this means faster commissioning and fewer support escalations. For building owners it means one login, one contract, and one system to audit instead of four.
Critically, this is native support, not a superficial pass-through gateway. xSERVA talks to each protocol at its own depth: BACnet is addressed at the object and property level, not just as a coarse point count; KNX is addressed at the group-address and datapoint-type (DPT) level, preserving the semantics of every lighting and blind actuator; MQTT is addressed at the topic and payload level, including nested and wildcard subscriptions; and Modbus is addressed at the individual register level, with correct data typing per device. A gateway that merely forwards raw values loses that depth and pushes the translation problem downstream to whoever configures the dashboard. xSERVA keeps the protocol-native detail intact all the way through the platform, which is what makes cross-protocol rules, alarms, and reporting trustworthy rather than approximate.
Explore each protocol
BACnet
The dominant standard for commercial HVAC, controllers, and building-wide device communication, with BACnet/IP, MS/TP, and BACnet/SC support inside xSERVA.
KNX
The dominant standard for lighting, blinds, and room-level automation wiring, with decentralized topology and ETS project import supported inside xSERVA.
MQTT
The dominant standard for lightweight sensor, IoT, and edge-device telemetry, with broker-based publish/subscribe messaging supported inside xSERVA.
Modbus
The dominant standard for meters, generators, and industrial equipment interfacing, with both Modbus TCP and Modbus RTU supported inside xSERVA.
Not sure which protocol matters most for your building?
See how BACnet, KNX, MQTT, and Modbus stack up against each other on topology, transport, security model, and the persona each one best fits.
Frequently asked questions
Does xSERVA really support BACnet, KNX, MQTT, and Modbus natively?
Yes. All four protocols are supported natively inside xSERVA, with no third-party gateway or bridging software required to bring devices into the platform.
Can xSERVA manage a building that mixes protocols, like BACnet HVAC and KNX lighting?
Yes, that is exactly the scenario xSERVA is built for. BACnet controllers, KNX lighting and blinds, MQTT sensors, and Modbus meters all appear in the same dashboard and data model.
Do I need separate software licenses for MQTT and Modbus devices?
No. Protocol support is built into the core xSERVA platform, so adding MQTT sensor fleets or Modbus meters does not require a separate license or a separate application.
How do I compare BACnet, KNX, MQTT, and Modbus side by side?
See the full protocol comparison table, which lines up topology, transport, typical use case, security model, and best-fit persona for all four protocols in one view.