Eleven core modules, five integration families, and an AI assistant. One codebase, one database, deployed together. This page is the catalog: what's shipped today, what each module does, where Aelita shows up.
Each module shares the same database and the same contract record. No sync layers, no import/export. One unified operational truth.
Dual billing engines, rule-based pricing, and automated bank reconciliation. Handle proration, prepaid/postpaid logic, and complex bundles without manual overrides.
NOC map with live device status, multi-vendor OLT management, and topology auto-discovery. Monitor, provision, and troubleshoot from one interface.
A geographic map of the entire fibre network: routes, conduit, manholes, cabinets, equipment, splitters, and customer connection points. Plan builds, trace every customer's path back to the exchange, and run cable-fault repairs from one place.
Warehouse and supply chain management. From purchase order to field deployment. Track every ONU, router, and cable spool by serial number.
Self-service dashboard where customers manage their accounts, make payments, and request support. Reduces call volume and after-hours helpdesk load.
Full contract lifecycle from lead capture to termination. Products, plans, bundles, addons, and digital signatures. All configuration-driven.
Unified Notes Hub with task board, service journal, and dashboard views. Status workflows with configurable transitions, KPI tracking, outage quick-log, and cascading filters. All connected to customer contracts and billing context.
Full workforce management. Employee lifecycle, attendance, leave, shifts, overtime, and payslip generation. Built for ISPs where field crews, NOC shifts, and office staff coexist.
Executive view of business health plus a dedicated Reports hub. KPIs, network status, cashflow, and operational queues in real time, backed by named financial, sales, coverage, and audit reports that print or export to CSV.
RESTful JSON API with 40+ endpoints across customer, contract, billing, and network operations. The same surface Aelita uses internally is what tenants and integrators get. Reference docs supplied directly to integrators.
The internal documentation system: SOPs, how-to guides, reference manuals, policies, and vendor docs in one place. Staff find the correct procedure for any task without asking a colleague or digging through email.
Each integration is built as a first-class operational workflow, not a raw data connector. Events produce outcomes, not just notifications.
Collect payments through multiple channels. Online card payments, bank transfers, point-of-sale terminals, and regional gateways.
Vendor-agnostic OLT management through a unified abstraction layer. Provision, monitor, and troubleshoot regardless of hardware mix.
Channel-agnostic notification dispatcher. Invoices, payment confirmations, reminders, and contract updates via the customer's preferred channel.
Native Asterisk/FreePBX integration that links phone calls to customer accounts. Caller ID resolution, agent extension mapping, and full call lifecycle logging. All inside the ERP timeline.
Storage, geolocation, and support tools. Connected where they matter in daily workflows.
Aelita is embedded LLM intelligence powered by Claude. She operates within the same permission boundaries as the logged-in user. She can draft, suggest, and analyze, but she cannot act without human approval.
Nineteen capabilities shipped today, organized into five clusters: customer-facing, field & NOC, finance & inventory, internal staff, and capability fundamentals. Every output is a draft. Every action requires a human in the loop.
Security and access control wrap the whole system. ACL v2 with dot-notation permissions and role inheritance. Immutable audit trail with before/after values. Mandatory 2FA for admin roles. IP-restricted access for sensitive operations. Note-area visibility for role-based view scoping. AI safety boundaries scoped to user permissions.
Three properties that survive every redesign of the rest of the system. They are the through-line of why ISPCQ exists.