Kiapoynt
Service

ISP & network operations

SmartOLTSplynxMikroTikFreeRADIUSBullMQDocker
The problem

Optical monitoring, billing and payments usually live in three separate platforms that were never built to talk to each other. A connection can be down for hours before anyone technical knows, because the only signal is a customer complaint.

Our approach

We build the layer that sits over the platforms you already run — polling the hardware on a schedule, raising an alert the moment something changes, and opening a ticket in your existing billing system without anyone doing it by hand.

What this covers
01

Optical monitoring & alerting

Scheduled polling against SmartOLT with per-tenant toggles, so a maintenance window on one network doesn't touch monitoring on another.

02

Automatic ticketing

An alert opens a Splynx ticket directly, with deduplication so a single flapping connection doesn't flood the queue.

03

Time-based escalation

A ticket left open past a configured threshold reassigns itself to a wider support group and raises its own priority — four tiers, no manual review required.

04

Multi-tenant isolation

Separate credentials and a circuit breaker per operator, so one tenant's outage can't stall polling or ticketing for another.

Need this for your business?

Tell us what you run today and where the gap is.