iPilot · AI operations engineer

Investigate, operate and verify your network with one engineering copilot

iPilot works inside ISPbills with the context an engineer needs: subscribers, RADIUS sessions, MikroTik routers, OLTs, ONUs, NetFlow and billing operations.

Realtime reasoning Visible tool activity Approval-gated changes
iPilotNOC workspace · MikroTik + OLT fleet
Engineer

Find why subscribers behind the north OLT are dropping and show the safest fix.

Realtime reasoning

Correlating RADIUS disconnects with ONU signal and OLT uplink state…

Resolved affected OLT and subscriber scope
Checked ONU signal distribution
Comparing disconnect times with uplink errors
Finding Optical degradation is concentrated on PON 2/4.

11 ONUs crossed the weak-signal threshold before the disconnect spike. Inspect the splitter path first; no configuration write is recommended yet.

Ask a follow-up or approve the next diagnostic step… Enter
Built for the engineering loop

From vague incident to verified action

Every response keeps evidence, execution and risk visible instead of hiding the work behind a generic chatbot answer.

01

Understand

Resolve the customer, device, interface or service affected by the prompt.

02

Inspect

Call live read tools across billing, RADIUS, routers, OLTs and NetFlow.

03

Act safely

Show exact commands, risk labels and approvals before a change runs.

04

Verify

Recheck the live state and explain whether the incident is actually resolved.

The real product

An AI workspace, not a chat bubble

Engineers can follow reasoning, tool execution, command risk and the final operational result in one continuous timeline.

iPilot terminal showing a live DDoS investigation with operational findings and next actions
A live DDoS investigation with network baselines, operational findings and coordinated next actions.

Fleet-aware investigations

One prompt can coordinate checks across routers, OLTs, ONUs and subscriber sessions.

Incident-mode workflows

DDoS, link failure and customer outage prompts trigger structured diagnostics instead of generic advice.

Change control built in

Safe, caution and destructive actions remain distinct, reviewable and attributable.

For the people on call

Useful at every engineering layer

NOC engineer

Turn alarms into a scoped investigation

Ask what changed, which customers are affected and which device should be checked first.

Summarize active incidents and rank them by subscriber impact.
Network engineer

Inspect live state before touching config

Compare routes, interfaces, firewall state, optical levels and traffic evidence across vendors.

Audit the edge routers for asymmetric routing and show evidence.
Field & support engineer

Trace a subscriber fault end to end

Correlate account status, RADIUS sessions, ONU signal and upstream device health.

Why is this subscriber offline, and where does the failure begin?
Terminal-first when you need it

The same operating model in iCLI

Use iPilot from the browser terminal or the command line with streamed reasoning, persistent tool activity and the same evidence-based final answer.

ispbills · iPilot CLI
iPilot CLI with streamed engineering activity
Human-controlled automation

Reason first. Approve second. Verify last.

Read-only diagnostics can run immediately Configuration changes show commands and impact Destructive operations require explicit approval

Start running your ISP on a platform your team will actually use

Start a free trial today — no credit card, no commitment.