Skip to content
DevUtils Online

AI Agents

gemini-cli vs mem0

gemini-cli leads by 2.2 · narrow

A · leads

gemini-cli

97.9

108,897 stars · Apache-2.0

B

mem0

95.7

69,113 stars · Apache-2.0

gemini-cli versus mem0 is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. gemini-cli is written mainly in TypeScript; mem0 is written mainly in Python. The composite score is 97.9 for gemini-cli and 95.7 for mem0.

gemini-cli has 108,897 GitHub stars to mem0's 69,113, a gap of 39,784 (1.58×). Forks are 14,956 for gemini-cli and 8,226 for mem0. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 94.

Push history: gemini-cli was last pushed on 17 November 2026 (0 days ago), and mem0 was last pushed on 17 November 2026 (0 days ago). Open issues stand at 739 for gemini-cli (0.007 per star) and 963 for mem0 (0.014 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Both gemini-cli and mem0 are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In AI Agents, both gemini-cli (108,897 stars) and mem0 (69,113 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: gemini-cli is open source, mem0 is open source.

gemini-cli is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 6 points (100 vs 94), and the tightest is self-hosting at 0 points (100 vs 100).

gemini-cli finishes ahead at 97.9 against mem0 at 95.7, a 2.2 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

gemini-cli versus mem0 metrics
Signal gemini-cli mem0
GitHub stars 108,897 69,113
Forks 14,956 8,226
Open issues 739 963
Adoption 100 96
Activity 100 100
Community 100 94
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 97.9 95.7

mem0

The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, gemini-cli or mem0?

gemini-cli has more GitHub stars: 108,897 versus 69,113 for mem0. The gap is 39,784 stars.

Which was updated more recently, gemini-cli or mem0?

Both were last pushed on 17 November 2026.

Can I self-host both gemini-cli and mem0?

Yes. This catalog marks both gemini-cli and mem0 as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, gemini-cli or mem0?

gemini-cli 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the gemini-cli vs mem0 score?

gemini-cli scores 97.9 and mem0 scores 95.7. This page calls that a narrow lead for gemini-cli.

Related comparisons