All your clients.
One single platform.
Deploy a probe at each client site, keep one console on your side. Monitoring, remote access, audit and AI: everything works through the probe, without VPN, with strict isolation between your clients.
Multi-tenant view
124 devices · 3 sites
48 devices · 1 site
210 devices · 12 sites
1 console
All your clients and all their sites in a single interface
0 VPN
The probe initiates an outbound connection — nothing to open at the client site
Total isolation
Each client is a watertight tenant: rights, data, rules
Real time
Alerts from all clients, consolidated by severity
Managing N clients should not require N tools
For a service provider, each client brings its own tools, accesses and procedures. Time is lost switching contexts, and no tool gives the big picture.
-
One tool per client
A monitoring instance here, a VPN there, a spreadsheet for the rest: nothing consolidates.
-
VPNs and open ports everywhere
Each client site requires its own inbound access: heavy to deploy, risky to maintain.
-
No big picture
Impossible to simply answer "which clients have critical alerts right now?"
-
Degraded reaction time
Connecting to the right tool, the right VPN, with the right account… before even starting to diagnose.
How much time do your technicians spend switching tools instead of solving incidents?
Remote probes, without VPN or open ports
A lightweight probe is installed at each client site and connects via outbound WebSocket to your platform. The probe initiates the connection: no inbound flow, no port to open, no VPN to maintain at the client site.
-
Outbound connection only
The probe establishes an encrypted WebSocket channel to the platform — the client's firewall stays closed to inbound traffic.
-
Unique key authentication
Each probe has its own individually revocable key, and its exchanges are encrypted.
-
Heartbeat & outage detection
Online status continuously checked: a probe silent for more than 60 seconds is marked offline and its running tasks are cleanly cancelled.
-
Multi-site and evolving capabilities
One probe can serve several sites, and announces its capabilities at each heartbeat: new features arrive without reinstalling.
Deployment in 3 steps
Install the probe
On a machine at the client site — lightweight installation.
It connects to your platform
Encrypted outbound connection, authenticated by its unique key.
The site is covered
Collection, monitoring and remote access flow through the probe.
What the probe relays
Collection
SNMP · SSH · Ping
SSH / Telnet
Browser-based terminal
RDP
Recorded remote desktop
Web
Non-routed admin interfaces
Everything flows through the probe
The probe is not just a collector: it relays all your operations on the client site, from monitoring to remote maintenance.
-
Full remote collection
Inventory, SNMP, SSH, Ping: the site devices are collected as if they were local.
-
Remote maintenance without VPN
Bastion SSH, RDP and Web sessions are relayed by the probe — recorded and audited like direct sessions.
-
Tasks tracked end to end
Every task sent to the probe is traced: progress, logs, timeout, clean cancellation on disconnection.
-
Collection mode per site
Local, probe or automatic — and never a silent fallback: if a site's probe is unavailable, the platform reports it instead of collecting another way.
A consolidated view of all your clients
The multi-tenant dashboard aggregates the state of all your client companies: devices, alerts by severity, open audit recommendations. You see at a glance where to act first.
-
Aggregated dashboard
Devices, critical/warning alerts and open recommendations, counted per client.
-
Drill-down per company
From the global view to the detail of one client, its sites and devices, in two clicks.
-
Actions from the central view
Acknowledge or resolve alerts from any client without switching context.
-
Audit is consolidated too
Network audit recommendations from all clients surface in the same view, prioritized.
Consolidated monitoring
12
client companies
1,847
monitored devices
3
critical alerts
27
open recommendations
Each client is a watertight tenant
Isolation is not a display option: each company has its own users, rules and data. A technician only sees the clients in their scope, and nothing leaks between tenants.
-
Rights per client
Scopes, roles and 2FA requirements are defined per company — a technician can be limited to one client, or even one site.
-
Rules adjusted per client
Audit rules, alert thresholds and monitoring profiles are configured company by company.
-
AI and knowledge compartmentalized
Enabled AI tools and the knowledge base (procedures, standards) are specific to each company.
-
Quota-based licences, split per client
A single deployment serves several clients: quotas (devices, remote accesses, log collectors) are tracked client by client.
Concrete use cases
How service providers use Intelligent Networks daily
MSP — multi-client managed services
Monitor the networks of dozens of clients from a single console. One probe per client, consolidated alerts, and built-in remote maintenance to intervene without VPN.
MSSP — security monitoring
Continuous configuration audit, detection of insecure protocols and topology risks at each client, with per-company reports to demonstrate your value.
IT services & integrators
Deploy a probe for the duration of a project: inventory and topology of the client site within hours, without touching their firewall, then remove it when the assignment ends.
One-off audit
For a flash diagnostic or pre-sales: a temporary probe is enough to map the network, audit configurations and produce a report.
Do you manage the network of several clients?
Let's talk about your business: we will show you the platform with a real multi-client scenario.