Remote plan

Your NOC, run from ours.

Nobody sits in your office. Our NOC hub watches your network 24 hours a day, acknowledges every alert, escalates to your team and vendors, and sends you locked PDF reports you can hand straight to an auditor.

Open the sample dashboard See the reports

Remote · monthly fee

RM 9,772 / month

Excluding SST. Fixed for the first 12 months.

Coverage: 24x7x365
Included: 1 site · 50 devices
Extra devices: RM 600 / 25
Extra site: RM 800 each
Onboarding (one-off): RM 9,772
Minimum term: 12 months

Price my setup

What you get

Included in every month.

24x7 monitoring

Our hub engineers watch your devices, links and applications around the clock, including weekends and public holidays.

Alert handling

Every alert is acknowledged, ticketed and worked against an approved runbook. P1 is acknowledged within 15 minutes.

AI checks every reading

AI spots threshold breaches and unusual patterns, logs in read-only to investigate, and ranks likely causes. An engineer confirms every finding.

Escalation

We call your on-call contact, log faults with your ISP and vendors, and chase them until the issue is closed.

Read-only dashboard

Named staff get a view-only login to the live dashboard. Nobody on your side can change alerts or delete history.

Locked PDF reports

Monthly, incident and quarterly reports, sent as softcopy PDFs with editing disabled. Details below.

Quarterly review

Your service delivery manager visits once a quarter to walk through the numbers and agree actions.

Reports

What lands in your inbox, and when.

All reports are emailed to the recipients you name in the escalation matrix. Formal reports are PDF only. We don't send Word or Excel versions.

Report	When	Format	What's in it
Monthly Service Report	By working day 5	Locked PDF	SLA scorecard, availability per site and service, incidents by priority, resolver and ISP performance, capacity watch, coverage changes, escalation matrix check, recommendations.
Major Incident Report	Within 3 working days of a P1 closing	Locked PDF	Timeline from alert to recovery, impact, actions taken, who was called and when, cause where known, follow-up actions.
Quarterly Service Review pack	Quarterly, before the meeting	Locked PDF	Three-month trends, SLA history, recurring issues, capacity forecast, signed meeting minutes afterwards.
Monitoring Coverage Register	Monthly, as an appendix	Locked PDF	Every monitored device and check, with IP, owner, criticality and the protocol used.
Annual Availability Summary	Every 12 months	Locked PDF	Year's availability per service, P1/P2 count, SLA attainment. Written for management and auditors.
Daily health email	Every working day, 9:00 am	Email	Overnight alerts, open tickets, vendor tickets pending. For your IT team; not a formal record.
Incident updates	P1 every 30 min, P2 every 2 hrs	EmailPhone	Status, next action and next update time while an incident is open.

Why locked PDFs

Editing, page changes and form filling are disabled, so what your auditor reads is exactly what we issued. Printing and copying text stay allowed.

Traceable

Each report carries a document number, version, reporting period, issue date and the name of the engineer who prepared it.

Re-issued on request

We keep every issued report for the length of the contract, so you can get any month again for an audit.

AI-assisted operations

AI watches every reading, then logs in to check.

Every reading that reaches us is checked by AI against your thresholds and against what's normal for that device. When something crosses a line or starts behaving oddly, the AI logs in to the device with a read-only account, runs diagnostic checks, and hands the engineer its findings before most people would have opened the alert.

Watch everything
Every reading is compared with fixed thresholds and with the device's learned normal pattern, so slow drifts and odd spikes get caught, not just hard failures.
AI · continuous
Group the noise
Related alerts become one incident, so a single link failure shows up as one problem, not 14.
AI · seconds
Log in and check
The AI runs approved read-only checks on the affected devices: interface status, error counters, routing, failover state, recent logs.
AI · read-only
Rank likely causes
Probable causes, most likely first, each with the evidence from its checks and the runbook step to test it.
AI suggests
Confirm and act
The engineer reviews the findings, follows the runbook and escalates. Only people make changes, and only with your approval.
Engineer decides
Draft the RCA
AI drafts the timeline and root-cause analysis from the records. The NOC Lead edits and signs off before the report is issued.
Engineer signs off

Guardrails on AI logins

Read-only accounts

The AI uses a dedicated account with read-only rights on each device (for example privilege level 1, or a read-only API role). It cannot change configuration even if it tried.

Approved commands only

The AI chooses from a list of diagnostic commands you approve during onboarding, such as "show interface" or "show log". Anything not on the list is refused.

AI never holds passwords

Credentials live in an encrypted vault on your collector. The AI asks the collector to run a check; the collector logs in and returns the output.

Runs from inside your network

Logins start from the collector on your network, over SSH or the vendor's API. Nothing connects in from outside.

Every session recorded

Each login, command and output is logged with a timestamp and listed in the incident report and the monthly report.

You stay in control

AI checks are opt-in. You can pause them per device, block them during change freezes, or switch them off entirely.

What AI sees

Monitoring data and the output of its read-only checks: readings, alerts, device logs, config and routing state. Never your traffic content, files or emails.

Your data stays yours

Your data is not used to train AI models. It's processed under the data protection terms in your contract, in line with PDPA 2010. The AI providers we use are named in the contract's data schedule.

Clearly marked

Reports show which sections were AI-assisted and who reviewed them, so your auditor knows how each conclusion was reached.

Samples

See them before you sign.

All samples use a fictional company, Syarikat Contoh Sdn Bhd, and mock data. Your reports follow the same layout with your own numbers.

LIVE DASHBOARD · SAMPLE

NOC dashboard

The read-only view your staff get: device status, link utilisation, open alerts and SLA timers.

Open dashboard

PDF · OCTOBER 2026 · SAMPLE

Monthly Service Report

Four pages: summary, SLA scorecard, availability, incidents, vendor performance and the coverage register.

Download PDF View in browser

PDF · P1 · SAMPLE

Major Incident Report

A primary internet link outage, from first alert to ISP fix, with every escalation timestamped.

Download PDF View in browser

Devices, vendors and telemetry

What we can monitor.

Supported devices and vendors, what we watch on each, the telemetry we accept, and whether you need our agent. The same for every plan.

See what we support

Limitations

What remote monitoring can't do.

We'd rather you know these now than find out during an incident.

Ping-only devices

A device with no SNMP, agent or API can only be checked for up/down and response time. This includes most ISP-managed routers unless your ISP grants read-only SNMP.

Only what the vendor reports

We can read only what a device exposes over SNMP or its API. Some models don't report VPN tunnels, fan speed or power supply state, and consumer-grade gear often reports very little.

No traffic content

We see how much bandwidth is used, not what it's used for. Per-user or per-application usage needs NetFlow or sFlow, which is not in the Remote plan.

Not a security service

We don't monitor for attacks, malware or intrusions. Syslog alerts are for operational faults only. A NOC is not a SOC.

Cloud and SaaS from the outside

For Microsoft 365, Google Workspace and similar services we check reachability and response time from outside, and track the provider's status page. We can't see inside the provider.

Short blips can be missed

A fault that starts and clears between two checks, such as a 20-second link drop, may not raise an alert. Device logs often catch these when the device sends syslog.

When your site goes dark

If your internet or the collector goes down, we see the whole site as unreachable but lose detail inside it until it's back. The collector stores readings for up to 24 hours and uploads them when it reconnects.

AI checks find, they don't fix

AI logins are read-only, so the AI can diagnose a problem but never repair it. Fixes are made by your team or, under the L2 add-on, by our engineers with your approval. Devices without a read-only SSH or API role get monitoring-only AI analysis.

No hands on-site

We can't press a button or re-seat a cable. Physical steps are done by your staff, guided by us on the phone, or by your vendor. If you need someone on-site, see the Essential or Standard plan.

Next step

Send us your device list and we'll confirm coverage.

We'll tell you which devices get full monitoring, which are ping-only, and what the monthly fee comes to.

[email protected]