NodivaroOne pane of glass.
Every site you run.
Every tower, plant room and depot in one place, each drawn as a scene you can read at a glance, operate from where you are, and wind back to any moment. When the link drops it keeps recording, and hands you every reading when the link returns.
The sites that matter are the ones you cannot get to.
Nobody is standing in them. A tower off the R31, a plant room behind a locked gate, a pump station four hours from the nearest technician. When something goes wrong there, the cost is not the fault. It is the six hours before anyone knew, and the second truck roll because the first one took the wrong part.
Most platforms answer that with a list of numbers. A list is fine once you know the site. It is useless at 03:00 when the person on call has never been there.
Nodivaro answers it with the site itself: the room, drawn, live, and operable. You can see which breaker is open, throw it, and watch the current come back.
One document per room.
Four ways to read it.
You build the room once. Nodivaro draws it four ways from that single document, so the engineer who wants a schematic and the technician who wants to recognise the cabinet are looking at the same live data, not at two drawings that will disagree by Thursday.
Live. Every object binds to a real metric and carries its own reading.
Operable. Click the object and it acts on the equipment, through a policy that can refuse, with the whole thing on the audit trail.
Rewindable. Scrub back and the room replays: the values, the flows, the alarms, as they were.
Honest. When the data behind an object goes stale the flow stops and the object greys. Nothing on this screen animates on data that is not arriving.
Most of this market calls that a digital twin. We call it a scene, because ours can be operated and wound back, not only looked at.
The link will drop.
You should not lose the data.
A site on an LTE modem in the Northern Cape is offline more often than anyone likes to put in a proposal. The gateway keeps reading its equipment through the outage and holds every sample on disk. Nothing is deleted from that buffer until the platform has written it to the database and said so.
Cut the link below and watch what happens.
Acknowledged, not assumed. Each batch carries an id. The gateway keeps its copy until the platform acknowledges that exact id after the database commit.
Tested on the real stack: an 83 second outage, the buffer went from 0 to 326 rows and back to 0, and nothing was lost.
Talks to what is already bolted to the wall.
You are not replacing the rectifier because of a monitoring decision. The gateway speaks the protocols your equipment already speaks, and a new device type on a protocol we support is a register map, not a project.
- Modbus RTU
- Modbus TCP
- SNMP v2c / v3
- CAN bus
- Serial ASCII
- MQTT
- HTTP
- RS-485
- GPIO and dry contacts
- ONVIF and RTSP
- OPC-UA
- BACnet/IP
- LoRaWAN
Outlined entries are scoped engagements rather than shipping drivers.
Priced per site.
Nothing else moves.
You pay for your account and for each site. Add a technician to the roster, tighten a poll interval from a minute to ten seconds, wire in forty more sensors at a tower, and the invoice is the same at the end of the month.
Numbers off the running system.
Figures taken from the live platform carrying 58 devices and 165 active series at 46 samples a second. We would rather publish a number we measured than one that reads better.
Where the name comes from.
People ask. It is not a jumble of letters chosen because the domain was free. It is three ideas, and they are the three things the platform does.
nodi- + vi- + -varo
In this world everything is a node, and an estate is not a handful of sites. It is thousands of connected things, each with its own address, its own protocol and its own way of failing.
sensors · PLCs · RTUs · single-board computers · ESP32 · inverters · power meters · UPS · weather stations · cameras · access control
The v is shared. Vi and varo run together into one letter, which is why the word is eight letters and not ten, and why it is easy to say once and remember.
Seeing all of it at once, and understanding it. Live telemetry, alarms that have learned what normal looks like, analytics, and the scene that puts a reading back on the piece of equipment it came from.
Raw device data is not information until somebody can act on it at three in the morning.
The ending carries overview, vantage, horizon and command. It is deliberately not tied to solar, or to telecoms, or to any one industry, because the platform is not either.
You are not only watching. You can reach in and change something, and the platform will tell you honestly whether it worked.
A complete view, and intelligent control, of every connected node.
Bring us two sites and a week.
A pilot is two or three of your real sites, on real hardware, with your own equipment and your own data. It is quoted and time boxed, with a written expansion path, and the onboarding fee is credited back in full when it converts.
We will tell you in that week whether this fits. If a driver does not read your rectifier correctly, you have not bought anything yet.