How is the Datto RMM deployment different from other RMMs?

For most RMMs you paste a script. For Datto RMM, Lavawall® ships ready-made components (a .cpt file for Windows and one for Mac) that you import into the Automation section and run as a deployment job. It is the same import-and-run workflow you already use for Datto components.

What is the LAVAWALL_KEY site variable for?

LAVAWALL_KEY is a site variable that holds the authentication code from your Lavawall® console. It is only required for MSP and Audit accounts. You create it once per site so the component knows which tenant the endpoints belong to.

Can I deploy Datto RMM agents from Lavawall as well?

Yes. You can copy a Site GUID from Datto RMM and paste it into the Lavawall® console under CLOUD/SAAS, then Datto RMM, to deploy Datto agents from Lavawall®. The integration runs in both directions.

Datto RMM integration

Boost Datto RMM with Lavawall

Lavawall® deploys through Datto RMM as a ready-made component, the same import-and-run workflow you already use. Keep Datto RMM for remote management, and let Lavawall® add cross-platform patching, 15+ GRC frameworks, and Microsoft 365 and Google Workspace breach detection from one multi-tenant console.

Start free, no credit card See the setup steps

Windows and Mac components · site variable · multi-tenant

How the Datto RMM integration works

Datto RMM is good at remote management, scripting, and basic patching. It does not give you compliance evidence for CMMC 2.0 or NIST CSF, it does not detect Microsoft 365 or Google Workspace breaches, and it does not run an indicator-of-compromise hunt for ransomware staging tools. Lavawall® fills those gaps and deploys as a native Datto RMM component.

Unlike other RMMs where you paste a script, Datto RMM uses downloadable components. Lavawall® ships a Windows component and a Mac component (.cpt files). You import the component into Datto RMM's Automation section, create a deployment job, and run it as the system account. The component installs the Lavawall® agent, which then runs alongside your Datto agent.

The integration also runs the other way. You can deploy Datto RMM agents from Lavawall® by copying a Site GUID out of Datto RMM and pasting it into the Lavawall® console under CLOUD/SAAS, then Datto RMM.

What data flows

Once the component installs the agent, Lavawall® collects and correlates:

Endpoint state across Windows, macOS, and Linux: patch status, configuration posture, application inventory, and hardware health.
Cloud signals from Microsoft 365, Entra ID, Azure, and Google Workspace, pulled directly from those tenants.
Compliance evidence mapped to 15+ frameworks, updated in real time as the fleet changes.
Security findings from configuration assessment, ransomware indicator hunting, and AV or EDR correlation.

Lavawall® reads directly from the endpoint and the cloud tenants, so your coverage is not limited to what Datto RMM happens to inventory.

Setup steps

Site variable (MSP and Audit accounts)

Get your authentication code from the Lavawall® console.
In Datto RMM, create a site variable named LAVAWALL_KEY and set it to that code. This step is only required for MSP and Audit accounts.

Windows agent

Download the Windows .cpt component from Lavawall®.
Import the component into Datto RMM's Automation section.
Create a deployment job targeting your devices.
Run the job as the system account.

Mac agent

Follow the same steps using the Mac-specific .cpt component.

Start free →

Thinking about switching?

You do not have to choose. Most MSPs run Datto RMM and Lavawall® together, with Datto handling remote management and Lavawall® handling security, GRC, breach detection, and analytics. If you are weighing a full move, the Lavawall® alternative to Datto RMM page lays out where each tool fits and what consolidating looks like.

Frequently asked

How is the Datto RMM deployment different from other RMMs?: For most RMMs you paste a script. For Datto RMM, Lavawall® ships ready-made components (a .cpt file for Windows and one for Mac) that you import into the Automation section and run as a deployment job. It is the same import-and-run workflow you already use for Datto components.
What is the LAVAWALL_KEY site variable for?: LAVAWALL_KEY is a site variable that holds the authentication code from your Lavawall® console. It is only required for MSP and Audit accounts. You create it once per site so the component knows which tenant the endpoints belong to.
Can I deploy Datto RMM agents from Lavawall® as well?: Yes. You can copy a Site GUID from Datto RMM and paste it into the Lavawall® console under CLOUD/SAAS, then Datto RMM, to deploy Datto agents from Lavawall®. The integration runs in both directions.
Does Lavawall® replace Datto RMM?: It does not have to. Many MSPs keep Datto RMM for remote management and let Lavawall® add security, GRC, breach detection, and analytics. If you are weighing a full switch, the Datto RMM comparison page walks through where each tool fits.