Advantx L.L.C. is a smart building company based in Kosovo. We design, build and install Stratosfere — our own platform for making a building behave like one system instead of a dozen unrelated installations.
We came to this from installation work, not from a software office. The pattern repeated on every project: a lighting bus commissioned by one contractor, HVAC by another, a security panel nobody could reach, three apps for the client and a configuration that existed only inside one laptop.
Every change after handover meant a site visit. Every fault meant guessing which subsystem had failed. And when the original integrator moved on, the building was effectively frozen.
So we built the thing we wanted to install. One server that owns every bus in the building and presents them as a single set of devices. One interface for the people who live there. One studio for the person commissioning it. And one cloud that keeps every finished site visible, backed up and reachable — so a building can still be improved five years later.
That is Stratosfere, and it is what we install on every project we take on.
They decide the architecture, and they are the reason the product looks the way it does.
Control logic belongs where the devices are. Scenes, schedules, alarm handling and every automation run on the server on site, so a lost internet line is an inconvenience, never an outage.
A device is a device — properties, values, units — regardless of whether it sits on KNX, Zigbee, Z-Wave, Modbus or Wi-Fi. That single abstraction is what lets scenes and automations cross technologies without glue code.
Anything that only its author can change is a liability in a building that lasts 30 years. Configuration is visual, versioned and exportable, and any site can be opened, understood and fixed by someone who did not build it.
The state of someone's home is not a data product. Remote access is explicit, scoped and revocable, and the cloud stores what is needed to support the system — not a diary of the household.
Four products that are really one system. Because we own all four, a gap found on site becomes a feature in the platform instead of a workaround in a cabinet.
The controller in the cabinet: protocol drivers, the device model, the automation runtime, scenes, alarm and the MQTT bus everything speaks over. An on-board Zigbee coordinator means one less box on the DIN rail.
The interface the family actually touches — wall panels, tablets and phones, with rooms, favourites, scenes, a live floor plan and a screensaver that turns into a control surface on a gesture.
Commissioning without config files: the building tree, bus discovery and address tooling, floor-plan editing and a node canvas where automations are drawn, deployed and verified.
The fleet layer for the company: every installed site with live status, outage history, version tracking, one-click configuration backups and remote management of any server.
Before a cable is pulled we agree the subsystems, the bus topology, the panel positions and what the finished handover looks like.
Rooms, devices, scenes and automations are named and structured for the people who will live with them — not left as raw addresses.
After handover the site is monitored, backed up and updatable. Most support questions are answered without anyone driving to the building.
New build or retrofit, one apartment or a whole block — send us the drawing and the subsystems you want covered, and we will come back with a layout and a device list.