head to head · open source
OpenViking vs repowise
OpenViking has 41,383 GitHub stars, 3,362 forks, 999 open issues and last shipped yesterday. repowise has 8,107 stars, 981 forks, 436 open issues and last shipped yesterday. OpenViking leads on adoption by 410% (41,383 vs 8,107 stars). OpenViking is written in Python under AGPL-3.0; repowise is written in Python under AGPL-3.0. OpenViking has attracted 8% as many forks as stars, repowise 12%. repowise was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| OpenViking | repowise | |
|---|---|---|
| GitHub stars | ★ 41K | ★ 8.1K |
| License | AGPL-3.0 | AGPL-3.0 |
| Written in | Python | Python |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 3.4K | ⑂ 981 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick OpenViking if
- You weight community size — 41K stars and counting
- You want the AGPL-3.0 license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick repowise if
- You want the repowise feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches Python
- You evaluated both and repowise fits your workflow better
About OpenViking
The Context Database for AI Agents English / 中文 / 日本語 Website · Live Demo · GitHub · Issues · Docs · Blog Lark · WeChat · Discord · X What is OpenViking OpenViking is an open source context database for AI agents — one filesystem for everything an agent knows: knowledge, memory, and skills. Most agent memory is a black box: text goes in, embeddings come out, and nobody can see what was actually stored. OpenViking organizes context as a virtual filesystem under viking:// instead. Agents navigate it like files — ls , tree , read , write , grep — and you can open any directory to inspect and edit what your agent…
read the full OpenViking overview →
About repowise
Stop paying your agent to re read your codebase. Repowise indexes your code, git history, tests and decisions once, on your machine. Your coding agent asks the index instead of grepping and opening files, so it does about half the work. You get the same answers in a dashboard: what calls this, what breaks, what to fix first, and why. Half the tool calls your agent opens 3 files where it opened 7 · 31.6% less output Up to 99% less noise from test runs, installs and git output · every error line kept 88% of the right files found in one call · next best tool: 61% Graph, risk, health, tests and dead code make zero…
read the full repowise overview →
More in Content & Publishing
Related comparisons
More Documentation & Knowledge Base projects
Compare either of these against the rest of the Documentation & Knowledge Base field.
Frequently asked questions
Is OpenViking or repowise more popular?
OpenViking has 41,383 GitHub stars and repowise has 8,107. OpenViking has the larger community by that measure.
Are OpenViking and repowise free?
Both are open source. OpenViking is licensed under AGPL-3.0 and repowise under AGPL-3.0. Neither carries a licence fee.
What is the difference between OpenViking and repowise?
OpenViking is written in Python and repowise in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, OpenViking or repowise?
Choose OpenViking if you want the larger community (41,383 stars) or its AGPL-3.0 licence terms. Choose repowise if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.