Co-managed IT RMM

Share endpoint operations. Keep every responsibility explicit.

Nizlo is an earlier-stage, Windows-first RMM for MSPs and internal IT teams evaluating a shared operating model. Pilot one authorized endpoint, attach a named owner to every handoff, and preserve identity, security, backup, service management, documentation, contracts, and incident response in the systems and teams built to own them.

Start the 14-day trial Explore all features

One shared support loop

Evaluate the platform and the handoffs at the same time.

A co-managed pilot should prove that both teams can find the same endpoint, understand the same signal, know who acts next, verify the result, and retain evidence without creating duplicate or silent ownership.

A shared endpoint record

Organize authorized Windows endpoints by customer and site, then review inventory, online state, health, software, and recent activity from one operating view.

Signals with a named owner

Evaluate alert visibility and routing against a written responsibility matrix so the internal team and MSP know who investigates, escalates, communicates, and closes each condition.

Controlled maintenance evidence

Review Windows patch posture, approvals, maintenance windows, reboot expectations, exceptions, and resulting evidence without assuming the platform replaces change authority.

Reviewed repeatable work

Test a harmless script on one noncritical endpoint, retain its output, and expand only after scope, permissions, ownership, rollback, and stop conditions are agreed.

Authorized remote support

Move from an endpoint signal to approved technician action while keeping device identity, customer context, recent activity, user coordination, and escalation expectations close to the session.

Evidence for service reviews

Use fleet, patch, alert, job, and activity views to review exceptions, recurring work, unclear handoffs, retained controls, and the next rollout decision together.

A controlled co-managed IT pilot

Prove one complete support path before enrolling a fleet.

Write the responsibility matrix

Name the owner, approver, operator, escalation path, communication duty, evidence requirement, rollback owner, and removal authority for enrollment, alerts, patching, scripts, remote access, and reporting.

Test one noncritical Windows endpoint

Confirm identity and inventory, create a safe signal, review patch posture, run a harmless script, exercise authorized support, inspect activity, and complete a documented internal-team-to-MSP handoff.

Make an explicit rollout decision

Record setup time, alert workload, ambiguous ownership, missing controls, retained tools, complete cost, user impact, offboarding behavior, and the exact conditions for expanding, holding, or removing the pilot.

Co-managed responsibility matrix

Decide who acts before the first real exception arrives.

“Shared” should never mean unowned. Put each decision in the service agreement and operating runbook, then use the pilot to test whether the handoff works under real conditions.

Endpoint enrollment

Who approves persistent management, owns the device list, and removes access when the service or employment relationship changes?

Alerts and incidents

Who acknowledges each signal, investigates it, contacts the user, escalates security events, and records the final outcome?

Patching and reboots

Who approves classifications and windows, records exceptions, coordinates business impact, verifies results, and owns rollback?

Scripts and automation

Who reviews content, target scope, permissions, secrets, testing, change records, stop conditions, and recovery before a run?

Remote access

Who authorizes support, confirms user expectations, controls privileged access, reviews activity, and responds to suspected misuse?

Reporting and review

Which evidence belongs in the service review, who owns unresolved exceptions, and what triggers expansion, remediation, or removal?

Review the internal IT path Review the small MSP path Build the client onboarding plan Define the offboarding path

Co-managed IT RMM questions

Define authority, evidence, escalation, and exit before scale.

What is co-managed IT RMM?

Co-managed IT RMM is a shared operating approach in which an internal IT team and an MSP use remote monitoring and management workflows while retaining explicit responsibility for endpoint enrollment, alerts, patch decisions, automation, remote support, reporting, escalation, and removal. The tool does not define the service agreement or transfer authority by itself.

Who should own the RMM platform in a co-managed model?

Ownership should be written into the service agreement and operating runbook. Define who administers the workspace, grants technician access, maintains the authorized endpoint list, approves policies and scripts, reviews activity, manages offboarding, and owns the data and evidence required when the relationship ends.

Does RMM replace Intune, EDR, backup, or a PSA?

No. Keep identity, device policy, endpoint security, backup, service management, documentation, contracts, and incident response in the systems and teams responsible for them. Evaluate Nizlo only for the endpoint monitoring and technician workflows it can demonstrate during the pilot.

How should a co-managed RMM pilot begin?

Start with one authorized, noncritical Windows endpoint. Agree on ownership first, then validate enrollment, inventory, a safe alert, patch visibility, a harmless script, remote-support authority, activity evidence, escalation, and clean removal before expanding.

How does the Nizlo co-managed IT trial work?

Nizlo offers a 14-day trial with no credit card. Use one noncritical endpoint and a written responsibility matrix to test a complete shared support loop, record missing capabilities and handoff friction, and make an explicit expand-or-remove decision.

Founding Tester offer

Test the shared operating model on one endpoint.

The first five successful paid upgrades receive 75% off for life, the next five receive 50% off for life, and the next ten receive 25% off for life. Applying or starting the 14-day trial does not reserve a position; successful paid-upgrade order determines the tier.

Review the complete Founding Tester terms

Test one shared endpoint workflow before expanding.

14-day free trialNo credit cardPlans from $59 per month

Start free View the product tour

Free decision tools

Turn a use case into a controlled RMM decision

Use the same evidence, cost assumptions, and rollout controls for every vendor. Each tool works in your browser and can be exported or copied for review.