An ACS talks to you in parameters. Corbrain talks to you in intent.
TR-069 (also written TR069) management tools work at the device level: someone has to write InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.SSID, and repeat that translation for every brand, model, and firmware deployed. Business logic ends up scattered across scripts that only the person who wrote them understands.
Corbrain inverts the order. You define a service profile in the terms of your operation — the customer’s WiFi, the service VLANs, telephony, the LAN — and the platform translates it into the concrete parameters for each device. That translation lives in data, not code: onboarding a new model doesn’t require a new product version.
Desired state, not commands. You don’t send orders and hope for the best. Corbrain keeps track, for every device, of how it should be configured and how it actually is. When the two differ — a technician touched the ONT, a unit was factory-reset, a firmware changed a value on its own — the platform detects the drift and corrects it.
A hundred thousand devices aren’t managed one at a time. They’re declared once, and the network converges.
Corbrain® Access covers the whole access network. Its two modules, one half each.
The plant and the subscriber’s equipment are two halves of the same problem, and they’re almost always handled by two different systems someone keeps in sync by hand. Corbrain treats them as one — or as each on its own, if that’s what you need today.
Corbrain CPE
The subscriber’s equipment, over TR-069. The ONT and everything behind it: WiFi, service VLANs, LAN and DHCP, telephony, port forwarding, firmware, and diagnostics. It ships with its own TR-069 ACS server built in — nothing separate to install or maintain.
Corbrain OLT
The plant, over CLI, SNMP, and NETCONF. ONT provisioning and deprovisioning, service profiles, optical status and power levels, ports and cards. Sees the device as soon as it connects to the fiber, before it even has service.
Corbrain® Access
Both modules, one platform. Access-network management tends to live scattered across several systems — by brand, by device, by function — and every activation, every change, and every ticket means going through all of them. Access brings it together in one platform: the plant and the subscriber’s equipment, from any vendor, run from the same place. From the fiber to the customer’s WiFi, on one screen.
Together, under Corbrain® Access: the OLT detects the ONT the moment a technician connects it, even before it’s declared. You authorize the activation from the same screen, and as soon as the device has service, Corbrain CPE takes over and applies the right profile. One system, one activation.
Truly multi-vendor — and we tell you exactly how far.
Protocols. TR-069/CWMP, SNMP, NETCONF, and SSH/CLI. That’s the floor: if your device speaks any of these, Corbrain can talk to it.
Certified models. Every model we manage was tested against real hardware, on an exact firmware version, and certified against that combination. Our list of certified models is shorter than other vendors’ lists of “compatible” ones, and that’s exactly the point: we’d rather tell you a model isn’t certified yet than have you find out in production.
Certifying a new model takes days, not product releases: it’s declared on the platform, not coded.
On your servers, or on ours.
On your infrastructure
A single binary, written in Rust. No Node.js, no interpreters, no stack to maintain: copy it, configure it, run it. Your network and subscriber data never leave your network.
Managed by Corbrain
We host it, update it, and monitor it. You log in through the browser and operate — no servers to provision.
It’s the same platform either way. You can start managed and move to on-premise later, or the other way around.
Nothing gets written to a device unless it’s certified.
Pushing bulk configuration to thousands of devices in production is the riskiest thing an ISP does. Corbrain treats it that way.
Compatibility. Can this model apply this profile? The platform answers that on its own, cross-checking the profile against what the model can do. If something’s missing, it tells you exactly which field, and why.
Certification. Has this configuration been tested on this model, with this firmware? That’s not decided by an algorithm: a person certifies it against real hardware. And if the profile changes afterward, the certification expires on its own and has to be re-tested.
Only once both are green does Corbrain write. Reading, monitoring, and diagnosing always work.