Comparison
memory-os vs kronotop
Verdict
Pick memory-os if memory-OS is a memory operating system tailored for Hermes Agent, focusing on local-first, self-hosted persistent storage and seamless integration with any LLM provider using Qdrant as the vector database; pick kronotop if kronotop is a distributed transactional document database that utilizes FoundationDB for ACID transactions and provides vector search.
Markdown twin · memory-os alternatives · kronotop alternatives
GraphCanon updated Sep 20, 2026
13views this month
vs
Trust & integrity
| Signal | memory-os | kronotop |
|---|---|---|
| Maintenance | Slowing (101d since push) As of Sep 20, 2026 · github_public_v1 | Very active (0d since push) As of Sep 20, 2026 · github_public_v1 |
| Provenance | Not a fork · Personal account As of Sep 20, 2026 · github_public_v1 | Not a fork · Organization account As of Sep 20, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 11, 2026 · osv@v1 | No lockfile (source not queried) As of Jul 11, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- memory-os
- A 7-layer memory operating system for Hermes Agent with persistent memory and context injection
- kronotop
- Distributed transactional document database backed by FoundationDB
Stars
- memory-os
- 1.4k
- kronotop
- 309
Forks
- memory-os
- 128
- kronotop
- 12
Open issues
- memory-os
- 9
- kronotop
- 3
Language
- memory-os
- Python
- kronotop
- Java
Adopt for
- memory-os
- Memory-OS is a memory operating system tailored for Hermes Agent, focusing on local-first, self-hosted persistent storage and seamless integration with any LLM provider using Qdrant as the vector database.
- kronotop
- Kronotop is a distributed transactional document database that utilizes FoundationDB for ACID transactions and provides vector search.
Persona
- memory-os
- -
- kronotop
- -
Runtime
- memory-os
- -
- kronotop
- -
License
- memory-os
- MIT
- kronotop
- Apache-2.0
Last pushed
- memory-os
- Jun 10, 2026
- kronotop
- Sep 19, 2026
Categories
- memory-os
- AI Agents, Vector Databases
- kronotop
- Vector Databases
Trust and health
Maintenance
- memory-os
- Slowing (36%)
- kronotop
- Very active (96%)
Days since push
- memory-os
- 101d
- kronotop
- 0d
Open issues (now)
- memory-os
- 9
- kronotop
- 3
Stars delta
- memory-os
- +75 (30d)
- kronotop
- +7 (30d)
Open issues delta
- memory-os
- +2 (30d)
- kronotop
- +1 (30d)
Owner type
- memory-os
- User
- kronotop
- Organization
Full report
- memory-os
- Trust report
- kronotop
- Trust report
Choose memory-os if…
- memory-os is primarily Python; kronotop is Java.
- License: memory-os is MIT, kronotop is Apache-2.0.
- Tags unique to memory-os: context-injection, docker, ground-truth, hermes-agent.
- Also covers AI Agents.
- - You are working with Hermes Agent and require a sophisticated memory management solution that operates locally.
When NOT to use memory-os
- - If you are looking for a completely cloud-managed service without any local setup or maintenance needs.
- - Your use case does not align with Hermes Agent; Memory-OS is specifically designed to complement this agent's functions and won't provide the same benefits when used independently.
Choose kronotop if…
- kronotop is primarily Java; memory-os is Python.
- License: kronotop is Apache-2.0, memory-os is MIT.
- Tags unique to kronotop: acid, ai-agents, database, distributed-database.
- When needing a multi-model database with support for JSON documents and key-value storage alongside transactional capabilities.
When NOT to use kronotop
- If the project does not require vector search capabilities or ACID transactions, as these features may introduce unnecessary overhead.
- When a simpler database model without the complexity of setting up and operating on top of FoundationDB would suffice for the application needs.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (ClaudioDrews/memory-os) · observed Sep 20, 2026
- GitHub forks (ClaudioDrews/memory-os) · observed Sep 20, 2026
- Last push (ClaudioDrews/memory-os) · observed Jun 10, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 12, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (kronotop/kronotop) · observed Sep 20, 2026
- GitHub forks (kronotop/kronotop) · observed Sep 20, 2026
- Last push (kronotop/kronotop) · observed Sep 19, 2026
- License file (Apache-2.0) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: memory-os 1.4k · kronotop 309 (synced Sep 20, 2026).
Common questions
- What is the difference between memory-os and kronotop?
- memory-os: A 7-layer memory operating system for Hermes Agent with persistent memory and context injection. kronotop: Distributed transactional document database backed by FoundationDB. See the comparison table for live GitHub stats and shared categories.
- When should I choose memory-os over kronotop?
- Choose memory-os over kronotop when memory-os is primarily Python; kronotop is Java; License: memory-os is MIT, kronotop is Apache-2.0; Tags unique to memory-os: context-injection, docker, ground-truth, hermes-agent; Also covers AI Agents; - You are working with Hermes Agent and require a sophisticated memory management solution that operates locally.
- When should I choose kronotop over memory-os?
- Choose kronotop over memory-os when kronotop is primarily Java; memory-os is Python; License: kronotop is Apache-2.0, memory-os is MIT; Tags unique to kronotop: acid, ai-agents, database, distributed-database; When needing a multi-model database with support for JSON documents and key-value storage alongside transactional capabilities.
- When should I avoid memory-os?
- - If you are looking for a completely cloud-managed service without any local setup or maintenance needs. - Your use case does not align with Hermes Agent; Memory-OS is specifically designed to complement this agent's functions and won't provide the same benefits when used independently.
- When should I avoid kronotop?
- If the project does not require vector search capabilities or ACID transactions, as these features may introduce unnecessary overhead. When a simpler database model without the complexity of setting up and operating on top of FoundationDB would suffice for the application needs.
- Is memory-os or kronotop more popular on GitHub?
- memory-os has more GitHub stars (1,366 vs 309). Stars measure visibility, not whether either tool fits your constraints.
- Are memory-os and kronotop open source?
- Yes - both are open-source projects on GitHub (memory-os: MIT, kronotop: Apache-2.0).
- Where can I find alternatives to memory-os or kronotop?
- GraphCanon lists graph-backed alternatives at memory-os alternatives and kronotop alternatives (memory-os markdown twin, kronotop markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, memory-os or kronotop?
- memory-os: Slowing. kronotop: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for memory-os and kronotop?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: memory-os trust report; kronotop trust report.