One platform to run your ISP
Subscribers, billing, MikroTik automation, installer dispatch, network monitoring, and audit trails — unified for Philippine ISP operators.
Why ISPs need NetCore
Philippine ISPs juggle disconnected systems that cause errors, leak revenue, and leave disputes without proof. Sound familiar?
Fragmented Tools
Spreadsheets for plans, separate ticketing for installers, manual MikroTik changes — nothing talks to each other. Every handoff is a chance for error.
Revenue Leakage
Activation mistakes, billing mismatches, and wallets that don't reconcile. When money moves without a ledger line, you can't explain the discrepancy.
No Audit Trail
When a subscriber disputes a charge or an installer changes a record, there's no trace. Without "who changed what and when," disputes are unresolvable.
Three roles, one platform
Configure
Set up tenants, plans, hierarchy, RBAC roles, MikroTik routers, and collections policies.
Monitor
Receive transaction notifications, view live maps, track installer jobs and network health.
Report
Generate, schedule, and export operational and financial reports within your scope.
Investigate
Drill into audit trails, trace disputes, and verify wallet ledger integrity.
Every role in the ISP
ISP Owners & Admins
Full platform overview across all franchises
Configure plans, hierarchy, RBAC, and collections policies
Transaction notifications, reports, and map monitoring
Assign geographic scope to staff — or see everything
Operations Staff
Scoped view within assigned regions and barangays
Manage subscriber exceptions and billing events
Coordinate installer jobs from map and dispatch board
Generate reports without ad-hoc spreadsheets
Installers & Contractors
Receive job orders with customer and location info
Capture router, plan, and activation fee on-site
Auto-activate subscribers from the field
Contractor admins manage their own team and pool
Subscribers
Self-service router binding to get connected
View plan, wallet balance, and payment history
Clear service vs. router status — know what's wrong
One account for billing, connectivity, and support
Choose a plan for your ISP
Flexible tiers that scale with your subscriber base and operational needs.
Starter
For small ISPs starting out
Custom
Contact us for pricingUp to 500 subscribers
Core billing & wallet
1 MikroTik router
Basic reports & CSV export
Email support
Professional
For growing operations
Custom
Contact us for pricingUnlimited subscribers
All billing, collections & promos
Multiple MikroTik routers
Contractor organizations
Network monitoring & maps
Scheduled reports
Priority support
Enterprise
For multi-franchise ISPs
Custom
Contact us for pricingEverything in Professional
Multi-tenant / multi-vendor
Geographic scope per admin
API access & webhooks
Custom SLA & onboarding
Dedicated support
Frequently asked questions
Nothing changes for them. NetCore ISP uses plan versioning — each subscriber is locked to the plan version they signed up for. When you update pricing, a new version is created for future signups. Existing terms remain stable until you explicitly migrate.
NetCore communicates with your MikroTik routers via the REST API (RouterOS 7+). You register each headend router (IP, port, credentials) in the per-vendor router registry. Activation, suspend, and restore commands are event-driven — triggered by job completion, payment settlement, or collections policies. No manual Winbox needed for routine operations.
Yes — that's the primary workflow. The installer receives a job order, enters the subscriber's Customer ID to bind the correct account, captures router/CPE details and plan selection, then submits. The system auto-activates on MikroTik and records everything with a full audit trail.
Every GraphQL query and mutation enforces tenant context via requireIspAccess(). Data is scoped by vendor (ISP) ID at the database level. Apollo cache is cleared on workspace switch. Super Admins with cross-vendor access undergo the same isolation checks — they just pass for all tenants.
Both prepaid and postpaid. Prepaid plans use validity days (7, 15, 30, or custom). Postpaid uses monthly recurring charges. Wallets track every peso with immutable ledger entries. Collections policies handle auto-disconnect for overdue accounts and auto-reconnect when payment clears.
Yes. 65+ GraphQL mutations and 12 RBAC server actions emit structured audit events with before/after payloads. Every money movement, plan change, role assignment, job update, and MikroTik command is logged with actor, timestamp, and context. Designed for dispute resolution and future restore-from-audit.
Absolutely. Super Admin can assign geographic scope per staff user — specific regions, provinces, municipalities, or barangays. Or grant "all areas" access for a single admin to oversee every franchise under the vendor without juggling multiple logins.
Yes. Installer organizations (contractor companies) have their own Contractor Admin role. They manage their own technicians, view org-scoped jobs, pull from job pools, and run team-level reports — without accessing other contractors' data or full vendor financials.