Your whole ISP on one platform, from the core switch to the GST return.
Subscribers and RADIUS, billing and collections, partners and their wallets, the network and its outages, analytics, and the records the DoT can ask for. And an assistant that does the work when you ask, and changes nothing until you say yes.
A collector on a doorstep, in their own words. The card is what the platform is about to do; nothing happens until someone taps it.
lines measured on 350 routers
1.5 lakhlines measured on 350 routers
RADIUS servers, and sign-ins answered while the API is down
2RADIUS servers, and sign-ins answered while the API is down
incident for one failure, at the device that failed
1incident for one failure, at the device that failed
home visits when your subscribers move across
0home visits when your subscribers move across
The platform
Everything your ISP runs, in one place
Twelve workspaces, one for each part of the business. Each person lands on the one their role needs. Switch off a module you do not use; its data stays.
Today and the assistant
The morning brief, and a command bar that does the work.
What needs you today, from live data
Ask in your own words, in English or Hindi
Every change is a card you confirm
Subscribers and sales
From the first enquiry to the hundredth renewal.
Enquiries, follow-ups and one subscriber record
KYC from the signed Aadhaar QR, or documents
A self-care portal with OTP sign-in and pay links
RADIUS and policies
Sign-in, speed and fair use, enforced on the router.
PAP, CHAP and MS-CHAPv2, MAC binding, session limits
Rate, burst, priority, fair use, a slow lane for unpaid bills
Speed changes live over CoA; suspending cuts the line
Network operations
The network as a tree, from the core switch to the home router.
Devices found over LLDP, confirmed once by a person
Ping each minute, syslog and traps, switch health
Config backups, switch audit and change requests
Billing and GST
Tax documents an accountant can file.
Rule 46 invoices, credit notes, GSTR-1 and Tally
E-invoicing: held for the IRN, printed with its QR
Combo plans, add-ons, booked packs and Razorpay
Collections and cash
Money traced from the doorstep to the bank.
A ladder of reminders, a slow lane and suspension
Cash collected, handed over, counted and matched
Bank reconciliation, TDS, deposits and refunds
Partners
Distributors, sub-distributors and LCOs.
Levels, roles and a commission cascade
Prepaid wallets with GST tax invoices
Price books, plan groups and a partner API
Enterprise
Leased lines with a contract behind them.
Accounts above their sites, circuits on switch ports
Outage reports drafted at restore, SLA reports monthly
SLA credits proposed as credit notes
Service desk and field
Complaints closed by the right person, in time.
Priority from impact, SLA by segment, breach on time
The desk on WhatsApp: diagnosis first, then a ticket
Work orders, dispatch and an app for engineers
Analytics
Traffic, capacity and revenue, area by area.
Traffic per area and per link, hour by hour
When each uplink fills, with an upgrade proposal
Every answer says how fresh and complete it is
Inventory and builds
The stock you hold and the network you are building.
Stock and every movement of it
Network builds and what they used
Customer devices through your own GenieACS
Compliance
The records your licence can demand.
IPDR, NAT and flow records, kept two years
Lawful-interception requests and TRAI reports
None of it ever goes to the AI model
Three people, one morning
Built for the people who actually run an ISP
Most ISP software is built for the person who bought it. This is built for the owner at 7am, the collector at the door, and the customer on WhatsApp.
The owner, at 7am
“What needs me today?”
Cash collected and not yet counted, lines expiring tomorrow, tickets past their SLA, routers out of contact — computed that morning from the live data, never a stale report.
The collector, at the door
“Sharma ji paid 800 cash”
The payment recorded against the right invoice, joined to their own cash handover, after they confirm. Money is not in the bank until somebody else counts it — and the platform says so.
The customer, on WhatsApp
“net slow hai?”
The real reason, in Hindi: you have used your fair-use data, or a bill is overdue, or there is a fault and an engineer is coming. Not a ticket number.
The network
One failure, one incident, everyone told
A probe on your management network reads every switch and router and changes none. When a branch goes silent, the platform finds the highest device that failed, opens one incident there, and tells the subscribers and operators behind it.
A tree a person confirmed
Each device's parent comes from LLDP or a MikroTik's neighbour table. A person confirms it once, so a wrong guess never raises an alarm.
Down means down
A missed ping counts only for a device that has answered steadily for ten minutes; a trap or syslog counts at once. A device that never answered reads "cannot tell", with the reason.
Planned work stays quiet
What is silent under a maintenance window is behind it, not an outage, and leased-line uptime leaves it out.
Read-only on every device
Ping, SNMP reads, the show commands of a config backup, and listening for syslog and traps. Enabling anything on a switch stays your engineers' change.
IncidentDistribution switch down
CoreCORE-01Up
DistributionDS-NORTH-03Down since 10:42
AccessAS-14 · AS-15 · AS-17Behind DS-NORTH-03
RouterMT-NORTH-2Behind DS-NORTH-03
Subscribers affected
312
Operators told
4, at 10:44
NOC ticket
TKT-2026-00731 · P1
One failure as the NOC board shows it: the top device is the outage, the rest are behind it. Example data.
Analytics
Know which link fills up before it does
An analytics tier on its own servers reads the platform by change capture, and the switches by sFlow and the probe's samples. Nothing in it can write back.
Traffic by area
Per router and per switch port, each hour, rolled up through the device tree.
Capacity runway
When each uplink fills, from its own trend, with an upgrade proposal and a 30-day backtest of the forecast.
Revenue by area
What each area earns, beside what it carries and what its devices cost.
Answers that admit gaps
Every answer carries its freshness and coverage. A stale source reads unknown, not zero.
The bad day
Built for the evening the server has a problem
An ISP's worst hour is when its own platform fails. These are the parts that keep subscribers online through it.
RADIUS outlives the API
When the API gives no answer, FreeRADIUS answers a known sign-in from its last accept. It never sends a reject that reads as a wrong password.
A second RADIUS server
A standby on its own host, with its own cache and spool, written to every router as its second server.
Accounting is never dropped
When the API cannot take a packet, it is spooled to disk and replayed in order.
Measured, not promised
150,000 lines on 350 routers, on a rig shaped like production: normal load, the evening peak, a router reboot and a storm of rejects.
Switching
Move from your current system without visiting a single home
Your subscribers come across with their logins, line passwords, packs and KYC. Move one operator at a time, smallest first, and put it back in one step if anything is wrong.
1
Import
Your current system's export, or one sheet per operator, read into subscribers, plans, partners and routers. A dry run shows every row first.
2
Shadow
The routers are adopted and watched. Your current system keeps answering their sign-ins.
3
Rehearse
Every line online on a router is signed in as a dry run. The router moves only if every one of them would be served.
4
Cut over
An operator's routers move together and are watched. If lines online at the cut-over are refused, they all go back together.
5
Learn
A line that arrives without its password learns it from its first good sign-in, from a device it was seen with.
The routers keep their configuration. Only their RADIUS settings change.
The floor
The things ISP software usually gets wrong
Not features. The compliance and honesty that decide whether an accountant, a tax officer or a customer can trust a document you gave them.
A tax invoice, not a receipt with INVOICE on it
Both GSTINs, place of supply with its state name, SAC, the CGST/SGST split, a financial-year series within Rule 46's sixteen characters, INV2627-0000001, and a credit note that names the invoice it reverses. GSTR-1 computed from the invoices, never stored.
A dashboard that prints — when it does not know
Churn is null when there is no base to measure it against. Routers are online, offline or unknown. Nothing is zero because a query returned nothing.
Cash has a chain of custody
Collected, handed over, counted by somebody else, and matched to your bank statement. Four different people's acts, recorded as four.
Built for the rules the licence imposes
KYC from the signed Aadhaar QR, keeping only the last four digits. IPDR, NAT and flow records in the DoT's format, kept two years, archived before deletion. DLT template ids on every SMS. Compliance is yours to hold; the platform keeps the records that let you.
Wi-Fi sold by the hour, without inflating your numbers
Hotel and café vouchers on the same RADIUS. A voucher is a credential, not a subscriber, so a busy Saturday never reaches your ARPU.
Every message in your name
WhatsApp first in Meta-approved wording, an SMS when WhatsApp fails, email alongside. A message not sent is recorded with the reason.
Open
Yours to connect to
Nothing here is locked in. The accountant, the assistant you already use, your partners' systems and your own scripts all get a door.
Tally export
The month as Tally XML: sales, receipts and credit notes, ready to import.
MCP, for any AI client
Every operation, as tools, for Claude or anything that speaks MCP. It acts as the person who signed in, with exactly their permissions.
A documented API
Every screen uses the same API you can. Staff and partners hold their own tokens, revocable in one click.
Your own ACS, your own routers
We drive GenieACS and select your MikroTik templates. We never push queue config and never build a worse copy of a tool you already run.
Honest status
What is not built yet
Everything else on this page exists and is in the product today. This list is kept because it is true.
Voice: the assistant reads and writes, it does not listen
PM-WANI's central registry handshake (the accounting it needs is there)
Offers and campaigns over WhatsApp
A direct API connection to the e-invoice portal: its JSON goes out and its answer comes back by file
GSTR-3B, and filing GSTR-1 on the portal: the tables are computed, the filing is your accountant's
DPDP erasure requests and a consent manager: the notice and consent links are there
EAP and 802.1X sign-in
Refunds to the gateway on their own: a credit note waits for staff to apply it
Pro-rating an add-on added mid-month
Labour cost inside a network build
Where a number is not genuinely known, the screens show a dash instead of inventing one. This page follows the same rule.
₹10 per active subscriber, per month
Everything included, the assistant too. No setup fee, no per-staff fee.