Obot
Obot is an open-source platform that helps organizations manage, secure, and govern agent ecosystems by connecting artificial intelligence clients to models,…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- 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.
59/100 Fair
- Maintained
- 100last commit 1 day ago
- Popular
- 621,207 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 54 serious findings, 5 minor, CI, tests
Based on 4 of 5 factors.
Security check: 4 serious findings
- A private key is committed in the source code (pkg/i18n/messages/auth-providers/en.json:211)
- A private key is committed in the source code (pkg/i18n/messages/auth-providers/ja.json:211)
- A private key is committed in the source code (pkg/i18n/messages/auth-providers/ko.json:211)
- A private key is committed in the source code (pkg/i18n/messages/auth-providers/zh-CN.json:211)
Automated checks on commit eed9ba4, 27 Oct 2026. Not an audit.
- GitHub stars
- 1,207
- Open issues
- 352
- Last commit
- 2026-11-20
- Latest release
- v0.28.2
- License
- MIT
- Activity
- steady
Checked yesterday - source: GitHub (obot-platform/obot)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set a bootstrap token before first start When you start the Obot Docker container, a packaged app that runs in isolation, set OBOT_SERVER_ENABLE_AUTHENTICATION=true and OBOT_BOOTSTRAP_TOKEN to a strong secret. That token is your first sign-in credential, and without it you may have no safe way to log in. source
- Open port 8080 for the web app Use -p 8080:8080 so your computer's network port 8080, like a door number for traffic, forwards to the container's port 8080 where the web app lives. If this is missing or blocked, the browser cannot reach Obot even when the container says it is running. source
- Keep the obot-data volume safe Use -v obot-data:/data so settings and saved files live in a Docker volume, which is named storage that survives container updates. If you lose or delete that volume, your accounts, agents, and saved work disappear. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Should I run Obot with Docker or Kubernetes in production?
Docker is suitable for local testing and small-scale deployments. For production, especially enterprise settings, Kubernetes is recommended for high availability, resource management, and upgrades.
What should I configure before first starting the Obot Docker container?
Set OBOT_SERVER_ENABLE_AUTHENTICATION=true and a strong OBOT_BOOTSTRAP_TOKEN, because that token is the first sign-in credential. Expose the container's port 8080 and mount the obot-data volume at /data.
Which volume do I need to back up to preserve Obot accounts and work?
Use the obot-data Docker volume mounted at /data. It stores settings and saved files, including accounts, agents, and saved work.
Can Obot proxy MCP servers that run outside the Obot platform?
Yes. The MCP Gateway can proxy MCP servers whether they are hosted by Obot or running outside it, and can control server and tool access by user or identity-provider group.
How does Obot manage LLM provider credentials?
It can keep provider credentials in Obot instead of distributing them to individual users or clients. Clients authenticate with scoped Obot API keys, and model access can be restricted by Model Access Policies.
Answers sourced from docs.obot.ai, github.com, github.com
Community
Collected 48 days ago - public community threads