India’s No.1 Fibre Monitoring Tool
Every ONU on your network reports how much light reaches it. We read all of them, every 10 minutes, from the OLT you already own — and tell you which stretch of fibre went wrong, and who it took with it.
No new hardware. No OTDR. Works with the GEPON and GPON OLTs you have.
Three customers dimmed by the same amount at the same moment. They share that stretch of fibre — so it is one fault, one repair, and the other three never needed a visit.
When six customers lose the same 2 dB at the same moment, that is not six faults. It is one, upstream of the point they share. We find the group, and send one crew.
Every ONU reports its distance as well as its light. The customers affected bracket where the break is — a span of route to walk, instead of a whole feeder to guess at.
A customer raises a ticket. Within three minutes the ticket carries the reading, the likely cause, and whether anyone needs to travel at all. In Telugu, for the technician who reads it.
A reading on its own means little. The same line drifting 1.5 dB over a fortnight is water getting into a joint — visible only if somebody kept yesterday.
Most faults are found by a customer. Ours are found at 07:00, in a report that says what moved overnight and what is still outstanding from last week.
Each operator gets their own address, their own logins and their own plant. Nobody sees anybody else's customers. Ever.
No new hardware, no changes to your network. Everything below reads your OLT’s own management interface, and everything below is running today.
Fifteen minutes, on your plant, with your customers’ readings. Bring an OLT address and a login. Conditions apply.
Live plant, not pilots — across Telangana.
The platform reads the plant today. The work now is to make it explain the plant — where the fibre physically runs, how much it is carrying, and what it is about to do next.
A dB figure says something is wrong; it does not say where to send the van. We are fixing every ONU to its position and drawing the route between them, so a fault appears on a map of your own plant instead of a list of customer names.
Light tells you the fibre is healthy. It does not tell you the port is full. The session data already carries upload, download and time online per customer — aggregated per PON, that turns “nobody complained yet” into a capacity plan you can budget against.
Almost nobody holds an accurate diagram of their own splitters. One snapshot cannot recover it — we measured that, and the noise is larger than the signal. A month of history can: the map gets drawn from which lines move together, not from paperwork nobody updated.
Five makes are driven today — BDCOM, Syrotech, Optronix, Optilink and DBC — over telnet, SNMP or the web console, whichever the box will answer. Each new make is one driver; nothing else in the platform moves. Tell us what you run and it goes on the list.
A customer complains and the ticket already carries the reading, the likely cause, and whether anybody needs to travel — in Telugu, for the technician who reads it. Next is closing the loop, so the resolution reaches the customer without being retyped.
Everything the dashboard shows sits behind an API with per-operator keys, so billing, a CRM or a WhatsApp bot can read exactly what your engineers see. Your plant’s data belongs in your stack, not locked inside ours.
Tell us where you operate and how many customers you carry. We will show you your own plant, not a slideshow.