jsonbored/mem0-aio repository overview

⁠mem0-aio

An Unraid-first, single-container deployment of Mem0 OpenMemory⁠ for people who want the easiest reliable self-hosted install without manually wiring a separate vector database on day one.

mem0-aio keeps the critical first-boot dependency bundled: Qdrant plus persistent local storage. The wrapper is opinionated for a predictable beginner install, but it does not hide the real tradeoffs: OpenMemory still needs a valid model/provider configuration to do useful work, external vector backends and hosted model endpoints still need operator knowledge, and exposing the direct MCP/API port is a deliberate security decision rather than a default requirement.

⁠What This Image Includes

• OpenMemory web UI on port 3000
• OpenMemory API / MCP server on port 8765
• Embedded Qdrant vector store
• Persistent appdata storage for SQLite and Qdrant state
• Upstream backup/export helper scripts bundled into the image
• Same-origin UI routing to the API so a standard Unraid install does not need separate browser-facing API networking
• Unraid CA template at mem0-aio.xml⁠

⁠Beginner Install

If you want the simplest supported path:

1. Install the Unraid template.
2. Leave the default appdata path in place.
3. Optionally set OPENAI_API_KEY if you want OpenAI immediately.
4. Start the container.
5. Open the web UI on port 3000.
6. If you did not set OpenAI, finish provider setup in the UI for Ollama or another upstream-supported provider.

Leaving OPENAI_API_KEY blank is supported for first boot. It only keeps the container usable enough to finish setup. Real memory generation still requires a working LLM and embedder configuration.

⁠Power User Surface

This repo is deliberately not a stripped-down wrapper. The template now tracks the practical OpenMemory self-hosted environment surface exposed by upstream source and docs, plus AIO defaults for the bundled SQLite + Qdrant path. In Advanced View you can:

• point OpenMemory at Ollama, Anthropic, Groq, Together, DeepSeek, Azure OpenAI, Bedrock-compatible providers, and other upstream-supported provider values
• override both LLM and embedder providers, models, API keys, and base URLs independently
• move vector storage to Chroma, Weaviate, Redis, pgvector, Milvus, Elasticsearch, OpenSearch, or FAISS
• keep using bundled Qdrant privately by default with telemetry disabled unless you explicitly re-enable it
• keep the bundled internal defaults for the easiest install while still exposing the upstream env surface for power users

The wrapper still defaults to the internal bundled storage path so new Unraid users are not forced into extra services on day one.

⁠Runtime Notes

• As of 2026-04-17, upstream Mem0 has a newer stable release than the original wrapper baseline; this repo is being moved to the current stable v2.0.0 line rather than staying on the older v1.0.x line.
• The direct API / MCP port is optional for normal browser use because the UI proxies to the API over the same published web port.
• The embedded Qdrant service is intentionally bundled because that is the critical first-boot dependency for the AIO path. External vector store support remains optional advanced configuration.
• If you expose OpenMemory beyond your LAN, treat the direct MCP/API surface and your model/provider credentials as real attack surface.

⁠Publishing and Releases

• Wrapper releases use the upstream version plus an AIO revision, such as v2.0.0-aio.1.
• The repo monitors upstream releases through upstream.toml⁠ and scripts/check-upstream.py⁠.
• Release notes are generated with git-cliff.
• The Unraid template <Changes> block is synced from CHANGELOG.md during release preparation.
• main publishes latest, the pinned upstream version tag, an explicit AIO packaging line tag, and sha-<commit>.
• When Docker Hub credentials are configured, the same publish flow pushes Docker Hub tags in parallel with GHCR so the CA template can read Docker Hub metadata.

See docs/releases.md⁠ for the release workflow details.

⁠Validation

Local validation in this repo is built around:

• XML validation for the audited template surface
• shell and Python syntax checks
• local Docker build and smoke coverage
• restart and persistence checks for the embedded OpenMemory stack

⁠Support

• Repo issues: JSONbored/mem0-aio issues⁠
• Upstream app: mem0ai/mem0⁠
• Official OpenMemory docs: docs.mem0.ai⁠

⁠Funding

If this work saves you time, support it here:

• GitHub Sponsors⁠
• Ko-fi⁠
• Buy Me a Coffee⁠

⁠Star History