head to head · open source

OpenViking vs mkdocs-material

OpenViking has 41,383 GitHub stars, 3,362 forks, 999 open issues and last shipped yesterday. mkdocs-material has 27,594 stars, 4,153 forks, 1 open issues and last shipped 4 days ago. OpenViking leads on adoption by 50% (41,383 vs 27,594 stars). OpenViking is written in Python under AGPL-3.0; mkdocs-material is written in Python under MIT. OpenViking has attracted 8% as many forks as stars, mkdocs-material 15%. OpenViking 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.

OpenViking ★ 41K mkdocs-material ★ 28K category Content & Publishing

← all 20902 open source comparisons

Side by side

OpenViking mkdocs-material
GitHub stars ★ 41K ★ 28K
License AGPL-3.0 MIT
Written in Python Python
Last push 2026-11-02 2026-10-30
Forks ⑂ 3.4K ⑂ 4.2K
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

full OpenViking profile →

pick mkdocs-material if

  • You want the mkdocs-material feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Python
  • You evaluated both and mkdocs-material fits your workflow better

full mkdocs-material profile →

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 mkdocs-material

A powerful documentation framework on top of MkDocs Write your documentation in Markdown and create a professional static site for your Open Source or commercial project in minutes – searchable, customizable, more than 60 languages, for all devices. Check out the demo – squidfunk.github.io/mkdocs material . Silver sponsors Bronze sponsors <img src=" height="58"

read the full mkdocs-material 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 mkdocs-material more popular?

OpenViking has 41,383 GitHub stars and mkdocs-material has 27,594. OpenViking has the larger community by that measure.

Are OpenViking and mkdocs-material free?

Both are open source. OpenViking is licensed under AGPL-3.0 and mkdocs-material under MIT. Neither carries a licence fee.

What is the difference between OpenViking and mkdocs-material?

OpenViking is written in Python and mkdocs-material 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 mkdocs-material?

Choose OpenViking if you want the larger community (41,383 stars) or its AGPL-3.0 licence terms. Choose mkdocs-material if its feature set, stack or MIT licence fits better. Both are self-hostable.