myisp

MYISP — ISP BILLING & SUBSCRIBER MANAGEMENT PLATFORM Build a complete, production-ready ISP Billing, Subscriber Management, Network Management and Field Service platform named MyISP. The platform should provide functionality comparable to professional ISP management systems such as ISPmate, but must use its own original architecture, database, UI and implementation. Do not copy proprietary source code, branding, or copyrighted designs. 1. PLATFORM OBJECTIVE MyISP is a multi-tenant SaaS platform for Fiber ISPs, Broadband ISPs, WISPs and FTTH operators. It must manage the complete ISP lifecycle: customer registration, KYC, plans, service activation, billing, payments, network authentication, MikroTik, FreeRADIUS, OLT/ONU, IPAM, support tickets, technicians, attendance, inventory, notifications and reports. Build a real working application, not a static prototype or UI mockup. 2. APPLICATIONS Create: Admin Web Panel: Dashboard, subscribers, KYC, plans, services, billing, invoices, payments, collections, network, MikroTik, RADIUS, OLT/ONU, IPAM, tickets, technicians, attendance, inventory, reports and settings. Customer Portal/App: Login, dashboard, current plan, expiry, invoices, payments, receipts, usage, complaints, tickets, notifications and profile. Technician App: Assigned jobs, customer information, navigation, job status, installation/service work, photos, notes, equipment usage, payment collection and customer signature. Super Admin: Manage ISP tenants, platform settings, subscriptions, administrators, global monitoring and audit logs. 3. TECHNOLOGY Use: - React + TypeScript - Tailwind CSS - Node.js + NestJS - PostgreSQL - Redis + BullMQ - REST APIs - WebSockets where useful - Docker/Docker Compose - JWT authentication - Secure password hashing - S3-compatible storage for documents Use a modular architecture so future microservice migration is possible. 4. MULTI-TENANCY & SECURITY Every ISP must be isolated using "tenant_id". Implement secure tenant context and never trust tenant IDs supplied by the frontend. Create roles: SUPER_ADMIN, TENANT_ADMIN, MANAGER, ACCOUNTANT, SUPPORT, TECHNICIAN, COLLECTOR, VIEWER and CUSTOMER. Implement granular permissions such as: "subscriber:create", "subscriber:read", "billing:create", "payment:verify", "ticket:assign", "network:manage". Implement JWT access/refresh tokens, refresh-token rotation, revocation, rate limiting, validation, secure headers, audit logging and encrypted storage for network credentials. Never expose passwords, RADIUS secrets, API keys or database credentials to frontend code. 5. SUBSCRIBER & KYC Create Individual and Business subscribers. Statuses: Lead, Prospect, Active, Suspended, Terminated and Closed. Generate customer numbers such as: "CUST-2026-000001" Store customer details, contact information, addresses, branch, sales person, technician, registration date and service information. KYC must support National ID, Passport, Driving License, Company Registration, signed CAF, address proof and photograph. Include document upload, secure storage, masking, hashing, approval/rejection workflow, rejection reason and audit history. 6. INTERNET PLAN ENGINE Create a professional bandwidth and package engine. Support: Residential, Business, Corporate, Dedicated, Prepaid and Postpaid plans. Plan parameters: Download speed, upload speed, CIR, MIR, MikroTik burst-limit, burst-threshold, burst-time, FUP threshold, FUP speed, validity, monthly price, installation fee, activation fee, deposit, discounts and taxes. Store bandwidth internally as integer Kbps. Support plan upgrade, downgrade, migration, renewal and versioning. 7. BILLING & PAYMENTS Build a real billing engine supporting monthly, prepaid, postpaid, prorated billing, renewals, discounts, taxes, installation charges, activation charges, deposits, late fees, credits, debits, adjustments and refunds. Generate: "INV-2026-000001" for invoices and: "RCT-2026-000001" for receipts. Payment methods: Cash, bank transfer, UPI, card, wallet, payment gateway and manual payment. Maintain a proper customer ledger with verified debit/credit entries. Use background jobs for invoice generation, reminders, expiry, suspension, reactivation, renewals, FUP reset and reconciliation. 8. NETWORK MANAGEMENT Integrate MikroTik RouterOS API and FreeRADIUS. MikroTik features: - Router management - CPU/memory/uptime - PPPoE users - Profiles - Active sessions - Disconnect users - CoA - Queues - Bandwidth profiles - Traffic statistics FreeRADIUS features: - Authentication - Authorization - Accounting - radcheck - radreply - radacct - Session history - Online/offline users - CoA/Disconnect Create NAS management for RADIUS devices. Create OLT/ONU architecture supporting GPON, EPON, XG-PON and XGS-PON. Store OLT, PON, ONU serial, MAC, VLAN, RX/TX power and status. Use an adapter architecture so additional OLT vendors can be added later. 9. IPAM & VLAN Create IP Address Management supporting IPv4, IPv6, public/private IPs, pools, subnets, allocation, reservation and release. Create VLAN management with VLAN ID, name, service type, OLT, router, NAS and status. Prevent duplicate allocations. 10. SERVICE ACTIVATION When a customer purchases a plan: Customer → Service → Username → Password → IP → NAS → VLAN → RADIUS → MikroTik → Activation → Billing → Notification. When an account becomes overdue, automatically notify the customer and suspend the service according to configured grace-period rules. Disconnect active sessions when required. When payment is verified, automatically reactivate the service and restore network access. 11. SUPPORT & FIELD SERVICE Create a ticketing system with ticket numbers such as: "TKT-2026-000001" Support priorities: Low, Medium, High, Critical. Statuses: Open, Assigned, In Progress, On Hold, Resolved, Closed. Create field jobs for installation, fiber repair, ONU/router replacement, no internet, slow speed, relocation, upgrade and maintenance. Technician workflow: Assigned → Accepted → En Route → On Site → Work Started → Completed → Verified → Closed. Allow photos, notes, GPS, parts used, payment collection and customer signature. 12. INVENTORY & ATTENDANCE Inventory must track ONU, routers, switches, fiber, connectors, SFPs, adapters, tools and other equipment. Track purchase, stock, warehouse, branch, technician stock, issue, return, damaged/lost items and serial/MAC numbers. Attendance must support check-in, check-out, GPS, field duty, leave, late arrival and overtime. 13. DASHBOARD & REPORTS Create a professional dashboard showing: Total customers, active/suspended customers, new customers, today's collection, monthly revenue, outstanding amount, tickets, technicians, online PPPoE users, routers, OLTs and network alerts. Reports: Subscribers, billing, invoices, payments, collections, outstanding, revenue, expenses, plans, renewals, suspensions, PPPoE sessions, bandwidth, tickets, technicians, attendance, inventory and network. Support filters and CSV/Excel/PDF exports. 14. DATABASE Use PostgreSQL with UUID primary keys and proper relationships. Core tables: tenants, branches, users, roles, permissions, customers, addresses, kyc_documents, internet_plans, plan_versions, services, invoices, invoice_items, payments, customer_ledger, routers, radius_accounts, radius_sessions, nas_devices, olts, onus, vlans, ip_pools, ip_addresses, tickets, ticket_comments, field_jobs, technicians, attendance, inventory, notifications and audit_logs. Add indexes, foreign keys, constraints and timestamps. 15. DEVELOPMENT RULE Build in phases. Start with: Phase 1 — Foundation, database, authentication, multi-tenancy, RBAC and basic dashboard. Do not create fake functionality. Inspect existing code before modifying it. Never delete working features. Connect every UI feature to real APIs and database records. For every phase: build database → backend APIs → permissions → frontend → validation → audit logging → tests → build verification. A phase is complete only when the application builds successfully, APIs work, tenant isolation is verified, security checks pass and there are no major errors. Finally, deploy MyISP as a scalable, secure and professional ISP management platform suitable for real ISP operations.