Skip to content

Every device, one agent.

Endpoints is the device management system in The One Stack, the platform MSPs run their whole business on. It enrolls, monitors, patches and connects to every client device with one agent, for the technicians who keep those devices working. It takes the place of your RMM, remote-control tool, documentation platform and password vault.

One agent on Windows, macOS and Linux monitors, patches, scripts and connects. The same install carries security, backup and DNS filtering, switched on per client without another rollout.

Replaces: your RMM, remote-control tool, documentation platform and password vault.

Harbor ITMeridian LawSample data

Endpoints

All clients
DevicesOne agent each
MER-FS01Windows ServerAlert cleared
MER-WS14Windows 11Patched
CAS-MBP-07macOSPatched
APX-SQL-02Windows ServerReboot pending
NWD-LNX-01UbuntuPatched
MER-FS01 · Meridian LawT-4821
CPU
38%
Memory
61%
Disk
71%
On this agent
MonitoringPatchingRemote controlDetectionDNS filteringBackup

Illustrative product view with sample data.

The job, start to finish.

The work Endpoints carries, in the order it happens, and where it hands off.

  1. 01

    Enroll

    Install one agent on Windows, macOS or Linux with a token scoped to the client. The device appears under that client and starts reporting.

  2. 02

    Monitor

    Each check-in is measured against the rules you set for device health and performance, by client or by device.

  3. 03

    Patch

    Operating system and third-party updates move from pending to approved to installed, by policy and inside the maintenance window you choose.

  4. 04

    Alert

    A rule that trips raises an alert with a severity. Maintenance windows hold alerts during scheduled work, and a condition that returns reopens the same alert.

  5. 05

    Ticket

    High and critical alerts open a ticket in the service desk with the device attached, so the technician starts with the context.

  6. 06

    Fix

    A script, an automation or a remote session (Connect) fixes the device. THEO runs the fix itself when a runbook covers it.

  7. 07

    Document

    The device, its configuration, the written procedure and the credentials sit on the client record, where the next technician finds them.

Inside Endpoints.

A few of its screens. Every module page shows its own.

The device page

Every managed device has one page: its health, its patch standing, its live load and its open alerts. A high or critical alert shows the ticket it opened, so the device and the work stay together.

Monitoring and alerting

Illustration, sample data. One device with its health, the reasons it needs attention and the ticket its open alert created.

The fix, on the record

A script run is a job. It keeps the steps, the output and who ran it, whether that was a technician or THEO working from a runbook that covers the fix.

Scripts and automation

Illustration, sample data. Every script run is a job with its steps, its output and the name of who ran it.

The same device, documented

The server that raised the alert is also a configuration item on the client record, with its hardware details, its documents and its vault entries one click away.

Assets and documentation

Illustration, sample data. One server on the client record, with its details, its documents and its credentials linked.

What it hands to the other systems.

An alert opens a ticket

A high or critical alert opens a ticket in the service desk with the device attached. The alert shows its ticket, and the ticket shows the device’s live health.

Service desk

A network or host alert pages on-call

Alert rules for network devices and virtualization hosts open a ticket and page the person on call.

On-call

The same agent carries detection and response

Switch on Defend for a client and the EDR sensor in the agent already on the device starts reporting detections. Response actions wait for a technician to approve them.

Detection and response

DNS filtering switches on without a rollout

DNS filtering (Shield) is a module of the same agent. Turn it on for a client or a device and there is nothing else to install.

DNS filtering

Endpoint backup uses the install you already have

Endpoint backup is a module of the same agent, switched on by client or by device.

Endpoints

A call about a device can end in a fix

A client calls about a device and THEO takes the call. When a runbook covers the problem, THEO runs the fix through the agent. Outside a runbook it hands the call to your team.

AI receptionist

Every device sits under one company record

Devices, documentation, credentials and virtualization hosts all sit under the same company record your sales and account work uses. Nobody keeps a second client list.

Sales and accounts

What changes for you.

For owners

Your RMM, remote-control tool, documentation platform and password vault become one platform with one agent. Security, DNS filtering and backup switch on per client from the install you already have, so adding a service does not mean another rollout.

MSP owners

For technicians

The alert, the ticket, the device, its documentation and its credentials are in one place. You open a remote session from the ticket, and scripts, sessions and credential use are all audited.

Service managers and technicians

For co-managed IT

The client’s internal IT team works on its own company’s devices and alerts inside the scope you grant. Your team and theirs look at the same device record, and access is gated and audited.

Co-managed IT

Proof slot

A customer running Endpoints on The One Stack

A named MSP, the tools it retired for this system, and a quote approved in writing by the customer.

Switching to it.

What imports

Integrate imports devices from NinjaOne and Datto RMM, configurations from ConnectWise and Autotask, configurations, flexible assets, passwords, domains and certificates from IT Glue, assets, passwords and articles from Hudu, hardware from Snipe-IT, and CSV files. Each import matches records to the client they belong to.

Bring your data

What runs side by side

Install the agent beside your current RMM and security tools. It recognizes them, names them on the device page and leaves them alone. Where another tool runs Windows Update, the device reads Managed elsewhere until you choose Take over patching. Switch modules on one at a time, one client at a time.

Run side by side

What you turn off

Once a client is running on the agent, remove the old agent as a separate, deliberate step. Then let your RMM, remote-control tool, documentation platform and password vault lapse as each renewal comes up.

How switching works

Questions

Questions about Endpoints

Does Endpoints replace my RMM?

Yes. It monitors, patches, scripts and connects to Windows, macOS and Linux devices with one agent. It also takes the place of your remote-control tool, documentation platform and password vault.

Which operating systems does the agent run on?

Windows, macOS and Linux. Chromebooks in school device programs are tracked through the school’s Google Workspace admin instead of the agent.

Can it run beside my current RMM?

Yes. The agent installs beside your current RMM and security tools, recognizes them and leaves them alone. You move one client at a time and remove the old agent when you choose.

Is remote control included?

Yes. Remote control (Connect) is part of Endpoints and uses the same agent, so it is included. The pricing page shows how the platform is charged.

Where do documentation and passwords live?

On the client record. Assets and documentation (CMDB) holds configurations, runbooks and SOPs. The password vault (Vault) holds encrypted credentials with checkout, sharing rules and an audit trail.

Do I need a second agent for security or backup?

No. The same agent carries Defend, DNS filtering (Shield) and endpoint backup. You switch each one on by client or by device.

Start

Run on One.

Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.