Bots

Bots is a private, self-hosted monitoring dashboard for Unraid.

  • Development
  • Monitoring & Logging
  • Tools & Utilities
Bots is a private, self-hosted monitoring dashboard for Unraid. Watch product prices and stock, HTTP websites, and TCP servers with history, confirmation rules, outage and recovery alerts, DNS and TLS monitoring, and configurable notification channels. All durable data stays in /data. Bots has no built-in authentication and should not be exposed directly to the internet.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
67last commit 108 days ago
Popular
123 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
3
Open issues
0
Last commit
2026-08-05
License
MIT
Activity
stale

Checked 8 days ago - source: GitHub (DotumZane/Bots)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 2 CPU core(s).

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in the Telegram bot API address with your token Set the API address using the HTTPS format shown by Telegram, for example https://api.telegram.org/bot<YOUR_TOKEN>/... . Without the correct token and an HTTPS address, the bot will not be able to talk to Telegram. source
  • Test the token before finishing setup After entering the token, call getMe by opening https://api.telegram.org/bot<YOUR_TOKEN>/getMe in a browser. If it returns your bot's name and user ID, the token works; otherwise the bot setup is not complete. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I add Bots to Unraid?

Copy the repository's unraid/bots.xml to /boot/config/plugins/dockerMan/templates-user/my-bots.xml, then add the container from Docker. The template maps /data to /mnt/user/appdata/bots and exposes the WebUI on port 3847.

What should I back up from a Bots deployment?

Back up the /data directory because the configuration, one SQLite database, and durable state live there. Also back up /data/encryption.key with the database, since notification secrets are encrypted with that key.

How do I set up a notification channel?

Open Notifications, choose a provider, enter the credentials, save, and use Test.

Will Bots work on login-protected or CAPTCHA-protected product pages?

Bots works best on public product pages with Schema.org Product data. It does not bypass authentication, CAPTCHAs, automated-client blocking, or unusual rendering.

Where should I report bugs or security problems?

Report bugs through GitHub issues, removing passwords, tokens, email addresses, and private URLs from screenshots or logs. Report security vulnerabilities privately through GitHub Security Advisories.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads