Billing & subscribers
Billing EngineBasic & PremiumPPPoE and static IP billing, M-Pesa and RADIUS in one self-enforcing loop
Hotspot & Vouchers3% of collectionsVoucher and M-Pesa hotspot access — users are free, we take 3% when you collect
CRMPremiumLeads pipeline, customer 360 and campaigns, next to the billing truth
MessagingBasic & PremiumRenewal reminders, receipts and outage notices — to exactly who they concern
Network operations
OLT/ONU ManagementPremiumHuawei, ZTE and VSOL OLTs and every ONU behind them, one console
ACS / TR-069PremiumFleet-wide CPE control: WiFi, diagnostics and config over TR-069
Device ManagementPremiumRouters, switches and APs monitored — know before the subscriber calls
Fiber MappingPremiumThe plant on a map — OLTs, splitters, ONUs — however big it grows
Back office & AI
InventoryPremiumLedger-driven stock for ONTs, routers and drums — plus full procurement on Plus
AI AssistantPremiumAsk the platform questions in plain language, answered from live data
10 modules — Basic covers the billing core, Premium includes every one of them.
Explore products →Smaller footprint
Estate & hotspot ISPBasicMany subscribers, few ONUs, hotspot in the common areas
Home fiber / neighborhood WISPPremiumPPPoE to every home, one ONU per household
Larger footprint
Regional fiber operatorPremiumMany OLTs and ONUs, mixed vendors, one NOC
Multi-brand ISP groupPremiumShared infrastructure, several brands
Four kinds of ISP, each with the plan that fits and a month worked out on the published prices.
Compare solutions →Guides
M-Pesa Daraja setupSTK Push and C2B on your own paybill
Billing, explainedTwo plans, volume bands, the math
Onboarding an OLT vendorHuawei, ZTE and VSOL side by side
Playbooks
Static IP to PPPoEConverting a live network safely
The migration playbookOff spreadsheets, onto CoreSync
Reducing disconnection complaintsProactive renewal reminders
Case studies
Automating renewals at scaleAn estate ISP, illustrative walkthrough
A multi-site fiber NOCTopology and optical alerts in practice
The migration playbook: moving off spreadsheets and manual M-Pesa reconciliation without a day of subscriber downtime. Most ISPs migrate in 1–2 days.
Read the migration playbook →Products — Billing Engine
Billing that enforces itself on the network
Plans, payments, RADIUS and disconnection in one loop: a lapsed payment suspends the session, an M-Pesa payment restores it — no spreadsheet, no manual switch-off, no argument about who paid.
What it does
Billing Engine, in specifics
PPPoE / RADIUS billing
FreeRADIUS-backed authentication with live sessions, speed profiles enforced the moment a plan changes, MAC binding and CGNAT-aware pools.
Static IP billing
Fixed-IP subscribers billed by plan rather than session — public-IP add-ons and mixed static + PPPoE fleets on the same account.
M-Pesa built in
STK Push and C2B on your own paybill, matched to the subscriber by account reference first, applied idempotently so a retried callback never double-credits.
Expiry becomes action
Expiry doesn't sit in a report. It suspends the session, notifies the subscriber, and reverses itself the moment payment lands — reconnection in seconds, not shift handovers.
Reminders that collect
SMS renewal reminders before expiry, receipts on payment, and outage notices — sent to exactly the audience each event concerns.
Migration-grade import
Bring thousands of subscribers from spreadsheets or another platform in one streamed, batched import with per-row validation — built for cutover day.
Under the hood
For the reader who wants the details
The payment loop
M-Pesa Daraja (STK Push + C2B) · wallet · invoices- Payments match by account reference first, then fall back to phone number — so a subscriber paying for a relative's account still reconciles.
- Every payment applies exactly once, even if Safaricom retries the callback — idempotency is enforced at the application layer, not by hoping.
- Partial payments follow your policy: hold in wallet or extend proportionally — your rule, applied consistently.
The enforcement loop
FreeRADIUS · MikroTik and standards-based BRAS- Suspend and restore are tied directly to billing state — no NOC ticket to disconnect a non-payer, no 2 a.m. call to reconnect one who paid.
- Speed profiles apply the moment a plan changes, without re-provisioning the CPE.
- Live session view per subscriber: IP, uptime, throughput — the support answer is on the screen before the subscriber finishes the sentence.
How it's priced
Which plan includes it
The billing engine is in both plans. Basic is the billing core on its own — PPPoE and static billing, M-Pesa and payments, RADIUS, SMS reminders and the subscriber portal — at KES 30 per user a month, KES 26 above 1,000 users. Premium adds every other module. A user is a subscriber that was active at any point in the month.
Runs well with
Modules that pull together
Create your account
Launch your ISP on CoreSync today
Tell us who you are and we will set up your workspace, walk you through onboarding and help you import your existing subscribers.
- 1Create your workspace — your own subdomain, branding and paybill.
- 2Connect your network — routers, RADIUS and OLTs, with our engineers on the call.
- 3Import subscribers and go live — from your current system or a spreadsheet.