Netxol ACS vs GenieACS: from an open-source ACS to an ACS on the ISP graph
GenieACS is the community's go-to open TR-069 server. It gets an FTTH ISP started fast — until subscriber provisioning stops being a monitoring problem and starts being a business one.
GenieACS is the default open-source ACS across small and mid-size ISPs worldwide. It is a fine technical piece of software. The question — like with LibreNMS — is what happens when it succeeds and you have to grow around it.
GenieACS implements TR-069 (CWMP) with a MongoDB backend and a Node.js server. It supports parameter management, faults, tasks and a web UI. Most ISPs adopt it because it is free and works. The issues surface later: no native subscriber model, no billing link, no field-service link, no unified auth, no included USP (TR-369) support at production quality, and no ISP-vendor OLT integration.
Where they differ
| Metric | Before | After | Δ |
|---|---|---|---|
| TR-069 (CWMP) | GenieACS · yes | Netxol ACS · yes | — |
| TR-369 (USP) with MQTT/WS | GenieACS · partial | Netxol ACS · shipping | — |
| TR-181 device model | GenieACS · yes | Netxol ACS · yes | — |
| Vendor-extension handling | GenieACS · per-vendor script by hand | Netxol ACS · vendor adapter framework | — |
| Zero-touch onboarding by service profile | GenieACS · scripting exercise | Netxol ACS · declarative from CRM plan | — |
| Firmware repository + campaigns | GenieACS · basic | Netxol ACS · staged rollout + rollback | — |
| Shared subscriber identity | GenieACS · none | Netxol · CPE ↔ subscriber ↔ service ↔ invoice on one graph | — |
| Deployment | GenieACS · self-hosted (MongoDB + Node) | Netxol Core · pre-installed | — |
The evaluator's question
An ISP running GenieACS at scale usually ends up building a private bridge between it and their CRM, so care agents can see what device the customer has, and so the sales team can trigger a plan change. That bridge is code you own forever. Netxol collapses it: the CPE, the subscriber, the plan, the invoice and the field-visit history all live on the same graph — no bridge to keep alive.
Migration is safe
If you are already on GenieACS, migration to Netxol ACS is well-worn — the platform can import CPE credentials + device-model presets in bulk, and CPE re-registration happens on the CPE's next inform without a truck roll.
A word on TR-181 support quality
GenieACS implements TR-181 broadly, but real-world CPE compliance to TR-181 varies widely. Vendor-specific extensions dominate. The practical differentiator is the vendor-adapter framework: how quickly can a new CPE model be onboarded with correct parameter mapping? Netxol adapter framework is described in the [Netxol NMM page](/products/modules/nmm) and covered in the [TR-369 (USP) adoption 2026 research post](/blog/tr-369-usp-adoption-2026).
GenieACS
New CPE model onboarding
2–5 days (custom preset)
Netxol ACS
New CPE model onboarding
Hours (adapter plugin)
GenieACS
USP MQTT transport, production quality
Partial
Netxol ACS
USP MQTT transport, production quality
Shipping
Migration from GenieACS
Bulk import of CPE credentials and device-model presets from GenieACS is a supported migration path. Re-registration happens on the next CPE inform — no truck roll required. Talk to sales for a scoped plan.