Skip to main content

GitHub - GibsonAI/Memori: Open-Source Memory Engine for LLMs, AI Agents & Multi-Agent Systems

·460 words·3 mins
GitHub AI Open Source Python AI Agent LLM
Articoli Interessanti - This article is part of a series.
Part : Everything as Code: How We Manage Our Company In One Monorepo At Kasava, we've embraced the concept of "everything as code" to streamline our operations and ensure consistency across our projects. This approach allows us to manage our entire company within a single monorepo, providing a unified source of truth for all our configurations, infrastructure, and applications. **Why a Monorepo?** A monorepo offers several advantages: 1. **Unified Configuration**: All our settings, from development environments to production, are stored in one place. This makes it easier to maintain consistency and reduces the risk of configuration drift. 2. **Simplified Dependency Management**: With all our code in one repository, managing dependencies becomes more straightforward. We can easily track which versions of libraries and tools are being used across different projects. 3. **Enhanced Collaboration**: A single repository fosters better collaboration among team members. Everyone has access to the same codebase, making it easier to share knowledge and work together on projects. 4. **Consistent Build and Deployment Processes**: By standardizing our build and deployment processes, we ensure that all our applications follow the same best practices. This leads to more reliable and predictable deployments. **Our Monorepo Structure** Our monorepo is organized into several key directories: - **/config**: Contains all configuration files for various environments, including development, staging, and production. - **/infrastructure**: Houses the infrastructure as code (IaC) scripts for provisioning and managing our cloud resources. - **/apps**: Includes all our applications, both internal tools and customer-facing products. - **/lib**: Stores reusable libraries and modules that can be shared across different projects. - **/scripts**: Contains utility scripts for automating various tasks, such as data migrations and backups. **Tools and Technologies** To manage our monorepo effectively, we use a combination of tools and technologies: - **Version Control**: Git is our primary version control system, and we use GitHub for hosting our repositories. - **Continuous Integration/Continuous Deployment (CI/CD)**: We employ Jenkins for automating our build, test, and deployment processes. - **Infrastructure as Code (IaC)**: Terraform is our tool of choice for managing cloud infrastructure. - **Configuration Management**: Ansible is used for configuring and managing our servers and applications. - **Monitoring and Logging**: We use Prometheus and Grafana for monitoring,
Part : This Article
Memori Labs
#### Source

Type: GitHub Repository Original Link: https://github.com/GibsonAI/Memori?utm_source=opensourceprojects.dev&ref=opensourceprojects.dev Publication Date: 2025-11-18


Summary
#

WHAT - Memori is an open-source memory engine for Large Language Models (LLMs), AI agents, and multi-agent systems. It allows storing conversations and contexts in standard SQL databases.

WHY - It is relevant for AI business because it offers an economical and flexible way to manage the persistent and queryable memory of LLMs, reducing costs and improving data portability.

WHO - GibsonAI is the main company behind Memori. The developer community actively contributes to the project, as evidenced by the numerous stars and forks on GitHub.

WHERE - It positions itself in the market as an open-source solution for managing the memory of LLMs, competing with proprietary and expensive solutions.

WHEN - It is a relatively new but rapidly growing project, with an active community and continuous improvements. The project has already reached 4911 stars on GitHub, indicating significant interest.

BUSINESS IMPACT:

  • Opportunities: Integration with our existing stack to reduce LLM memory management costs. Possibility of offering persistent memory solutions to clients without vendor lock-in.
  • Risks: Competition with proprietary solutions that may offer advanced features. Need to monitor the project’s evolution to ensure it remains aligned with our needs.
  • Integration: Memori can be easily integrated with frameworks such as OpenAI, Anthropic, LiteLLM, and LangChain. Example of integration:
    from memori import Memori
    from openai import OpenAI
    
    memori = Memori(conscious_ingest=True)
    memori.enable()
    
    client = OpenAI()
    
    response = client.chat.completions.create(
        model="gpt-4o-mini",
        messages=[{"role": "user", "content": "I'm building a FastAPI project"}]
    )
    

TECHNICAL SUMMARY:

  • Core technology stack: Python, SQL databases (e.g., SQLite, PostgreSQL, MySQL). Memori uses an SQL-native approach for memory management, making data portable and queryable.
  • Scalability and limits: Supports any SQL database, allowing horizontal scalability. The main limitations are related to the performance of the underlying database.
  • Technical differentiators: Integration with a single line of code, cost reduction of up to 80-90% compared to solutions based on vector databases, and zero vendor lock-in thanks to data export in SQLite format. Memori also offers advanced features such as automatic entity extraction, relationship mapping, and context prioritization.

Use Cases
#

  • Private AI Stack: Integration in proprietary pipelines
  • Client Solutions: Implementation for client projects
  • Development Acceleration: Reduction of project time-to-market
  • Strategic Intelligence: Input for technological roadmap
  • Competitive Analysis: Monitoring AI ecosystem

Resources
#

Original Links #


Article recommended and selected by the Human Technology eXcellence team, processed through artificial intelligence (in this case with LLM HTX-EU-Mistral3.1Small) on 2025-11-18 14:09 Original source: https://github.com/GibsonAI/Memori?utm_source=opensourceprojects.dev&ref=opensourceprojects.dev

Related Articles #

Articoli Interessanti - This article is part of a series.
Part : Everything as Code: How We Manage Our Company In One Monorepo At Kasava, we've embraced the concept of "everything as code" to streamline our operations and ensure consistency across our projects. This approach allows us to manage our entire company within a single monorepo, providing a unified source of truth for all our configurations, infrastructure, and applications. **Why a Monorepo?** A monorepo offers several advantages: 1. **Unified Configuration**: All our settings, from development environments to production, are stored in one place. This makes it easier to maintain consistency and reduces the risk of configuration drift. 2. **Simplified Dependency Management**: With all our code in one repository, managing dependencies becomes more straightforward. We can easily track which versions of libraries and tools are being used across different projects. 3. **Enhanced Collaboration**: A single repository fosters better collaboration among team members. Everyone has access to the same codebase, making it easier to share knowledge and work together on projects. 4. **Consistent Build and Deployment Processes**: By standardizing our build and deployment processes, we ensure that all our applications follow the same best practices. This leads to more reliable and predictable deployments. **Our Monorepo Structure** Our monorepo is organized into several key directories: - **/config**: Contains all configuration files for various environments, including development, staging, and production. - **/infrastructure**: Houses the infrastructure as code (IaC) scripts for provisioning and managing our cloud resources. - **/apps**: Includes all our applications, both internal tools and customer-facing products. - **/lib**: Stores reusable libraries and modules that can be shared across different projects. - **/scripts**: Contains utility scripts for automating various tasks, such as data migrations and backups. **Tools and Technologies** To manage our monorepo effectively, we use a combination of tools and technologies: - **Version Control**: Git is our primary version control system, and we use GitHub for hosting our repositories. - **Continuous Integration/Continuous Deployment (CI/CD)**: We employ Jenkins for automating our build, test, and deployment processes. - **Infrastructure as Code (IaC)**: Terraform is our tool of choice for managing cloud infrastructure. - **Configuration Management**: Ansible is used for configuring and managing our servers and applications. - **Monitoring and Logging**: We use Prometheus and Grafana for monitoring,
Part : This Article