A
mem0
94.1
69,113 stars · Apache-2.0
AI Agents
Open WebUI leads by 5.0 · narrow
A
94.1
69,113 stars · Apache-2.0
B · leads
99.1
158,922 stars · MIT
mem0 versus Open WebUI is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. mem0 is written mainly in Python; Open WebUI is written mainly in Svelte. The composite score is 94.1 for mem0 and 99.1 for Open WebUI.
Open WebUI has 158,922 GitHub stars to mem0's 69,113, a gap of 89,809 (2.30×). Forks are 8,226 for mem0 and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 90 versus 100.
Push history: mem0 was last pushed on 17 November 2026 (0 days ago), and Open WebUI was last pushed on 17 November 2026 (0 days ago). Open issues stand at 963 for mem0 (0.014 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
mem0 is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Open WebUI is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for mem0 and 96 for Open WebUI. This is a procurement signal, not legal advice.
In AI Agents, both mem0 (69,113 stars) and Open WebUI (158,922 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: mem0 is open source, Open WebUI is open source.
Open WebUI is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 12 points (84 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against mem0 at 94.1, a 5.0 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | mem0 | Open WebUI |
|---|---|---|
| GitHub stars | 69,113 | 158,922 |
| Forks | 8,226 | 23,097 |
| Open issues | 963 | 208 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.1 | 99.1 |
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
Open WebUI is a self-hosted chat interface for local and remote language models, including Ollama. It adds users, documents, and tools around the model endpoint.
Open WebUI has more GitHub stars: 158,922 versus 69,113 for mem0. The gap is 89,809 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both mem0 and Open WebUI as self-hostable. Confirm each project's deploy docs before you plan a migration.
mem0 is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Open WebUI is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Open WebUI scores 99.1 and mem0 scores 94.1. This page calls that a narrow lead for Open WebUI.