The operating system for ISPs who build their own future

One system runs the ISP.

Billing, network operations, fibre plant, field crews, sales and support on one database, built and run by people who operate ISPs. Self-host it on your hardware, or run it as SaaS: your data stays yours either way.

Book a demo Compare to Splynx, Sonar, UISP
One data spineOne record per person or company travels one spine; billing, network, fibre plant, tasks and field, sales and CRM, customer portal, HR and Aelita dock onto it instead of keeping their own copy of it. CUSTOMER RECORD ONE DATABASE BILLING NETWORK FIBRE PLANT TASKS & FIELD SALES & CRM CUSTOMER PORTAL HR AELITA One data spineOne record per person or company travels one spine; billing, network, fibre plant, tasks and field, sales and CRM, customer portal, HR and Aelita dock onto it instead of keeping their own copy of it. CUSTOMER RECORD ONE DATABASE BILLING NETWORK FIBRE PLANT TASKS & FIELD SALES & CRM CUSTOMER PORTAL HR AELITA
Multi-tenant Multi-currency Self-host or SaaS AI-native In production since 2014
How a day runs

Four things that happen every week at an ISP, on one record.

Every step below exists in the product today, and each box links to the module it belongs to. There is no sync layer between any two of them: the signup, the fibre cut, the deal and the invoice all write to the same customer record.

01

Signup to first invoice

An address is checked against the fibre map before anyone promises anything. The contract carries the products and terms; provisioning on the OLT and the NAS reads them; the first invoice follows the calendar the contract set. The payment lands on whichever rail the customer uses and is reconciled without a person retyping it.

Signup to first invoiceCoverage check on the fibre map, contract, ONU authorised on the OLT, NAS session, first invoice, payment on a supported rail, reconciliation, ledger and overdue balances. COVERAGE CHECK fibre map first CONTRACT products · terms · e-signature ONU AUTHORISED on the OLT, per-vendor driver NAS SESSION provisioned from the contract FIRST INVOICE calendar or periodic billing PAYMENT card · debit order · mobile money RECONCILED bank statement import LEDGER MRR, ARR, overdue balances
  1. Coverage Check fibre map first
  2. Contract products · terms · e-signature
  3. ONU Authorised on the OLT, per-vendor driver
  4. NAS Session provisioned from the contract
  5. First Invoice calendar or periodic billing
  6. Payment card · debit order · mobile money
  7. Reconciled bank statement import
  8. Ledger MRR, ARR, overdue balances
02

Fibre cut to restored

A PON port goes dark on the OLT and the board shows one outage: every customer behind it on one row, one repair job for the whole port, not a stack of hand-made tickets. Dispatch sees the cluster and the crew; the field app walks the technician through the repair; a customer who phones in hears that the team already knows; and when the signal is back, the restored alert stamps the downtime on every incident note and closes it once the line reads as good as before. The repair job closes with its protocol on file.

Fibre cut to restoredA PON port goes dark on the OLT and becomes one outage, every affected customer on one row and one repair job for the port; dispatch and the field app on one branch, the outage-aware phone line and the restored alert on the other; the repair job closes with its protocol on file. OLT ALARM link down · signal lost ONE OUTAGE every customer behind the port, one row DISPATCH crew, schedule, board FIELD APP GPS · photos · signature CALLERS HEAR IT the IVR knows the outage RESTORED closed on a good reading JOB CLOSES protocol on file
  1. OLT Alarm link down · signal lost
  2. One Outage every customer behind the port, one row
  3. Dispatch crew, schedule, board
  4. Field App GPS · photos · signature
  5. Callers Hear It the IVR knows the outage
  6. Restored closed on a good reading
  7. Job Closes protocol on file
03

Deal to contract

A pipeline for the deals an operator makes: routes with legs, three kinds of money, a next step that is a real task, with a due date if you give it one. The stages are rows you edit, not code you wait for. When the deal is won you point it at the contract that bills it, on the same account, and the funnel report shows where deals actually wait. The CRM, in full →

Deal to contractA deal moves through stages the operator defines, with a next step that is a task, a days-in-stage counter and a funnel report along the way, and can be pointed at the contract it became. stages are yours to define LEAD QUOTE SIGNED BUILD LIVE BILLING CONTRACT LINKED the contract it became NEXT STEP a task; overdue ones escalate DAYS IN STAGE amber, then red FUNNEL REPORT medians, with n=
  1. Stages You Define lead, quote, signed, build, live, billing, or your own
  2. Contract Linked the contract it became
  3. Next Step a task; overdue ones escalate
  4. Days In Stage amber, then red
  5. Funnel Report medians, with n=
04

Invoice to cash

The bill run, the invoice, the payment, the bank line, the ledger and the customer’s service state are one loop on one account. A service suspended for an overdue balance is restored from the same contract that suspended it, and a customer who has paid up can resume it themselves from the portal.

Invoice to cashBill run, invoice out, payment in on any rail, bank statement auto-matched, ledger and aging, service state, and round again next period. BILL RUN calendar or periodic INVOICE OUT email · portal · PDF PAYMENT IN debit order · card · mobile money AUTO-MATCHED bank statement import LEDGER MRR · ARR · auto-suspend SERVICE STATE suspend · restore · self-resume
  1. Bill Run calendar or periodic
  2. Invoice Out email · portal · PDF
  3. Payment In debit order · card · mobile money
  4. Auto-Matched bank statement import
  5. Ledger MRR · ARR · auto-suspend
  6. Service State suspend · restore · self-resume
The Problem

ISPs are fed off-the-shelf ERPs that don't know what an OLT is.

The category has been served by adapted-from-elsewhere software for two decades. A generic CRM bolted to a billing engine bolted to a ticket system, glued by sync layers, sold by sales teams who learned about ONUs in their pre-call brief.

The integrators promise unified and deliver duct tape. The dashboards promise insight and deliver the same nine widgets every other vertical gets. The roadmap promises industry focus and ships features for retail.

ISPCQ was built by people who run an ISP, for people who run an ISP. Every module maps to operational reality: cabling crews, OLT firmware, NAS sessions, splitter trees, customer-IP reverse lookups, prepaid periods, bank-statement reconciliation, multiple currencies, multiple tax regimes.

The surfaces look the way they do because the engineers are also the operators, and the roadmap is the production backlog. There is no committee writing requirements that haven’t been pulled at 2am during a fibre cut.

Where it runs

In production since 2014. Live today in Bulgaria and South Africa, with a pan-African operator group taking it into Kenya and more markets.

Currencies
Multi-currency, proven in production across different currency regimes on one codebase
Regulators
Different tax regimes and address formats, all configuration, no forks
Tenancy
One codebase, one database per operator. No per-tenant forks; the differences live in configuration.
Deployment
Self-host, or run as SaaS while you build the team. Same architecture.
Cadence
One codebase, one release train, every tenant. The changelog is public.
Sovereignty  /  The philosophy

Your data. Your jurisdiction. Your deployment model.

Sovereignty is not about owning the source code. It is about your data being yours, exportable, never trapped, and your deployment being your call. Two ways to run ISPCQ, same architecture either side of the boundary.

01
Deploy anywhere.
Self-host on your hardware, in your region. Or run it as SaaS while you build the team to bring it in-house. Same data model, same migration path either side of the boundary.
02
Multi-tenant by design.
One codebase; multiple ISP brands across jurisdictions, currencies and regulators; no forking. Every operator runs the same codebase from the same repository; what differs between them is configuration and permissions, not a fork. Add a tenant brand, not another instance.
03
Your data, yours to query.
Customer records, billing history, OLT and line telemetry, call transcripts and support notes: one relational database you can dump and take with you if you change deployment model or host. Sovereignty is portability.
The deployment boundary Self-hosted on your hardware and run as SaaS are the same architecture, the same data model and the same migration path; the boundary between them is where the hardware sits; the data model is the same on both sides. the boundary SELF-HOSTEDyour hardware, your region RUN AS SAASwe host it, you keep the data SAME CODE same data model · same migration path

One platform, not nine tools glued together.

64 capabilities · all shipped · one database
Billing & revenue
Network operations
Fibre plant
Field & operations
Sales & CRM
Fleet & GPS
Customer-facing
Aelita AI
Platform
And it speaks to what you already run
FinanceStripeFinanceMoSAFinanceiKhokhaFinanceFNBFinanceePayFinanceMoMoNetworkIPACCT NASNetworkTR-069 ACSNetworksFlowNetworkCloudflareNetworkMulti-vendor OLTNetworkObserviumNetworkPBX + speech-to-textMessagingWhatsAppMessagingViberMessagingTelegramMessagingWeb PushPlatformNextcloudPlatformMicrosoft 365 SharePointPlatformosTicketPlatformOIDC SSOPlatformMaxMindPlatformISPmanager mailPlatformClaude APIPlatformAd attributionPlatformSA company lookup

Comparing ISPCQ to Splynx, Sonar, Powercode, UISP, or your current platform?  Read the comparison brief →  ·  All modules →

Aelita  /  Built-in, not bolted-on

The AI assistant already running inside the platform.

Her ticket copilot reads the same records operators do: contracts, payments, invoices, ONU signal and the OLT event log. Inside the ERP, a staff member’s question is answered from the knowledge base and the procedures, inside that person’s permissions.

Powered by Claude, with voyage-4-nano embeddings against a sqlite-vec store. Live in production since December 2025 inside a platform that has been shipping since 2014.

Read the architecture →
Model
Claude
Embeddings
voyage-4-nano
Vector store
sqlite-vec
Surface
In-app, every back-office screen
Live since
Dec 2025
Book a demo

See it on your own data.

Bring an export of your billing, network, or support data. We'll show you the same operational view your team would see on day 14, with your customers, your tariffs, your OLT topology.

Demos run roughly 45 minutes. Self-hosted or SaaS, your call. We don't pitch; we show.

Coming from another platform? The most recent operator to bring its pipeline onto the platform arrived with it in a different CRM. Its accounts, contacts, deals, stage history, activity notes and attachments came across in one import, and deals were being worked on the platform within days. There are things the platform does not do yet; the roadmap shows what is in flight.

Book a demo → Compare to Splynx, Sonar & others

Direct

Email
[email protected]
What is coming next
The roadmap, in the open
Why ISPCQ
The full thesis