One appliance. Whole operator. Live in a week.
You don’t need a five-vendor stack to run a growing ISP. Rack a Core X1, boot NOS, and get the network, subscribers and business under one login before the weekend.
Small and greenfield operators up to 10,000 subscribers.
The first years of an ISP are a race against your own back office. Every new subscriber piles onto a spreadsheet, every outage means a WhatsApp fire-drill, and every vendor you bolt on wants its own login, its own admin, and its own headache.
Netxol answers that with a single decision: rack one appliance, and the operator’s brain moves inside it. Provisioning, billing, care, reporting and the AI that ties it together — all under NOS, all logged in the same audit trail.
Because the AI ships turned on, a two-person team can operate like a ten-person team. Chatty AI closes routine tickets, drafts the monthly report, and quietly restarts things it knows how to restart — before you even hear about it.
The economics of a small ISP are unforgiving. Every hour spent stitching four tools together is an hour not spent selling. Every hour spent troubleshooting a mysterious mismatch between the billing system and the network is an hour not spent installing subscribers. Netxol removes both classes of hour by shipping the whole stack — NMM, ACS, RADIUS, CRM, Billing, ERP and the Companion Apps — pre-integrated on the Core appliance.
For a Pakistani or MEA small ISP specifically, the built-in JazzCash and EasyPaisa collection layer is the single biggest operational unlock. Subscribers pay from inside the Netxol Subscriber App on day one, without the operator signing a separate merchant contract with each wallet. See the operational detail in the post on collecting via JazzCash and EasyPaisa at /blog/jazzcash-easypaisa-for-isps.
On the network side, a Core X1 comfortably supports 5,000 active subscribers and up to 12 OLTs. Discovery finds every device on your network; monitoring templates apply automatically; the ACS handles TR-069 zero-touch onboarding for standard CPE; and the AI Engine — bundled — handles the routine tickets a two-person team would otherwise stay up late for. Details on the network side at /products/modules/nmm.
The financial back-office comes with it. Netxol ERP provides a general ledger fit for an ISP, accounts receivable that auto-reconciles against the Billing module, and financial statements produced from live data. Your accountant reviews numbers instead of building them.
Four moves.
Rack the Core X1
One 1U appliance, dual-drive redundant, boots NOS on first power-up.
Onboard in an afternoon
Guided setup imports your OLTs, subscribers and plans in a few clicks.
Give the team a login
Care, engineering, finance — every seat, no per-seat billing.
Let the AI cover the gap
The routine ticket work, the reports, the after-hours cover — handled.
Turn on the payment layer
JazzCash, EasyPaisa, Mastercard, Visa live inside the Subscriber App on day one. Netxol operates aggregation.
Zero-touch CPE onboarding
The bundled TR-069 / TR-369 ACS onboards standard CPE without a truck roll.
Everything you get with this playbook.
We usually pair this playbook with Netxol Core X1.
The X1 is what most ISPs boot when they’re done stitching four tools together. Rack it, plug it into your uplink, and it comes up with the operating system already talking to your network. One appliance, one login, and every corner of the business on one screen.
Operators already running this play.
Questions we get on the first call.
How long does it take to go live?
Small deployments complete in under a week from unboxing the Core to first paying subscriber; larger rollouts scoped in weeks not months.
Do we need to change our existing hardware?
No. NOS ships adapters for every mainstream OLT and router. You keep the gear you own; we replace the tooling above it.
What happens to our data?
Everything stays on your Core appliance by default. Backups go to your object store of choice. No subscriber data leaves your rack unless you turn on an opt-in telemetry channel.
Can we migrate from another platform?
Yes — we run a scoped migration project with matching data mappings and cut-over windows. Standard editions include the first migration.
Other stories in this shape.
Ship an ONT to a subscriber. When they plug it in, NOS provisions it, binds it to their record, and lights up their plan — without a technician touching a config file.
ReadOutcomeMost of what a NOC does at 3 a.m. is small, boring and repeatable. NOS is built to notice those patterns, act on them safely, and keep humans in the loop for anything that isn’t routine.
ReadOutcomeA branded Subscriber App that pays the bill, runs a real speed test, opens a ticket and gives honest outage visibility — routing 40% of the calls your care team never has to take.
Read