OpenMemory: The Neuro-Symbolic Consolidation Engine
OpenMemory is a Tier-1, enterprise-grade AI memory system designed for infinite scalability, zero-hallucination auditing, and military-grade security. Built for production LLM infrastructures (like those at OpenAI and Anthropic) or large enterprise deployments.
🚀 Features
- Asynchronous Scalability: Built on pure
async/awaitFastAPI andaiosqlite/asyncpg. It will never block the event loop, easily handling thousands of concurrent AI agents. - Envelope Encryption (AWS KMS): Security is not an afterthought. OpenMemory uses mathematically secure Envelope Encryption via
boto3. Master keys are held securely in the cloud, while the database only stores encrypted data keys. - Redis Token-Bucket Rate Limiting: Prevent API bankruptcy and DDoS attacks from runaway AI scripts. Malicious or looping agents are automatically throttled (HTTP 429).
- Neuro-Symbolic Consolidation (NSCE): Avoids standard vector DB hallucination loops by employing adversarial pruning before context injection.
- Docker & Kubernetes Ready: A multi-stage Dockerfile and Docker Compose setup is included for immediate, highly-available deployment.
📦 Installation
pip install openmemory-ai
🛠️ Quick Start
1. Local Deployment (Docker)
The easiest way to start OpenMemory, ChromaDB, and Redis locally:
git clone https://github.com/shivay00001/openmemory.git
cd openmemory
docker-compose up --build
2. Manual Start
pip install -r requirements.txt
uvicorn api.server:app --reload
🔐 Security Audit
OpenMemory has passed a rigorous simulated Vendor Security Review (VSR). It scored 100/100 for architecture (KMS, Redis, Async Postgres).
👨💻 About the Author
Built by Shivam Kumar (shivay00001).
📄 License & Commercial Use
OpenMemory uses a Dual-Licensing model:
- Free / Non-Commercial: Free for personal, academic, and non-commercial hobbyist use.
- Enterprise / Commercial: Paid. Any commercial use, production deployment, or integration into a revenue-generating product requires a paid Commercial License.
For enterprise licensing, VSR (Vendor Security Review) documentation, or Big Tech acquisitions, please contact the author.
Metadata
Release files for shivay00001 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| shivay00001-1.0.0.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shivay00001-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / shivay00001-1.0.0.tar.gz
| Download URL | shivay00001-1.0.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0491f7a20c31064a1116b5c2f01ea5f186d6c9f0ee40b30d0f57ed49beec6124
|
|
BLAKE2b-256 checksum How to use checksums |
0bccc18802270eb2f8dd1c363cafa94ae83c4f5bbd64d264a379564595ea8850
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / shivay00001-1.0.0-py3-none-any.whl
| Download URL | shivay00001-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
78926358879dd697d0b2e7019e86f34be2de354696245bd832c37270d754dd6b
|
|
BLAKE2b-256 checksum How to use checksums |
b04ad15db6ec9e2399c2a3266ac8d3ae9e581e4e2267ebffd05f888e4a0bbb61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for shivay00001 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.