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 →Company
Built where the networks are, Nairobi
We build the operating system for internet service providers — because we run networks too, and spreadsheets were never going to scale.
Why we built this
We were running the spreadsheet too
Before CoreSync was software, it was our own operational problem. A subscriber list in a spreadsheet. Payment confirmations screenshotted out of M-Pesa messages and matched to names by hand. One engineer who knew the OLT CLI well enough to fix a splitter fault, and everyone else waiting on him when he was offline.
None of that scales past a few hundred subscribers, and none of it survives someone leaving. We kept buying billing tools built for other markets — prepaid mobile, or enterprise telco — that assumed away the parts that actually define running an ISP here: M-Pesa as the primary rail, GPON plant that mixes vendors, and support teams who need to see the network, not just the invoice.
So CoreSync is the tool we wished existed while we were the ones on call. It is built by people who have carried the pager, not just people who sold to whoever does.
How we operate
Principles that show up in the product, not just the pitch
Built by operators
Every screen was argued about by someone who had to use it during an outage first. If a feature does not survive contact with a real fault ticket, it does not ship.
No vendor lock-in
Huawei, ZTE, VSOL — your OLT plant should not decide your billing vendor, and your billing vendor should not decide who you can buy an OLT from next.
Uptime over vanity features
A dashboard chart is nice. A subscriber getting reconnected automatically the second their payment lands is the actual job. We build the second thing first.
Works where M-Pesa works
STK Push and C2B are not an add-on integration for us, they are the default rail — because that is how your subscribers actually pay, not how a Western billing tool assumes they pay.
An ISP that gets sharper with every payment
Every M-Pesa confirmation, every session, every optical reading feeds the same system — so billing, the network and your books never disagree with each other.
110,000+ payments last month, every one reconciled.
Where we work
Nairobi, Kenya
We work from the same city as a lot of the networks running on CoreSync — close enough to sit with an operator's support desk during a bad outage, not just read about it in a ticket.
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.