trio.so
For MSPs and MSSPs

MDM for MSPs that keeps every client in its own lane

One trio.so console for every client you manage. Each client approves your access and keeps its own workspace, with its own Apple, Microsoft and Google accounts. Your team enrolls, patches and checks compliance in each one, while every client's devices, users and policies stay separate.

  • Windows
  • macOS
  • Linux
  • iOS/iPadOS
  • Android
Rated 4.8 on G2
trio.so MSP console showing the Customers list: each customer's relationship status, next step, workspaces and account manager.

Most device tools were built for one company. You look after twenty.

Every new client brings its own Apple Business account, its own Microsoft tenant and its own Android Enterprise. Most MDMs force a choice. Either you run a separate console per client and log in twenty times a day, or you pile every client into one console and hope nobody pushes the wrong policy to the wrong fleet.

trio.so takes neither route. It is one console for all your clients: your team signs in once and works across every client, while each client's devices, users and policies stay separate.

Management accounts

Each client's accounts stay theirs

Each client links its own workspaces to you when it accepts your invitation. Inside each workspace, the client's Apple organization, Microsoft tenant and Android Enterprise become management accounts, and each one keeps a hard boundary around its devices, profiles and assignments.

The right account, picked for you

When a device can only belong to one client account, trio.so binds it automatically. When several could fit, trio.so asks once. When none fits, it stops and tells you what is missing instead of guessing.

Policies that cannot cross over

Enrollment profiles and assignment targets carry the account they belong to. A profile made for one client's tenant cannot be applied to another's.

Bulk jobs that stay inside one client

Enroll five hundred laptops at once and trio.so splits the job by account. A single run never spans two clients.

Your team, scoped by role

Each technician works only on the clients they are named on, with View or Manage access, and you can set when that access ends. Provider roles decide what each person can see and change in your MSP console.

A customer record in the trio.so MSP console listing the customer's workspaces and the technicians with access to each.
Client onboarding

Onboard each client the way their devices already expect

trio.so works with the enrollment programs your clients already pay for, so new hardware can ship straight to the user and arrive managed.

Apple

Automated Device Enrollment through Apple Business, account driven enrollment for personal devices, and Apple Configurator for devices you set up by hand.

Windows

Windows Autopilot, automatic enrollment through Microsoft Entra, and bulk enrollment with a provisioning package, so new PCs enroll without hands-on setup.

Android

Zero-touch enrollment, Samsung Knox, QR code and work profiles for personal phones.

Linux

The trio.so agent, managed from the same console as everything else.

Network and certificates on day one

Wi-Fi (WPA2 and WPA3 Personal on Windows and Apple devices) and certificate policies (PKCS#12, SCEP and trusted root on Apple devices and Windows) arrive with enrollment, so each client's devices join that client's network on first boot.

Automated Device Enrollment settings in a client's trio.so workspace for company iPhones, iPads and Macs from Apple Business Manager.
Patch and vulnerability

Patch what is actually dangerous first

A list of four thousand CVEs tells you nothing. trio.so scores every finding from 0 to 100 using CVSS, the likelihood of exploitation (EPSS), CISA's list of known exploited vulnerabilities, how critical the device is and how exposed it is. Anything already being exploited goes straight to the top.

One overview per client

Open findings, what is critical now, what has passed its deadline, and which devices keep coming back.

A decision for every finding

Start remediation, mitigate, accept the risk or mark it a false positive. Accepting risk needs its own permission, so it is never a quiet click.

Your own packages, checked first

Upload MSI, PKG or DMG installers. Each one is scanned with VirusTotal and approved before it reaches a client device.

OS updates and third-party fixes

trio.so handles OS updates through Auto Patch policies on Windows, macOS, iOS/iPadOS and Android, and third-party fixes through remediation plans, and shows the result for each device. On Linux, fixes come through the device's package manager.

Patch and vulnerability findings in a client's trio.so workspace with severity, status, CVSS, EPSS and KEV for each CVE.
Compliance

Evidence each client's auditor can read

trio.so checks every device against the controls that matter: disk encryption, firewall, screen lock, anti-malware and patch level. Each device shows as compliant, at risk or non-compliant, so the question "what do we fix first" has an answer.

Built on recognised benchmarks

Controls map to CIS benchmarks and to frameworks such as SOC 2, ISO 27001, NIST 800-171 and GDPR.

Status that stays current

Each device's compliance status updates as it checks in, so a client's view shows today's fleet, not last month's.

Export it, hand it over

Evidence and the audit trail export to CSV or Excel, one client at a time, ready for their auditor or their insurer.

Endpoint compliance findings in a client's trio.so workspace, each failing control mapped to frameworks such as CIS and SOC 2.

Bring your messiest client to the demo

Tell us how many tenants, which operating systems and which enrollment programs. We will walk through that client in trio.so.

Remote operations

Fix it from your desk, not from their office

Most tickets do not need a site visit. They need a screen, a shell or a single command.

A live remote PowerShell terminal session to a client's Windows laptop in trio.so Remote Operations.

Remote Desktop

Take over a Windows, Mac or Linux screen with the user.

Terminal

Open a shell on Windows, macOS or Linux, and see services, processes and scripts on the device.

Remote commands

Lock, locate, restart or wipe phones and tablets over the air. A selective wipe removes only company data from a personal device.

LockLocateRestartWipeSelective wipe

Remote Desktop, Terminal and remote commands come with every plan.

Automations

Let the repeat tickets handle themselves

With trio.so automations, you pick a ready-made fix, choose the devices, and see exactly which ones it will touch before anything runs.

Automation scenarios in a client's trio.so workspace, each with its safety level, run mode and device counts.
Templates include
Restart the management agentComplete a pending restartRestore the firewall baselineRenew a device certificateReinstall a required appRecover a kiosk app
Only approved templates, never free scripts.
Risky changes need a second person to approve.
A run counts as done only when trio.so has checked the device is actually fixed.

Bring your own AI

Connect Claude, Microsoft 365 Copilot, GitHub Copilot, Cursor or Codex through the Trio MCP server. A connection in a client's workspace answers questions about that client's devices in plain language. The connection in your MSP console is read-only and covers your own records: customers, access and the activity log. You create and revoke every connection in the console.

The Trio MCP page in trio.so listing AI clients such as Claude, Microsoft 365 Copilot and Codex that can connect to the workspace.
For MSSPs

The device layer under your security service

Your SOC watches for threats. trio.so makes sure each client's devices are encrypted, patched and configured the way your service promises, and gives you the records to prove it.

findings

Risk scored vulnerability findings per client, with the deadlines you agreed.

reports

Scheduled reports per client, so device posture reaches your analysts before the client asks.

evidence

Device posture and audit trails your analysts can export into the reports you already send.

trio.so sits beside your detection and response tools. It does not replace them.

Getting started

How MSPs start with trio.so

Sign up and apply

Create your trio.so account, then apply for provider access in Settings. Tell us which services you offer: IT management, security operations or both.

We review it with you

trio.so reviews your request, and a short call agrees pricing for your client mix. MSP pricing is set per partner, and there is no minimum device count.

Invite your first client

Send the client's owner a request from your MSP console. Once they approve, your team works in their workspace and enrolls their devices.

Need to keep data in your own environment? An on-premises or customer-hosted deployment can be scoped with our product team when a client needs it.

Want to resell, distribute or refer trio.so instead? See the partner program →

Questions MSPs ask us

Yes. trio.so manages all your clients from one MSP console. Each client accepts your invitation and keeps its own workspace, so its devices, users and policies stay separate, and profiles, assignments and bulk jobs stay inside that one client.

An RMM monitors devices and runs scripts against them. An MDM enrolls devices and enforces how they are configured, secured and patched, using the management channels Apple, Microsoft and Google build into their operating systems. Many MSPs run both. trio.so covers enrollment, policy, patching, compliance and remote support, and sits next to the RMM you already use.

Each client has its own workspace, and inside it each Apple organization, Microsoft tenant and Android Enterprise is its own management account. Profiles, assignments and bulk jobs are bound to one account, so a policy built for one client cannot be applied to another, and a bulk enrollment never spans two clients. Your technicians can only open the clients they are named on.

Yes. The client's existing Apple Business account, Microsoft Entra tenant or Android Enterprise connects to that client's trio.so workspace. Devices the client has already bought through those programs can then enroll at first boot.

Yes. Devices leave the old MDM and enroll in trio.so through the client's own Apple, Microsoft or Android Enterprise programs, device by device. Book a demo and our team will help you plan a larger move.

MSP pricing is agreed per partner, based on your client base and device count. There is no minimum number of devices. Sign up and apply for provider access, or book a demo to get a quote.

When a client needs it, an on-premises or customer-hosted deployment can be scoped with our product team on a call.

Yes. Provider roles decide what each person on your team can do in your MSP console, and each technician gets View or Manage access only to the clients they are named on.

trio.so sits beside your RMM rather than replacing it. Alerts can go to Slack or Microsoft Teams channels, and device events and compliance alerts can stream to Splunk.

Windows, macOS, Linux, iOS/iPadOS and Android, from one console. ChromeOS is coming soon.

Run every client from one console, without mixing them up

Bring one real client to a demo and see how it looks in trio.so.