head to head · open source

OpenViking vs mkdocs-material

OpenViking has 39,947 GitHub stars, 3,177 forks, 999 open issues and last shipped today. mkdocs-material has 27,575 stars, 4,145 forks, 1 open issues and last shipped yesterday. OpenViking leads on adoption by 45% (39,947 vs 27,575 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 ★ 40K mkdocs-material ★ 28K category Content & Publishing

← all 20902 open source comparisons

Side by side

OpenViking mkdocs-material
GitHub stars ★ 40K ★ 28K
License AGPL-3.0 MIT
Written in Python Python
Last push 2026-10-15 2026-10-14
Forks ⑂ 3.2K ⑂ 4.1K
Self-hosting Yes Yes
Data ownership Your server Your server

pick OpenViking if

  • You weight community size — 40K 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

OpenViking is an open source context database for AI agents that keeps everything an agent knows — knowledge, memory, and skills — in one virtual filesystem, built for developers and teams who need to inspect and edit what their agent actually stored instead of trusting an opaque embedding index.

read the full OpenViking overview →

About mkdocs-material

Material for MkDocs is a documentation framework built on top of MkDocs, the static site generator for project documentation. It lives in the Python ecosystem and is distributed as a theme plus an accompanying set of plugins, so authors write documentation in Markdown and MkDocs builds it into a static site that the theme renders. The project is licensed under MIT, has existed for eleven years, and is maintained as an open source project with more than 27,000 stars and over 4,000 forks on GitHub.

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 39,947 GitHub stars and mkdocs-material has 27,575. 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 (39,947 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.