MSPZERO
Help MSP Zero grow

Help MSP Zero grow Keep powerful MSP tools free

MSP Zero was created with a simple mission: give managed service providers and IT professionals access to powerful tools without expensive licensing, subscriptions, or unnecessary restrictions.

We believe great software should be accessible to everyone. Whether you’re an MSP owner, technician, developer, or simply someone who believes in open-source software, you can help MSP Zero grow.

You don’t have to contribute money. Sharing the project, reporting bugs, suggesting improvements, and helping others discover our tools are just as valuable.

Six ways to help Share MSP Zero
Six ways you can help

Pick whatever fits your time

Most take a minute. None needs an account on this site.

  1. Spread the word

    Facebook, LinkedIn, Reddit, email, or just the link — for MSP Zero or one tool.

    Share

  2. Contribute on GitHub

    Star, fork, report bugs, send code, improve docs, review security, test releases.

    Project links

  3. Suggest features or new tools

    New tools, features, integrations, usability fixes — and vote on others’ ideas.

    Suggest an idea

  4. Become a beta tester

    Run new tools and versions in a lab, check compatibility, and tell us what broke.

    Testing

  5. Support development

    Entirely optional. It helps cover development, hosting and infrastructure.

    Sponsorship

  6. Contribute resources or expertise

    Development, documentation, security audits, translation, hardware, hosting, tutorials.

    Offer help
Spread the word

Know another MSP paying too much for software?

Tell them about MSP Zero. Every share helps us reach more IT professionals — there is no advertising budget, so most people find a tool like this because somebody they trust mentioned it.

Share one tool

Nothing is sent anywhere unless you click: each button opens that service’s own share screen, your device’s share menu, or your mail app. On Reddit and in groups, share where it is relevant and follow the community’s rules.

Beta testing

Become a beta tester

Testers run new tools, upcoming features and integrations in a lab — never on a client’s production system — and report what broke, with versions and steps. Unusual hardware, older firewalls and other hypervisors are the most useful, because that is where the surprises are.

  • Test new tools and upcoming features
  • Validate compatibility on your platforms
  • Report bugs and usability problems
  • Try integrations with what you already run
Sign up to test

Name or alias, role and what you can test are optional. An email is needed for our reply, and only with your consent.

Resources and expertise

Contribute resources or expertise

Development and documentation
Code, install notes for a platform the docs miss, tutorials. Pull requests are welcome; or offer it here first.
Security auditing
Read the code and the security policy; report a vulnerability privately as the policy says.
Testing environments, hardware, hosting
Spare firewalls and switches, a hypervisor host, or infrastructure new versions can run on.
Translation
Not every project is set up for it yet, so tell us the language and the tool first.
Offer resources or expertise
Community impact

What the community has built so far

Read from GitHub’s public API once a day. Nothing is estimated, and anything GitHub could not tell us is left out rather than guessed.

  • 6Public projects, all MIT licensed
  • 182GitHub stars
  • 9Contributor accounts
  • 289Releases published
  • 146Issues resolved

Project figures read on 31 Oct 2026, 17:06 UTC. Issues resolved: issues GitHub search finds closed as completed, read 31 Oct 2026.

Figures per project
GitHub figures per project
Project Stars Forks Contributors Releases Open issues Latest release Last commit
clientst0r 78 20 2 64 1 v3.17.558, 15 Sep 2026 21 Oct 2026
OPNMGR 30 1 2 20 0 v3.67.0, 17 Sep 2026 29 Oct 2026
Depl0y 34 4 1 65 0 v2.2.107, 16 Oct 2026 16 Oct 2026
St0r 31 4 1 86 0 v3.2.122, 21 Oct 2026 21 Oct 2026
rem0te 8 1 2 51 0 v0.19.6, 31 Oct 2026 31 Oct 2026
m0nitor 1 0 1 3 0 v1.23, 31 Oct 2026 31 Oct 2026

Stars and forks are per repository, so somebody who starred two projects counts twice. Contributors are the GitHub accounts GitHub credits with commits; help that is not a commit is not in that number, which is why recognition exists. Open issues exclude pull requests.

Contribute on GitHub

Projects that need contributions

Each project lives in its own public repository. These go straight to the right place in each one.

Bugs: say what you ran, which version, what you expected and what happened; leave out client data and credentials. Security: never in a public issue — follow the project’s security policy.

Community ideas

Ideas, votes and the roadmap

Vote for what you want built next on the public roadmap, or with a 👍 on GitHub. Every request sent from this site is read by a person before it is published.

Votes come from confirmed email addresses, one per person; GitHub 👍 are shown beside them. Community votes tell us what matters most to MSPs. Development priorities also consider security, impact, technical feasibility, and available resources.

Open the roadmap Request a feature
  1. 0voters

    Which FOSS projects should I focus on?

    Poll MSP Zero

    Answer

Most-voted requests per project: clientst0r · OPNMGR · Depl0y · St0r · rem0te · m0nitor.

Public roadmap

Only what each project publishes in its own repository, shortened. Plans change; the linked source is the authority, and none of it is a promise.

  • clientst0r

    In development

    • Reliability and customer-boundary hardening
      Making existing features hold up in use before new ones are built on them.
    • Technician workspace
      Day-to-day ticket work in fewer steps, without losing work or replying over someone else.
    • Documentation readiness and lifecycle
      Know what is missing, why it matters and who owns the fix.
    • Guided customer service requests
      Collect what technicians need up front and show customers where things stand.

    Planned

    Nothing listed.

    Released

    Latest release v3.17.558, 15 Sep 2026

    • "Help Us Grow" call to action v3.17.586
      Sharing the project with another person made easy from inside the app.
    • Advanced project management v3.17.548–555
      Templates, budgets, profitability, task-to-ticket, timelines and billing.
    • Network configuration backup v3.17.544–547
      Versioned, diffable device configuration with drift alerts.

    From the project’s roadmap, read 31 Oct 2026.

  • OPNMGR

    No roadmap document in the repository; planned work is tracked as open enhancement issues (0). Latest release: v3.67.0, 17 Sep 2026.

  • Depl0y

    No roadmap document in the repository; planned work is tracked as open enhancement issues (0). Latest release: v2.2.107, 16 Oct 2026.

  • St0r

    No roadmap document in the repository; planned work is tracked as open enhancement issues (0). Latest release: v3.2.122, 21 Oct 2026.

  • rem0te

    No roadmap document in the repository; planned work is tracked as open enhancement issues (0). Latest release: v0.19.6, 31 Oct 2026.

  • m0nitor

    In development

    Nothing listed.

    Planned

    • Configuration-change history
      From OPNsense audit events, with an authentication events view.
    • Server page DNS card
      Transport and names, with correlation confidence.
    • Optional adapters
      LibreNMS for interface counters, NetBox for inventory and prefixes.
    • External exposure checks
      Certificate expiry for published services; only against your own addresses, and opt-in.
    • Health notifications
      Off by default, once destinations are tested.
    • Installer script and restore drill
      For a fresh host, with a restore drill on a fresh VM.

    Released

    Latest release v1.23, 31 Oct 2026

    Not commitments; ordered roughly by value. From the project’s roadmap, read 31 Oct 2026.

Community recognition

Thank you

Code, documentation, testing, community help, resources and sponsorship — listed only for people who asked to be, under the name they chose, for what they actually did.

Nobody has asked to be listed yet. To be credited after you help, tick “credit me publicly” on the volunteer form, or ask in your pull request. You can ask to be removed at any time.

Code contributors are also credited by GitHub itself: clientst0r, OPNMGR, Depl0y, St0r, rem0te, m0nitor.

Together, we can keep great MSP tools free

MSP Zero is free, open, and community-driven. You don’t need to donate money to make a difference. Your ideas, feedback, code, testing, and support help make these tools better for everyone.

Share MSP Zero MSP Zero on GitHub Suggest an idea

About this website: rate it or tell us what is unclear or broken. Follow MSP Reboot on Facebook.