Category
RMM for MSPs in DACH: tenant separation, margin and NIS2
An MSP earns on efficiency and trust. An RMM therefore has to do three things: separate tenants cleanly, allow a predictable margin, and turn your clients' compliance topics into a sales story rather than a risk.
| Dimension | OneLog | Other RMM |
|---|---|---|
| Tenant separation | Multi-tenant by design, hard isolation per client, role-based view per tenant | Multi-tenancy available; depth of isolation varies by provider/plan |
| Data location / hosting | EU-sovereign (STACKIT Sovereign Cloud, headquartered in Germany), no US cloud exposure | Frequently US-operated or US parent company — CLOUD Act exposure |
| NIS2 as a selling point | NIS2 mapping out of the box, evidence can be generated per tenant | Generic RMM; NIS2 evidence left to the MSP's own efforts |
| AI layer / efficiency | AI agents resolve standard tickets autonomously — margin without more staff | Scripting and automation, no autonomous agent layer |
| Pricing model | Transparent, predictable | Per-device with minimum commitments, annual lock-in |
As of June 2026. Fair representation based on publicly available information; details of other RMMs vary by provider and plan.
Three requirements that decide an MSP RMM
For an MSP, the RMM is not one tool among many but the central production machine. Three things decide whether it holds up:
- Tenant separation — cleanly isolated clients across the entire managed fleet.
- Margin — a pricing model that remains predictable and does not play every endpoint you win off against your own profitability.
- Compliance as a selling point — in DACH, that means above all data location and NIS2.
Multi-tenant by design
An MSP serves many clients in parallel. Separation must therefore be hard, not cosmetic. OneLog is multi-tenant by design: every tenant is isolated, and views and permissions are assigned role-based per client. A technician sees exclusively the fleet they are authorised for — and client data does not mix across tenant boundaries.
That is not merely a matter of convenience but of liability: anyone managing other people’s client systems must be able to demonstrate the separation to auditors and to their own clients.
Margin: predictable rather than escalating per device
Many established RMMs charge per endpoint, with minimum commitments and annual lock-in. That works for the vendor — for the MSP, it eats margin as soon as the managed fleet grows.
OneLog relies on two levers:
- Predictable terms. Transparent tiering without aggressive per-device escalation.
- AI layer as efficiency lever. AI agents work through defined standard tickets autonomously. Patch incidents, recurring remediation and routine work run before an operator intervenes.
The economic effect: the managed fleet can scale without headcount growing in step. Margin comes from automation, not from overtime.
The AI layer as an overlay
The AI agent layer is not a replacement for your team but an overlay on top of existing RMM operations. It takes over the recurring, well-defined work and lets your technicians work on the cases that genuinely need experience. That improves the response time per tenant — and with it what the client actually notices.
NIS2 as a selling point towards clients
NIS2 is bringing more and more mid-sized companies (the German Mittelstand) into scope — precisely the clients an MSP serves. For many of them, this is a procurement topic on which they are looking for support.
With OneLog, that becomes a selling point instead of a burden:
- NIS2 mapping out of the box. Asset, patch and risk evidence is mapped directly to the NIS2 obligations.
- Evidence per tenant. You generate the records per client — cleanly separated, without manual collation.
- Sovereignty as an argument. EU-sovereign operation in the STACKIT Sovereign Cloud, no US cloud exposure. For public sector buyers and clients close to KRITIS (German critical infrastructure), this is often the deciding factor.
A fair assessment
Established RMMs from the US market are technically mature and a solid basis for many MSPs. But as soon as data location, the CLOUD Act or NIS2 evidence come up in client conversations — and in DACH they increasingly do — the sovereignty and compliance question becomes the differentiator. That is precisely where OneLog plays to its strengths.
Frequently asked questions
- What must an RMM for MSPs in the DACH region be able to do?
- Clean tenant separation across many clients, a predictable pricing model for the MSP's own margin and robust compliance evidence. In the DACH region, data location and NIS2 are added as procurement criteria.
- How does OneLog support MSP margin?
- Through two levers: predictable terms instead of aggressive per-device escalation, and an AI agent layer that works through standard tickets autonomously. That lets the managed fleet scale without headcount growing in step.
- How clean is tenant separation in OneLog?
- OneLog is multi-tenant by design: every client is isolated, and views and permissions are role-based per tenant. A technician sees only the fleet they are authorised for.
- Does OneLog help when selling to clients subject to NIS2?
- Yes. NIS2 is mapped within the RMM, and asset, patch and risk evidence can be generated per tenant. That turns NIS2 into a selling point for the MSP instead of extra work.
See OneLog in your environment
Monitors and maintains your IT remotely and fixes many incidents automatically — hosted in the EU, with no dependency on US cloud providers. NIS2 requirements are built in from the start.