What is eCloud OLT Controller

The NMS and ACS for your fiber network, in one panel.

eCloud OLT Controller is a web-based system for ISPs running GPON and EPON networks. It monitors your OLTs and every ONU, anticipates failures, groups alerts by root cause, provisions subscribers without opening a terminal and manages the subscriber’s router over TR-069. All from the browser, including on the technician’s phone.

Who it’s forFiber ISPs of any size: the NOC, field technicians, support and administration all work from the same data.
What it solvesFewer vendor-specific consoles, fewer duplicate alerts, fewer emergency truck rolls and fewer subscriber calls to change the WiFi password.
How it worksIt’s a web panel: it connects to your OLTs over SNMP and CLI, and to each subscriber’s router over TR-069. No need to switch OLT brands or install anything on the ONUs.

The concepts, in plain language.

Six acronyms that show up all over this site, and what each one means inside eCloud.

NMSNetwork Management System: The system that watches every device, keeps its history and alerts you when something goes out of the ordinary. In eCloud, the NMS reads your OLTs and every ONU: optical power, traffic, device health, alarms and status.
ACSAuto Configuration Server: A server that remotely manages subscribers’ routers (the CPEs). eCloud ships with a built-in ACS based on GenieACS: from the subscriber’s record you can change the WiFi, the connection or the voice line without a home visit.
TR-069CWMP, from the Broadband Forum: The protocol the subscriber’s router uses to talk to the ACS. eCloud works with both data models vendors use (TR-098 and TR-181) and with TR-104 v1 for voice.
OLT and ONUOptical Line Terminal / Optical Network Unit: The OLT sits in your node and distributes fiber through its PON ports; the ONU (or ONT) sits in the subscriber’s home. In between are splitters and NAP boxes.
GPON and EPONThe two passive fiber technologies: ISP networks use one or the other depending on the OLT brand. eCloud works with both: for example, V-SOL V1600G (GPON) and V1600D (EPON), or C-Data FD16xx (GPON) and FD12xx/FD13xx (EPON).
SNMP and CLIHow each OLT is read: SNMP (v2c and v3) for periodic polling, and the command line over SSH or Telnet for whatever the OLT doesn’t expose over SNMP and for provisioning. Each brand’s profile knows which to use in each case.

How it connects to your network.

The panel lives in the cloud and reaches your equipment through the same paths you use today.

The panelA multi-operator web application: each ISP sees only its own data, with its own users and roles. It installs as an app on the technician’s phone.
OLT accessOver a public IP or, if your OLTs are on a private network, through a WireGuard tunnel to your MikroTik (RouterOS 7.1 or later). SNMP, SSH/Telnet and the OLTs’ syslog all travel over that path.
The outside plantEach ONU is mapped to its PON port, its NAP box and its splitter. That’s how alerts are grouped by cause and how the power it should be receiving is calculated.
The subscriber’s routerIt connects to the ACS on its own over TR-069 and lands on the same record as its ONU: fiber and WiFi in a single view.
Your billingWispHub, Mikrowisp or eCloud-ISP request suspensions and reconnections, and the panel carries them out on the OLT, with a brake against mass cutoffs by mistake.

Every feature.

Twelve modules sharing the same data. All of them come with every plan.

Monitoring (NMS)

Every OLT, port and ONU, with its history.

Receive and transmit optical power for every ONU, over SNMP or CLI. An impossible reading is discarded: a value is never made up.
Traffic on uplinks, PON ports and ONUs via standard IF-MIB, with 64-bit counters.
CPU, temperature and uptime for every OLT, with history and trend.
Extended optical monitoring (DDM/DOM): what the OLT receives from each ONU and the status of each port’s optical module (laser bias current, temperature, voltage).
Distance to each ONU and real-time alarms via syslog on OLTs that report them (currently ZTE).

Analytics and forecasting

The curve before the outage.

90-day forecast for four series: each ONU’s power, each PON port’s laser, uplink and port utilization (daily 95th percentile) and each OLT’s temperature.
For each one, when it would cross its threshold and with what confidence; if confidence is low, it’s shown as uncertain.
A warning when an ONU drops 3 dB below its own seven-day history, even if it’s still above the threshold.
Optical budget per ONU: the power it should receive based on its distance, its splitter and its port’s module, compared with what it measures.
SLA reports that separate availability from measurement coverage, exportable to CSV.

Root-cause alerts

One notification per failure, not one per ONU.

More than 20 alert types: OLT down or rebooted, ONU with no signal or low power, PON port or NAP box down, uplink saturated or down, VPN tunnel down, optical module, overdue backup and more.
Cause chain: VPN tunnel → OLT → port or NAP → ONU. Only the failing link is notified, with a count of what’s affected.
If most of a NAP reported loss of power, the alert says so: a likely power outage, not a fiber cut.
Escalation from warning to critical with just one new notification, and automatic closing on recovery.
Via Telegram, email or signed webhook; thresholds editable live, and maintenance windows that don’t count toward the SLA.

Provisioning

From the box to a subscriber online, with no terminal.

Expected ONUs: load the serial number ahead of time and, when the ONU shows up, it authorizes itself with your template.
Authorize, move to another port or replace the device from the panel: if the OLT rejects the change, it rolls back on its own.
Bulk actions with preview: up to 50 at a time or up to 5,000 in the background, with a brake if an OLT rejects 3 in a row.
Reconciliation between the OLT and the inventory, without sending commands to the device.

ACS / TR-069

The subscriber’s router, with no visit.

WiFi: network name, password and channel, on TR-098 and TR-181.
Internet: PPPoE username, password and VLAN.
Voice: the router’s SIP account (TR-104 v1).
Remote reboot and factory reset.
Cross-diagnostics: if the WiFi is fine and the optical power is dropping, the problem is in the fiber.

Batch firmware

Hundreds of devices, no all-nighters.

OLTs over SSH (the OLT downloads the image via TFTP, FTP, HTTP or HTTPS), ONUs through the OLT (OMCI) and routers over TR-069.
Image verified with SHA-256, and a compatible model required.
Batches of up to 200 devices, with a time window in your local time and controlled parallelism.
Automatic brake: if failures reach √n (minimum 2), the batch pauses.

FTTx maps and topology

The outside plant, drawn and live.

Outside plant editor: cables from 1 to 288 fibers, splice closures, splitters from 1:2 to 1:64, and poles.
Coverage and occupancy for each NAP box, and ONUs down per NAP.
Network status on the map, updated every minute, and live topology from the OLT to the subscriber.
Import from Excel or CSV.

Integrations and API

Your billing suspends and reconnects on its own.

WispHub (instant notifications and periodic checks), Mikrowisp (periodic checks) and eCloud-ISP (instant notifications).
Brake: nothing is suspended if a check asks to cut off more than 10 ONUs or more than 10%.
Public API to query, suspend and reactivate contracts, with API keys.
Signed webhooks (HMAC-SHA256) for alerts, OLT status changes, authorized ONUs and maintenance windows.

Installer app

The field technician, on their phone.

The panel installs as an app on the phone.
Serial number barcode scanning (in Chrome for Android).
Live signal measurement during installation.
Installation record with GPS location that can’t be edited.

Security

Your data and your subscribers’ data, protected.

Isolation between ISPs at the database level (PostgreSQL Row-Level Security): each operator sees only its own data.
Two-factor authentication (TOTP) and passkeys, with an attempt limit.
Three roles per operator (Administrator, Support and Installer), enforced on the server.
OLT credentials encrypted with AES-256-GCM, and an audit log exportable to CSV.

Day-to-day operations

What you don’t see, but holds everything up.

Configuration backups for OLTs whose profile supports it, when they’re added and, if you enable it, on a schedule.
Read-only CLI and SNMP explorers: query an OLT from the panel with no risk of changing anything.
Signed updates, applied right away or at the time you choose, with rollback.

Knowledge base

Procedures at hand, by brand.

More than 170 articles with procedures for V-SOL, ZTE, Huawei, C-Data and HALNy ONTs.
CLI commands from 33 OLT vendors, organized by task and marked as read or write.
Initial setup guide for a brand-new OLT, by brand.

With the OLTs you already have.

Profiles for ZTE, Huawei, V-SOL and C-Data, plus generic SNMP monitoring for any other OLT. The ZTE C320 is validated in production; the rest of the profiles are fine-tuned with your equipment during onboarding.

See what it does with each brand →

Who uses it every day.

NOCSees the whole network in one panel, gets one alert per failure with its cause, and plans ahead with the forecasts.
Field technicianInstalls from the phone: scans the serial number, measures the signal and closes the installation record with GPS.
SupportResolves issues without a visit: sees the subscriber’s fiber and WiFi on the same record and changes the router’s configuration.
AdministrationConnects billing so suspensions and reconnections happen on their own, with SLA reports to show.

Frequently asked questions.

Do I have to replace my OLTs or ONUs?

No. eCloud works with ZTE, Huawei, V-SOL and C-Data OLTs, and monitors any other one via generic SNMP. Nothing is installed on the ONUs.

My OLTs are on a private network. How does the panel reach them?

Through a WireGuard VPN tunnel to your MikroTik (RouterOS 7.1 or later). The tunnel only accepts private networks and doesn’t overlap with other operators’ networks.

Do I need a separate ACS for TR-069?

No: the ACS is built in. Your subscribers’ routers connect to it and show up on each subscriber’s record, next to their ONU.

Is my data kept separate from other ISPs’ data?

Yes. The isolation lives in the database itself: if a query has no operator, the result is an error or zero rows, never someone else’s data.

Do I have to install anything on the technicians’ phones?

No app store needed: the panel installs as an app from the phone’s browser.

What does each plan include?

Every feature comes with every plan; what changes is how many OLTs, ONUs and users it allows, and the support. There’s a 14-day free trial.

Tour the modules → · See pricing →

Fewer trucks on the street. More subscribers who stay.

We’ll walk you through eCloud OLT Controller with your own OLTs, in 30 minutes.

Watch the prediction again