Billing & subscribers

Billing EngineBasic & Premium

PPPoE and static IP billing, M-Pesa and RADIUS in one self-enforcing loop

Hotspot & Vouchers3% of collections

Voucher and M-Pesa hotspot access — users are free, we take 3% when you collect

Leads pipeline, customer 360 and campaigns, next to the billing truth

MessagingBasic & Premium

Renewal reminders, receipts and outage notices — to exactly who they concern

Network operations

OLT/ONU ManagementPremium

Huawei, ZTE and VSOL OLTs and every ONU behind them, one console

ACS / TR-069Premium

Fleet-wide CPE control: WiFi, diagnostics and config over TR-069

Device ManagementPremium

Routers, switches and APs monitored — know before the subscriber calls

Fiber MappingPremium

The plant on a map — OLTs, splitters, ONUs — however big it grows

Back office & AI

InventoryPremium

Ledger-driven stock for ONTs, routers and drums — plus full procurement on Plus

AI AssistantPremium

Ask the platform questions in plain language, answered from live data

All ten modulesOne platform, two plans, priced per user

10 modules — Basic covers the billing core, Premium includes every one of them.

Explore products →

Smaller footprint

Estate & hotspot ISPBasic

Many subscribers, few ONUs, hotspot in the common areas

Home fiber / neighborhood WISPPremium

PPPoE to every home, one ONU per household

Larger footprint

Regional fiber operatorPremium

Many OLTs and ONUs, mixed vendors, one NOC

Multi-brand ISP groupPremium

Shared infrastructure, several brands

Different ISP, different billSee the plan and an example month for each archetype

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 setup

STK Push and C2B on your own paybill

Billing, explained

Two plans, volume bands, the math

Onboarding an OLT vendor

Huawei, ZTE and VSOL side by side

Playbooks

Static IP to PPPoE

Converting a live network safely

The migration playbook

Off spreadsheets, onto CoreSync

Reducing disconnection complaints

Proactive renewal reminders

Case studies

Automating renewals at scale

An estate ISP, illustrative walkthrough

A multi-site fiber NOC

Topology and optical alerts in practice

FeaturedWhy ISPs switch to CoreSync

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 →

Developers / Versioning

Versioning

v1 only gains things. A breaking change would come as /api/v2, alongside v1, with v1's retirement date announced.

Updated 4 November 2026API v1.0.1

Developer docs

On this page

What v1 promises#

Within v1, nothing you use is taken away or renamed: operations, fields, event names and error codes stay as they are. What can be added:

New operations.
New optional fields in requests.
New fields in answers and event payloads.
New error codes, and new webhook events you can choose to subscribe to.

Build your client to ignore fields it doesn't know, and to cope with a value it doesn't recognise. Treat an unknown error code by its HTTP status.

Version numbers#

The URL stays /api/v1. The spec's info.version (now 1.0.1) goes up on every change: the last number for fixes, the middle one for additions.

Check the current version (no key needed)

curl -s https://coresyncapi.avitechcloud.com/api/v1/openapi.json | jq -r .info.version

Breaking changes#

If something ever has to change in a way that would break you, it will be published as /api/v2. v1 keeps running beside it, and the date v1 retires is announced on the changelog well before it happens.

Stay informed#

Every change is on the changelog. Questions about a change? Write to hello@coresyncisp.com.

NextChangelog →

Stuck, or missing something? Tell us what you're building.

hello@coresyncisp.com