The customer is at the centre — whoever owns the service relationship. NetPulse puts a guided diagnostic app in their hand, so they get answers in seconds rather than waiting in a support queue.
The customer experience starts the moment something feels wrong. NetPulse closes that loop from the customer's phone to the network and back again — mostly without them needing to call anyone.
Customer reports a problem via the NetPulse app. The app silently detects whether they're on their home connection, then runs guided diagnostics: WiFi signal, DNS, gateway ping, and speed test.
In parallel, NetPulse runs a live check across every layer of the customer's connection — physical port health, active session state, and equipment status — and correlates the results into a single verdict. All before the customer finishes reading the first screen.
If the network is healthy, the app guides the customer to the right action: speed comparison vs their contracted plan, WiFi tips, an event marker for intermittent issues, or a downdetector check.
If the issue can't be self-resolved, a ticket arrives with full network context already attached and a clear domain classification. No blind calls, no "can you describe the problem again."
One platform across the full operations stack — no stitching together five different tools.
Android app guides customers through the right tests for their issue type. Detects on-network vs off-network automatically. Issue picker leads to targeted advice or a pre-analyzed ticket — never a dead end.
Automated analysis across every layer of the customer connection — physical, datalink, network, and CPE — correlated into a single confidence-scored verdict. Engineers get a clear domain classification, not a raw data dump.
Per-customer SLA countdown with configurable thresholds. Auto-triggers diagnostic as the SLA approaches. On breach, escalates automatically and attaches the diagnostic context to the ticket.
Continuously monitors enterprise customer connections. The moment a link goes down, a ticket is created, a diagnostic runs, and device evidence is attached — automatically, before anyone calls. On recovery, a post-mortem is generated without any manual work.
Auto-discovery builds a hierarchical live map — access, aggregation, and core — with real-time link status, site clustering, and a routing event overlay that shows protocol changes as they happen.
Per-hop path analysis with ICMP latency and loss tracking. Historical traces and event marks show when degradation started and where in the path. Y.1731 and TWAMP measurement on the roadmap.
Automated config backup per device with full diff history. Change tracking correlated with tickets and outages. VLAN path discovery across the network. Know what changed, when, and on which device.
Per-device power consumption via SNMP, aggregated to network-wide kWh and CO₂ equivalents. Built for Nordic sustainability reporting requirements — stadsnät boards need this for annual reporting.
Remote NetPulse probe nodes run locally at your PoPs or customer sites — keeping all management traffic inside your network. Probes relay diagnostics, metrics, and config backups over an encrypted channel with no inbound firewall rules required.
A built-in security workspace that turns your existing network into its own sensor: multi-vendor config-compliance auditing, RPKI route-origin validation, sFlow anomaly detection (DDoS / scan / reflection), BGP monitoring via BMP, Flowspec mitigation, and DNS RPZ threat blocking — all feeding the same incident system, no separate stack to stitch together.
A NIS2 readiness cockpit scores your posture across the directive's control areas from live data — documentation, segmentation, hardening, backup, supply-chain/CVE exposure, and crypto. CSIRT incident reporting tracks the 24h / 72h / 1-month deadlines, and an interactive blast-radius map shows exactly which customers, enterprises, and SLA euros a failed router or fibre puts at risk — in seconds, with audit-ready topology proof.
When something feels wrong, the customer is the first to know — and with NetPulse, they become part of the diagnosis. The app measures the connection from where they're sitting, combines that with a live network check, and gives them a clear answer without a phone call.
When a ticket is needed, it arrives pre-analysed: the engineer knows whether the fault is on the network, the CPE, or the customer's own equipment before they say a word.
NIS2 puts Nordic stadsnät and ISPs in scope as essential entities. Instead of buying a separate SIEM, a separate compliance tool, and a separate impact-analysis spreadsheet, NetPulse derives all three from the live network — one platform, one source of truth.
A single readiness score across the directive's control areas — documentation & asset inventory, intrusion detection, segmentation & Zero Trust, authentication & hardening, logging, backup & redundancy, incident handling, supply-chain, and cryptography — each scored from live NetPulse data with per-area gap lists. Board-ready evidence, not a self-assessment questionnaire.
Open a report the moment you become aware of an incident and NetPulse tracks the NIS2 clock for you — 24-hour early warning, 72-hour notification, one-month final report — with on-time/overdue status and a ready-to-submit export. Reportable incidents are surfaced automatically from the platform's own detection, pre-filled from the outage onset. Swedish PTS (LEK) export included.
Click any device or link to fail it and see the consequence in seconds: which downstream customers go dark, how many are enterprise vs private, the SLA exposure in € / SEK / NOK per hour, single-points-of-failure, and which surviving uplinks would overload. The same engine identifies affected subscribers during a real outage and pushes them a notification before they call.
Your live inventory is matched against a CVE catalogue and end-of-life dates per vendor, model, and software version — so a critical advisory on a Nokia BNG or an end-of-support access switch shows up as a scored risk against the actual boxes in your network, mapped to the NIS2 supply-chain control.
The network becomes its own sensor — sFlow anomaly detection (DDoS, scanning, reflection), BGP monitoring over BMP, RPKI route-origin validation, and DNS RPZ threat blocking — with confirmation-gated Flowspec mitigation that never auto-announces. Detection feeds straight into the incident system alongside everything else.
Capture an immutable, dated snapshot of the entire network graph as evidence — "the network looked like this on this date" — exportable for auditors and rendered graphically, not just as JSON. Multi-vendor config-compliance baselines back it up, flagging telnet, SNMP v1/2c, weak crypto, and missing centralized AAA across every vendor in your fleet.
In carrier and city networks, the customer sits between two organisations — the city carrier that owns the fiber and the ISP that owns the service. NetPulse holds both accountable to that customer, with the right view for each party.
The city carrier owns the fiber; the ISP owns the relationship. When the customer reports a problem, both parties need the same diagnostic truth. NetPulse gives each the right view — infrastructure detail for the carrier, service experience for the ISP — with no finger-pointing and no duplicated calls.
An ISP operating across multiple city networks can log in once and see all their customers — whether they're on Digimitt, Umenet, or Mittnät fiber. One portal, one diagnostic workflow, filtered strictly to their own subscribers. The customer gets consistent support regardless of which carrier's network they're on.
Customer subscriber records sync from COS Systems, Bitvis FiberFlow, or Packetfront BECS — so when a customer opens the app, their service plan, ISP, and equipment are already known. No manual lookup, no misidentified subscribers.
Every diagnostic session, ticket, and configuration record is scoped to its tenant. An ISP sees only their own customers. A city carrier's data is never visible to neighbouring operators. The customer's data belongs to their service relationship — not to the platform.
No forklift upgrades. NetPulse connects to the devices you already have — access switches, aggregation routers, BNG, ONTs, and CPEs.
Don't see your vendor? Our driver framework is open — new vendors are added within days, not months.
We'll walk you through the platform with your own NE list, your vendor mix, and your subscriber model. No generic demo — real data, real insight.
Whether you're evaluating platforms, scoping an integration, or ready to onboard — we'd love to hear from you. We're a small team and respond within one business day.