Built for developers and system integrators

xSERVA is built on an open integration layer, not a closed appliance. Every connected protocol, BACnet, KNX, MQTT, and Modbus, is normalized into one data model, giving integrators a single point of access instead of four separate systems to wire together on every project.

Talk to Our Integration Team
Two engineers seen from behind at a standing desk in a dim office at night, studying a large wall-mounted display glowing with soft blue light.
Integration work is a conversation with our team today, not a download.
A dark desk at night, a mechanical keyboard lit from the side and two monitors angled away so only their glow is visible, a mug and a notebook beside them.
An integration layer is judged at eleven at night, by whoever is still trying to make it work.

An open integration layer, from the ground up

Instead of treating each protocol as an isolated silo behind its own vendor tooling, xSERVA was architected so that BACnet objects, KNX group addresses, MQTT topics, and Modbus registers all resolve into a common internal point model. That normalization is what makes cross-protocol dashboards, alarms, and automation rules possible without hand-built bridging logic for every project. For integrators, this means the hard work of protocol translation is already done at the platform level, so engagement can focus on mapping a building’s actual devices rather than reinventing interoperability from scratch.

A long cable tray run above a ceiling void, bundled data and power cabling combed into separate trays with regular supports, disappearing into perspective.
An integration is only ever as reliable as the physical path underneath it.

REST and webhook connectivity, conceptually

xSERVA is built on an open integration layer designed with REST-style access and webhook-driven event delivery as core architectural principles, not as an afterthought bolted onto a closed system. This is a description of the platform’s design intent, not a listing of documented, publicly available API endpoints, because a public API has not shipped yet. When it does, the goal is for external systems to be able to query point data and receive real-time event notifications through standard, well-understood web patterns, rather than proprietary protocols that require custom client libraries.

Native protocol objects — a BACnet analog input, a KNX group address, an MQTT topic and a Modbus register — are normalised into one addressable resource model, so nothing above that layer needs to know which protocol a point came from. REST-style access and webhook delivery are marked as architecture today; a public documented REST API and an SDK are marked clearly as roadmap and not yet shipped, with integrators engaging directly through scoping, support and joint delivery until then.
What exists today is the layer. The public API and SDK on top of it are still roadmap.

Roadmap: public API and SDK

Roadmap — not yet shipped. The items below describe planned direction, not current capability.

A publicly documented REST API and an accompanying SDK are on the xSERVA roadmap, intended to let developers and integrators build against the platform directly rather than working exclusively through the xSERVA interface. Until that ships, integration work is scoped and delivered directly by our team on a per-project basis, ensuring every connection is validated against the actual devices and network conditions on site.

How integrators engage with us today

Because the public API and SDK are still in development, system integrators currently work with xSERVA through direct engagement with our team: scoping the protocols and device counts on a project, confirming network and hardware requirements, and coordinating commissioning alongside the rest of the building program. This hands-on model lets us validate integration work against real devices before it goes live, and it feeds directly into shaping what the public API and SDK need to support once they are available.

Discuss an Integration Project

Frequently asked questions

Is there a public xSERVA API today?

Not yet. xSERVA is architected on an open integration layer designed for REST and webhook-style connectivity, but a public, documented API is on our roadmap rather than something generally available today. Message our team on WhatsApp to discuss integration timelines for your project.

Can xSERVA already integrate with third-party systems?

Yes, at the protocol level. xSERVA natively connects to BACnet, KNX, MQTT, and Modbus devices and systems, which covers the large majority of building-side integration needs today. Application-layer integrations with external software are handled case by case while the open API is developed.

Will there be an SDK?

An SDK is on our roadmap alongside the public API, intended to give integrators a faster path to building on top of xSERVA. It has not shipped yet, and we will update this page and notify our integrator community when it does.

How do I become an xSERVA integration partner?

Message Patrick directly on WhatsApp using the button on this page. We work directly with system integrators on a project-by-project basis to scope protocol coverage, deployment, and any custom integration needs.