Clean rebuild ยท 2026-06-07

ISP Deck

Multi-tenant ISP CRM, billing, service state, and access control.

Thesis

Business state drives the network

ISP Deck owns customers, services, billing, access identity, service state, and audit. Routers, RADIUS, UniFi, UISP, traffic, payment, and accounting systems are adapters.

OwnCRM, billing, service state, PPPoE/RADIUS records, IPAM, audit
AdaptMikroTik, FreeRADIUS, UniFi, UISP, QuickBooks, payments, traffic
ProtectPreview first, guarded apply later, no destructive suspension
Market read

What the research showed

UniFi

Excellent network/site control plane. Not an ISP CRM/BSS.

UISP

Closer to ISP operations with CRM, services, billing, jobs, tickets, shaping, and suspension.

BSS market

Splynx, Sonar, Powercode, VISP, Azotel, and gaiia confirm the center: customers, billing, access, automation, reporting.

Architecture

Source-of-truth chain

  1. Platform
  2. Tenant
  3. Users / Roles
  4. Customers
  5. Billing
  6. Services
  7. Service State
  8. Access Control
  9. Delivery Adapters
  10. Audit
Built now

Current clean rebuild artifacts

DomainTenant-scoped customers, plans, service state, delivery intents
PersistenceFoundation PostgreSQL schema and migration registry
APIRoute contracts, HTTP handler, local dev server
DemoDashboard, Customers, Billing, Access, Audit
Safety

Default gates are closed

Roadmap

Next six phases

1Demo foundationDone
2Real API + local Postgres seedNext
3API-backed operator UI V1Next
4Billing + access workflowsQueued
5Sandbox delivery adaptersQueued
6Guarded lab applyLater
Decision

Recommended next step

Connect the demo UI to a real local/dev API and Postgres seed, while keeping all external writes locked. This turns the demo into a real product slice without risking routers, RADIUS, payments, or customer data.