#44th of 12 in Memory

OpenViking

Context database exposing agent memory, knowledge and skills as a filesystem

Stars
39.6k
License
AGPL-3.0
Last commit
Oct 2026
Last release
Oct 2026
Language
Python

Overview

OpenViking organises everything an agent knows as a viking:// virtual filesystem of resources, memories and skills, browsed with ls, tree, read and grep, with search scoped to a subtree. Each directory carries generated summaries so agents read full content only when needed. The server needs Python 3.10+ plus an embedding model and a VLM; plugins cover Claude Code, Codex, Cursor and OpenClaw.

Who it is for: Teams wanting transparent, file-like memory shared across coding agents

Strengths

  • Memory is inspectable and editable as Markdown files under viking:// URIs
  • LoCoMo accuracy 80 to 83% for OpenClaw, Hermes and Claude Code at far fewer tokens
  • Python, Go and TypeScript SDKs plus HTTP API; multi-tenant accounts and ACLs
  • Hosted Studio playground at openviking.ai/studio; Railway one-click deploy

Weaknesses

  • AGPL-3.0 license
  • Needs both an embedding model and a vision-language model from a provider
  • Memory plugin installer is macOS/Linux only; Windows uses the beta desktop app
  • Benchmarks were run with Volcengine Doubao models

What it needs

  • no GPU
  • Docker + Compose
  • Models: Volcengine, OpenAI, Codex OAuth, Kimi, GLM

Also in Memory

See all 12
Also in Memory
RankProjectScore
1hindsightAgent memory server with retain, recall and reflect operations48.1k stars, MIT78 out of 100
2MemPalaceLocal verbatim memory for coding agents on ChromaDB with 45 MCP tools59.5k stars, MIT77 out of 100
3agentmemoryPersistent memory server for coding agents, exposed over MCP and REST29.3k stars, Apache-2.075 out of 100
#5Mem0Memory layer for agents with a self-hosted server, SDKs and CLI Live demo ↗ (opens in a new tab)67k stars, Apache-2.073 out of 100
#6CogneeMemory engine that turns documents and code into a knowledge graph32k stars, Apache-2.073 out of 100