N-able (formerly SolarWinds MSP) ships two flagship RMMs: N-central for larger MSPs needing deep automation, and N-sight (formerly RMM) for SMB-focused MSPs wanting simpler workflows. Both have strong patch management, monitoring, and a long ecosystem of partner integrations.
Many MSPs still buy security, compliance, and breach detection as separate procurement lines next to their RMM. N-able offers EDR add-ons. For cross-platform compliance evidence, M365 / Entra identity threat detection and response (ITDR) with endpoint correlation, administrator elevation and execution prevention, replacement prioritization, and SaaS / shadow-AI discovery, check N-able's documentation.
Technicians get browser-based remote control, a background admin workspace, and a remote shell on Windows and Mac, scripting on Linux, and ad-hoc support for computers without the agent, with end-to-end encrypted sessions available. Lavawall can run on its own as your RMM, or be installed through Datto RMM, NinjaOne, ConnectWise, Kaseya, Intune or any tool that runs a script, while you move over.
Where Lavawall® wins for MSPs
Lavawall® puts security depth, compliance evidence, and breach-detection coverage in the same agent and console as patching, scripting, and remote support. For MSPs delivering CMMC 2.0, CPCSC, SOC 2, HIPAA, PCI DSS, or cyber-insurance readiness, the RMM is also the evidence base.
Cross-platform coverage is the second. Lavawall® patches, scripts, and monitors Windows, macOS, and Linux with one agent, one console, and one set of compliance reports, with remote control on Windows and macOS. Check N-able's documentation for its macOS and Linux depth.
For MSPs running N-central plus a separate Vanta / Drata GRC tool, a separate ThreatLocker elevation-control tool, a separate M365 monitoring add-on, and a separate Zendesk-class helpdesk, Lavawall® brings the RMM, GRC, breach detection, administrator elevation, and helpdesk into one platform. It can start alongside N-able so the move does not disrupt clients.
Where N-able (N-central / N-sight) wins
N-able is one of the most mature MSP RMMs in the market. Deep automation libraries, strong patch automation, well-documented ScreenConnect-class remote control (Take Control), and broad partner integrations make it a long-standing core for many MSPs.
For MSPs whose Windows-fleet automation is the central concern and whose security and compliance are handled by other dedicated tooling, N-able alone may be enough.
N-able customers can deploy Lavawall® through N-able-pushed scripts and run both side by side while they move over.
Feature comparison
| Feature | Lavawall® | N-able (N-central / N-sight) |
|---|---|---|
| MSP-focused RMM with mature automation | Standard scripting and APIs | Yes, mature MSP-focused RMM |
| Cross-platform agent (Windows, macOS, Linux) | Yes; remote control on Windows and macOS, scripts, patching, and monitoring on all three | Strong Windows; lighter mac/Linux |
| Public application patch catalogue | 7,400+ applications, published openly | OS + bundled third-party |
| Compliance framework mapping (CMMC 2.0 / NIST / SOC 2 / HIPAA) | 70+ frameworks; continuous evidence with System Security Plan (SSP) and remediation plan (POA&M) | Reports; not framework-mapped GRC platform |
| M365 / Entra ID / Azure breach detection with endpoint correlation | Native multi-tenant identity threat detection and response (ITDR) | Limited |
| Google Workspace breach detection | Native | Limited |
| Administrator elevation and execution prevention (no kernel driver) | Native | No |
| Curated SaaS / shadow-AI discovery (1,277-app catalogue) | Native with user attribution | No |
| Replacement prioritization (battery / TPM / SMART / RAM / age) | Multi-factor scoring | Lifecycle dates |
| Akira ransomware indicator hunter | Native | No |
| Per-named-agent helpdesk (unlimited tickets) | US$59 / agent / month | Add-on |
| Built and used by an audit firm | ThreeShield (CISSP / CISA) | No |
Who should pick which?
Pick Lavawall® if…
MSPs that want an RMM with security, GRC, breach detection, and analytics built in, installed through N-central or N-sight while they move over.
MSPs delivering CMMC 2.0, CPCSC, NIST 800-171, SOC 2, ISO 27001, HIPAA, PCI DSS, PIPEDA, BC E-Health Act, Alberta HIA, NERC CIP, CIRO, CPA Canada, or Australian Essential Eight readiness as a service.
MSPs with growing macOS / Linux fleets that want patching, scripts, and monitoring for them from the same agent as Windows.
Frequently asked
- Does Lavawall® replace N-able?
- Yes. Lavawall® covers patching, scripting, remote support, and inventory itself, along with security, GRC, and analytics. It can be installed through N-able, and both can run side by side while you move over.
- Can Lavawall® be deployed through N-able?
- Yes. PowerShell and bash scripts deploy it through N-central / N-sight to Windows, macOS, and Linux endpoints.
- Does Lavawall® coexist with N-able's own EDR?
- Yes. Lavawall® coexists with N-able's EDR offerings and major third-party EDR products (Defender, Huntress, Sophos, SentinelOne, CrowdStrike) without conflicts and surfaces their state in the Lavawall® console.
- Will Lavawall® conflict with the N-able agent?
- No. Lavawall® coexists with major RMM agents without conflicts.
Security and FIPS 140-3 by design
Lavawall® is built so the secrets it manages stay encrypted where you are. The secrets that matter (vault items, server credentials, and any key pushed to an endpoint) are encrypted where you are and stored by us only as ciphertext, so an administrator with full access to our database sees encrypted blobs and nothing to open them with. See security and privacy.
Lavawall®’s relay and Windows and Mac agents use a FIPS 140-3 validated cryptographic module, the Go Cryptographic Module, NIST CMVP certificate #5247, and sign-in can be restricted to a FIPS 140-3 validated security key, the YubiKey 5 FIPS Series, certificate #5291. In-browser encryption uses the FIPS 140-3 approved algorithms. Full detail is on FIPS 140-3 support.
That same secret-handling powers WireGuard deployment across the fleet. Each endpoint generates its own private key locally and only the public key comes back, so the tunnel’s private key is never in a script, a log, or our database. Weighing N-able for a regulated environment? This is the line worth checking against your obligation.