One database, one auth layer, one deploy. Billing, network operations, inventory, and support sit on the same data spine. Self-host on your hardware or run it as SaaS: your data, your jurisdiction, your choice.
The category has been served by adapted-from-elsewhere software for two decades. Generic CRMs bolted to billing engines bolted to ticket systems, glued by sync layers, sold by sales teams who learned about ONUs in their pre-call brief.
The integrators promise unified, then deliver duct tape. The dashboards promise insight, then deliver the same nine widgets every other vertical gets. The roadmap promises industry focus, then 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, BGP sessions, splitter trees, customer-IP reverse lookups, prepaid-credit reconciliation across multiple currencies and tax regimes.
This is what the surfaces look like when the engineers are also the operators.
ISPCQ wasn't designed in a strategy deck. It runs in production today across two geographies, two currency regimes, and two regulatory environments, on real subscribers, real money, real regulators, all from a single codebase, deployed together. Every architectural claim on this page is operational reality, not a roadmap promise.
Two ISPs running in production today. Live customers, live billing, live regulators. Not a sandbox.
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.
Stop stitching together spreadsheets and vendor EMS tools. Run your entire ISP from one operating layer.
Dual billing engines with rule-based pricing, automated bank reconciliation, mobile money collection, and cashbox management.
Vendor-agnostic OLT management and TR-069 automation. See signal levels inside the customer ticket.
Complete fiber network documentation. Cables, cores, splitters, ducts, manholes. OTDR integration and cable-fault impact analysis.
Configurable status workflows with For-Review sign-off, chain-of-command close, kanban board, dynamic dashboard views, KPI metrics, and automatic escalation.
Track every serial number from GRN to customer premise. Multi-warehouse and vehicle-stock tracking.
Attendance tracking with fingerprint import, leave management with auto-login blocking, shift scheduling, and payslips.
Built around AI from the ground up, not bolted on. The assistant reads the same database your team reads. Customer summaries, note categorization, document verification, after-hours triage.
Self-service portal with 2FA, invoice viewing, online payments, ONU reboot, Portal Badger self-repair, and reseller management.
PBX phone-system integration, email with bounce handling, payment gateways, and messaging plugins.
Deployment sovereignty, role-based access control, 34 automated cron jobs, multi-tenant architecture.
Comparing ISPCQ to Splynx, Sonar, Powercode, UISP, or your current platform? Read the comparison brief →
Aelita reads the same data spine that operators do: customer history, network telemetry, billing ledgers, support notes, OLT firmware logs. She is part of the operating layer, not a chatbot grafted on top.
Built on voyage-4-nano embeddings against a sqlite-vec store. Live in production since December 2025 (v3) inside a platform that has been shipping since 2014.
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.