head to head · open source

Uptime Kuma vs Microsoft365DSC

Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. Microsoft365DSC has 2,440 stars, 682 forks, 66 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 3,719% (93,190 vs 2,440 stars). Uptime Kuma is written in JavaScript under MIT; Microsoft365DSC is written in PowerShell under MIT. Uptime Kuma has attracted 9% as many forks as stars, Microsoft365DSC 28%. Uptime Kuma was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (monitoring), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Uptime Kuma ★ 93K Microsoft365DSC ★ 2.4K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

Uptime Kuma Microsoft365DSC
GitHub stars ★ 93K ★ 2.4K
License MIT MIT
Written in JavaScript PowerShell
Last push 2026-11-02 2026-11-02
Forks ⑂ 8.7K ⑂ 682
Self-hosting Yes Yes
Data ownership Your server Your server

pick Uptime Kuma if

  • You weight community size — 93K stars and counting
  • You want the MIT license terms
  • Your stack matches JavaScript
  • You value the larger contributor base for long-term maintenance

full Uptime Kuma profile →

pick Microsoft365DSC if

  • You want the Microsoft365DSC feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches PowerShell
  • You evaluated both and Microsoft365DSC fits your workflow better

full Microsoft365DSC profile →

About Uptime Kuma

Uptime Kuma Uptime Kuma is an easy to use self hosted monitoring tool. 🥔 Live Demo Try it! Demo Server (Location: Frankfurt Germany): It is a temporary live demo, all data will be deleted after 10 minutes. Sponsored by Uptime Kuma Sponsors. ⭐ Features Monitoring uptime for HTTP(s) / TCP / HTTP(s) Keyword / HTTP(s) Json Query / Websocket / Ping / DNS Record / Push / Steam Game Server / Docker Containers Fancy, Reactive, Fast UI/UX Notifications via Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP), and 90+ notification services, click here for the full list 20 second intervals Multi Languages Multiple…

read the full Uptime Kuma overview →

About Microsoft365DSC

Microsoft365DSC This module allows organizations to automate the deployment, configuration, reporting and monitoring of Microsoft 365 Tenants via PowerShell Desired State Configuration. The compiled configuration needs to be executed from an agent's Local Configuration Manager (LCM) (machine or container) which can communicate back remotely to Microsoft 365 via remote API calls (therefore requires internet connectivity) For information on how to get started, additional documentation or additional resources, please navigate to the official web site at Microsoft365DSC.com and check out the official YouTube channel…

read the full Microsoft365DSC overview →

More in Infrastructure & Operations

Related comparisons

More Monitoring & Observability projects

Compare either of these against the rest of the Monitoring & Observability field.

Frequently asked questions

Is Uptime Kuma or Microsoft365DSC more popular?

Uptime Kuma has 93,190 GitHub stars and Microsoft365DSC has 2,440. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and Microsoft365DSC free?

Both are open source. Uptime Kuma is licensed under MIT and Microsoft365DSC under MIT. Neither carries a licence fee.

What is the difference between Uptime Kuma and Microsoft365DSC?

Uptime Kuma is written in JavaScript and Microsoft365DSC in PowerShell. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Uptime Kuma or Microsoft365DSC?

Choose Uptime Kuma if you want the larger community (93,190 stars) or its MIT licence terms. Choose Microsoft365DSC if its feature set, stack or MIT licence fits better. Both are self-hostable.