MSPZERO

Your tools. Your data. Your choice.

Free, open-source tools for MSP documentation, firewalls, infrastructure, backups, remote support and network monitoring. Use one, several or all six — there is no need to replace tools that already work for you.

Explore the tools Install your first tool
clientst0r — global dashboard
The clientst0r global dashboard in dark theme: quick actions, counts of organizations, users, assets, documents, passwords and monitors across every client, thirty-day system health and a map of client locations.
rem0te — dashboard
The rem0te operator dashboard in dark theme: a site-outage banner, tiles for devices, critical alerts, restart pending and patch compliance, the Work on next list and the client-location map.
Independent tools — not a required suite

The MSP Zero stack

Six independent tools. Use one, several or all six. They do not depend on each other.

All six are MIT licensed and self-hosted, with no paid tier. They cover six jobs, not everything an MSP runs. How each one protects your data

Free & open source · in development — not released

Next open-source project from the same developer: Office Unbound

A free, open-source workspace platform being designed to bring email, calendars, files, documents, chat, meetings and their administration together, hosted where you choose rather than in a single provider’s cloud.

  • Built on established open-source projects; the components are still being evaluated.
  • Designed for customer-hosted or MSP-hosted deployment, with Proxmox VE as the target.
  • Planned migration from Microsoft 365 and Google Workspace.

It is not one of the six MSP Zero tools. There is no public repository yet and no license has been chosen for its own code; both will be announced on its site.

Follow Office Unbound at officeunbound.com

Office Unbound — interface concept
A proposed Office Unbound home screen with today's meetings, messages needing attention, recent files and notifications, using example data. A strip across the bottom reads: proposed interface concept, not released.

What each one does

Release numbers read from the GitHub API; the oldest of these checks was on 15 Nov 2026, 05:17 UTC.

Recently changed

What’s new in the tools

The main changes since mid-October, as each project’s own changelog describes them. Read 14 November 2026.

  • clientst0r

    A hardware catalog of about 16,500 models with front and rear panel artwork, clickable ports and cable tracing through patch panels; documentation readiness scores with a repair queue; a customer portal with its own sign-in and guided request forms; pairing with an RMM from the ticket; and upgrades that install only a signed release behind a tested backup.

    Changelog

  • OPNMGR

    pfSense CE and Plus can now sit beside OPNsense in the same fleet (implemented, not yet tested on a live pfSense device); policy templates, a VPN topology map, customer reports and integrations; signed agent releases; and several security fixes, with clean installs now requiring administrator two-factor.

    Changelog

  • Depl0y

    A node maintenance preview that classes every guest before a verified, one-at-a-time evacuation; an HA-ZFS wizard; 120 days of iDRAC and iLO power and temperature history; pinned host certificates and SSH keys; per-host roles; and an option to make two-factor mandatory.

    Changelog

  • St0r

    Scheduled recovery drills that restore a canary file from the offsite copy and check it, with optional isolated Windows boot drills on Proxmox VE; signed releases; a dedicated service account; and three security releases.

    Changelog

  • rem0te

    Now does part of an RMM's job: monitoring and alerts, inventory, patch status, staged Windows updates, approved scripts and winget installs run only from signed plans, read-only Linux and macOS agents, and chat. The project marks much of the Windows action side as not yet run on a real computer.

    Changelog

  • m0nitor

    Device profiles and syslog parsers for 20+ firewall, router and switch vendors (only OPNsense verified on hardware), IPFIX and sFlow collection, incidents, "What changed?" comparisons, plain-English search and a per-firewall onboarding test.

    Changelog
See it in action

Real screens, real work

From each project’s own repository, running its demo data. Select one to enlarge it.

Trace a cable end to end Follow one connection from a switch port through the patch panel and the wall jack to the workstation, each hop documented.
See why a finding matters Related findings on one server become a single incident, with what happened, the confidence and the next steps.
Plan a failover before enabling it Set ZFS replication of a VM to a second node and read every change the wizard will make before it makes any.
Who builds it

Built from actual MSP work.

MSP Zero was created by Dewey Straughn after 24 years operating an MSP. The projects grew out of ordinary problems involving documentation, firewalls, infrastructure, backups and remote support.

Why MSP Zero exists

1994
Started working in IT
1999
Co-founded an MSP
24 yrs
Ran it, including our own data center
2023
Sold the business
Why open source

This isn’t a crusade against paid software.

If a commercial product works well for you and earns its cost, keep using it. MSP Zero is another option.

  • Free is the licence, not the sales pitch.

    Being free doesn’t make them better than what you pay for, and they don’t match mature commercial platforms feature for feature.

  • Open source means you don’t have to wonder what’s inside.

    These tools hold credentials, firewall configs and remote access. You can read the code that does it, or have someone you trust read it.

  • Don’t just trust it. Verify it.

    Open source is not automatically secure. It means you can check: review the source, scan its dependencies, watch what it sends over the network.

  • The project doesn’t disappear if we do.

    Your install keeps running, your data stays in your database, and the MIT-licensed code can be maintained by anyone.

Why open source, in full — and how to verify it

Common questions

What do I need to run a project?

A small Linux server or VM each, in most cases, plus whatever the tool manages: UrBackup for St0r, a RustDesk server for rem0te, OPNsense (or, untested, pfSense) for OPNMGR, Proxmox VE for Depl0y, a firewall or router sending NetFlow, IPFIX or sFlow and syslog for m0nitor (OPNsense is the verified one). Each project page has a First deployment section with the details.

How do I get help?

Bugs and questions go to each project's GitHub issue tracker, in the open. The guides cover choosing a first tool and running it well.

Getting started

Run it yourself, with help in the open.

Self-host

Free software. Your infrastructure.

Pick one tool, read its first-deployment notes, and install it on a server of your own. The software costs nothing; the server and your time still do.

Install your first tool
Free help

Stuck? Ask in the open.

Every project has its own GitHub issue tracker for bugs and questions, and the guides cover choosing a first tool and running it well. Nothing here is a paid tier, and nobody gets faster answers for paying.

Read the guides Or send a question
Feedback & sharing

Help MSP Zero grow

Find MSP Zero useful? Help spread the word, tell us what you think, or suggest something we could do better. You don’t need to contribute money to make a difference.

See all six ways to help

  • Rate this site

    How useful is this website to you? Private, and no account needed.

    Rate this site

  • Share with another MSP

    Copy the link or an introduction, or share it on Facebook, LinkedIn or by email.

    Share MSP Zero

  • Suggest an improvement

    A feature, a new tool, an integration, or something broken? Tell us privately.

    Request a feature

  • Follow MSP Reboot

    Connect with MSP Reboot on Facebook for updates and conversations with other MSPs.

    Follow MSP Reboot on Facebook