Why local-first architecture matters when the internet you sell is also the internet you depend on. Operations don't pause when the upstream does.
The old way. The ISP's upstream provider has a planned maintenance window at 03:00. The SaaS-hosted billing system briefly becomes unreachable from the operations network. Cashbox cannot record overnight payments. Provisioning queues stack up. A planned 30-minute maintenance becomes a four-hour operational outage by the time the queues drain.
What ISPCQ does. Self-hosted ISPCQ runs on the ISP's own infrastructure inside the operations LAN. The database, the billing engine, the ticket queue, the network provisioner all live on the same network as the people using them. When the upstream link drops, internal operations are unaffected. Module licensing validates through a key server with generous offline grace periods so connectivity interruptions never disrupt live operations.
The operational outcome. Maintenance windows on the upstream link become invisible to operations. The same architecture also supports SaaS deployment for ISPs that want ISPCQ-managed hosting without the on-prem responsibility.
One of twenty-two detailed articles on real ISP workflows. Each walks through the problem, what teams used to do, what ISPCQ does, and the operational outcome. The architecture is the same; the workflows differ.