Skip to main content
ICP System is a web-based network operations dashboard built for Internet Service Providers. It gives your NOC and operations team a single pane of glass to track bandwidth capacity, manage infrastructure, oversee corporate clients, and monitor live traffic via Zabbix integration.

Quick Start

Set up ICP System and log in for the first time in minutes.

Authentication

Learn how JWT tokens work and how sessions are managed.

Capacity Dashboard

Monitor contracted vs assigned vs available bandwidth per connection.

Zabbix Monitoring

View real-time IN/OUT traffic metrics collected by Zabbix.

What ICP System does

ICP System centralises every layer of your ISP’s network into one dashboard — from upstream provider contracts down to individual client connections.

Providers & Services

Track upstream providers, purchased bandwidth, and service contracts.

Nodes

Manage physical and logical network nodes with geolocation data.

Connections

Create and manage client links with full bandwidth lifecycle tracking.

Corporate Clients

Manage corporate accounts and their branch offices (sedes).

Equipment

Inventory network devices with SNMP and management credentials.

Administration

User accounts, role-based access, Excel import, and contracts.

Get up and running

1

Deploy the frontend

Build and serve the React application. Point VITE_API_BASE_URL at your backend API host.
2

Log in

Navigate to /login, enter your credentials, and receive a JWT access token. The token is stored in localStorage and attached automatically to every request.
3

Explore capacity

The home screen opens the Capacity & Risks dashboard. You’ll see KPI cards for total contracted, assigned, and available bandwidth across all connections, along with risk distribution charts.
4

Configure your network

Add your upstream Providers, create Services (bandwidth contracts), register Nodes, and wire up Connections to corporate clients.
ICP System requires a compatible REST API backend. See Backend API for the full list of endpoints the frontend consumes.