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.
Like every RMM, N-able is built for IT operations work, not for the security, compliance, and breach-detection layer that has become a separate procurement line on most MSP P&Ls. N-able offers EDR add-ons, but cross-platform compliance evidence, M365 / Entra identity threat detection and response (ITDR) with endpoint correlation, kernel-free application control, replacement prioritization, and SaaS / shadow-AI discovery remain gaps.
Lavawall® drops in via N-able as a script and runs alongside it, providing the security and compliance layer with a single agent on Windows, macOS, and Linux.
Where Lavawall® wins for MSPs
Lavawall® delivers the security depth, compliance evidence, and breach-detection coverage that N-able does not address natively. For MSPs delivering CMMC 2.0, CPCSC, SOC 2, HIPAA, PCI DSS, or cyber-insurance readiness, Lavawall® is the evidence base; N-able is the operational RMM.
Cross-platform parity is the second gap. N-able's Windows automation is mature; macOS and Linux coverage is thinner. Lavawall® treats Windows, macOS, and Linux as first-class with one agent, one console, one set of compliance reports.
For MSPs running N-central plus a separate Vanta / Drata GRC tool, a separate ThreatLocker app-control tool, a separate M365 monitoring add-on, and a separate Zendesk-class helpdesk, the Lavawall® / N-able combination consolidates the security, GRC, breach detection, app control, and helpdesk layers without disrupting N-able.
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 sufficient.
N-able customers can deploy Lavawall® via N-able-pushed scripts and gain the security and compliance layer without leaving N-able.
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) | Full security parity across all three | Strong Windows; lighter mac/Linux |
| Public application patch catalog | 7,400+ applications, published openly | OS + bundled third-party |
| Compliance framework mapping (CMMC 2.0 / NIST / SOC 2 / HIPAA) | 15+ 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 |
| Application control without kernel driver | Native | No |
| Curated SaaS / shadow-AI discovery (1,130+ catalog) | 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 running N-central or N-sight that need a security, GRC, breach-detection, and analytics platform alongside it.
MSPs delivering CMMC 2.0, CPCSC, NIST 800-171, SOC 2, ISO 27001, HIPAA, PCI DSS, PIPEDA, BC HIA, Alberta HIA, NERC CIP, IIROC, CPA Canada, or Australian Essential Eight readiness as a service.
MSPs with growing macOS / Linux fleets that have outpaced N-able's strengths.
Frequently asked
- Does Lavawall® replace N-able?
- It can. Lavawall® provides patching, scripting, remote support, and inventory. But most N-able shops choose augmentation instead: keep N-able for automation, add Lavawall® for security, GRC, and analytics.
- Can Lavawall® be deployed through N-able?
- Yes. PowerShell / bash scripts deploy via 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, FIPS 140-3, and zero-knowledge by design
Most RMMs hold the keys to everything they manage. Lavawall® is built the other way. 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 agents and relay run on 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. An RMM that automates a VPN with a script carries that key through its job history and the vendor’s database instead. Weighing N-able for a regulated environment? This is the line worth checking against your obligation.