Frequently asked questions
Clear answers, fast.
How the platform works, how it deploys, and how it keeps your network safe.
Platform
Correlation, root cause, the digital twin and prediction.
What does AssureMesh do?
AssureMesh is network intelligence for enterprise NOC teams. It builds a digital twin of your network, correlates alert storms into incidents, finds the likely root cause with evidence, shows the blast radius across devices, sites and business applications, predicts what needs attention next, and suggests remediation steps for your engineer to review and run.
Does root cause analysis need an AI provider?
Deterministic, pattern-based root cause analysis runs on its own, with no external AI key. Optional AI enrichment adds a narrative when you configure a provider, and the platform shows clearly when it is switched off.
What is the network digital twin?
A multilayer model of your network covering physical links, routing and dependencies, with versioned snapshots and a routing engine. It answers reachability, isolation and path questions, highlights single points of failure, and verifies a proposed change against your reachability and isolation intents.
How does predictive early warning work?
Least-squares trend forecasting runs over metric history such as interface errors and CRC, utilisation, BGP stability, CPU and memory. Each warning carries a confidence level and an estimated time to threshold.
How does AssureMesh fit with the tools we already use?
It works alongside them: your monitoring, ticketing and workflows stay as they are. AssureMesh collects its own telemetry and sends notifications to Slack and email. Which monitoring and ticketing tools to connect first is decided together with early-access customers.
Can we set our own detection thresholds?
Yes. Tenant owners configure supported detection thresholds. Values are validated, versioned and applied wherever the live detector supports that override.
Deployment
Collectors, devices, clouds and onboarding.
Can the collector run on premises?
Yes. An edge collector runs inside your network, so device management interfaces stay private. The deployment plan records whether the control plane is cloud-hosted, on premises or hybrid.
Which devices and clouds are supported?
Cisco IOS-XE, Arista EOS and Juniper Junos over gNMI, NETCONF, eAPI and SSH CLI; SNMP v2c and v3 devices; and AWS, Microsoft Azure and Google Cloud through cloud agents. Coverage is reported per device in clear levels, from recognised and generically monitored through enhanced telemetry, verified detection and field validation.
How do devices get connected?
Your tenant owner connects the collectors and cloud accounts AssureMesh reads from, using read-only credentials. Every decision is written to a tamper-evident audit log, and each customer is a separate tenant with isolated data. To talk through your environment, request a demo.
Security
Access, data handling and disclosure.
What does read-only by default mean?
Write actions to devices are blocked in the platform itself. Your engineer runs every command. Tenant administration, including users, devices, thresholds, incident workflow and notifications, stays fully manageable.
How is data sent to an AI provider handled?
AI enrichment is optional and off until you enable it. Before it is turned on, the provider, redaction, retention and tenant opt-out are agreed with you explicitly.
What security assurance can we review?
The AssureMesh security programme is documented. The security page covers release provenance you can verify yourself, sub-processors and the vulnerability disclosure process, and deeper architecture and control detail is shared during your security review.
How do I report a vulnerability?
Email security@assuremesh.com and follow the process on the security page.
Still curious?