PropTech & Smart Buildings
We read meters over Modbus, manage access, calculate charges and take payments, and send a fault alert to whoever will actually drive out.
What does not work in building management
Meters, barrier, intercom, lighting, boiler room — everything installed, everything working, everything separate. The management company sees readings once a month, and residents call when something has already broken.
Second, money. Charges, payments, debts. Data arrives from different places, is merged by hand, and finding out why one flat does not add up costs half a day.
What we do
Remote meter reading
Polling meters over Modbus instead of walking flats and floors.
Access control
Barriers, gates, locks — tied to a resident or tenant, access for a defined period.
Charging and payments
Calculation from readings, payment acceptance, debt tracking. Meter data reaches the invoice without manual transfer.
Faults and alerts
A leak, a consumption spike, stopped equipment — a message to whoever will drive out.
Resident portal
Own readings, own charges, payment history. Fewer calls to the dispatcher.
Owner reporting
Consumption per building, debts, fault rates, comparison between properties.
What it runs on
Modbus RTU/TCP for meters and controllers, acquiring integration for payments, Node.js and PostgreSQL on the server. We do not build smart-home systems for a flat: our part is the commercial and accounting layer of a building, where equipment and money meet.
Frequently asked
Do you build smart homes?
Can existing meters be connected?
How many properties make it worthwhile?
Answers on this topic
Plain explanations without marketing — useful even if you never hire us.
Custom system or an off-the-shelf box: an honest comparison
When a boxed product wins, when custom wins, and the third option: a working system adapted to your process. Lock-in, code ownership, support, migration risk.
Selling on WhatsApp: the 24-hour window and lost messages
How the WhatsApp Business API actually behaves: the 24-hour window, templates, and why an "ok" from the API does not mean the customer saw your message.
Telemetry where the link drops for hours
Telemetry where the mobile link drops for hours: store-and-forward, clock drift, deduplication, staleness on the dashboard, alerts that do not cry.