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 →Solutions — Multi-brand ISP group
Many brands, one plant, clean books
You run more than one ISP brand off shared infrastructure. CoreSync gives each brand its own tenant — own subdomain, own subscribers, own invoice — while the group shares OLTs and back office. Infrastructure sharing without data sharing.
Sound like you? You've grown into a group: different brands for different markets, sometimes different towns, all riding shared backhaul and sometimes the same OLT. The commercial problem is separation — each brand needs its own books, its own rates and its own customer experience — without duplicating the plant or the people who run it.
The week, before and after
What actually changes
Running it by hand
- One billing system pretending to be several — or several systems pretending to agree
- Two brands' ONUs on the same OLT means one brand can see the other's plant
- Every brand's billing is its own island — different tools, different reports, different month-ends
- Every acquisition or new brand is a months-long systems project
On CoreSync
- Each brand is a full tenant: own subdomain, own branding, own team, own invoice
- Shared OLTs with per-brand visibility — each tenant sees and bills only its own ONUs
- Every brand bills on the same published plans, in the same system, on the same month-end
- A new brand is a new tenant on day one — the plant is already under management
Your module stack
Four modules that carry this shape
The modules this kind of operator leans on, each tagged with the plan that includes it. Basic covers the billing core; Premium includes every module.
The money, worked
An example month on Premium
Illustrative month, published prices
KES 123,000 / moShown for one brand-tenant on Premium. Each brand is its own tenant with its own invoice, and the shared OLTs and backhaul are part of Premium, so the plant adds nothing to the bill.
Getting there
The rollout, step by step
First tenant migrated
The largest brand moves first: subscribers imported, OLTs under management, enforcement live — the pattern the rest will follow.
Brands separated cleanly
Each remaining brand gets its tenant; shared chassis are split by ONU ownership so every book reads only its own plant.
One back office for the group
Shared plant, NOC and support run once for every brand, while each brand's subscribers, books and invoice stay its own.
Not quite you?
The other archetypes
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.