head to head · open source
OpenViking vs markdoc
OpenViking has 41,383 GitHub stars, 3,362 forks, 999 open issues and last shipped yesterday. markdoc has 8,520 stars, 263 forks, 29 open issues and last shipped 8 days ago. OpenViking leads on adoption by 386% (41,383 vs 8,520 stars). OpenViking is written in Python under AGPL-3.0; markdoc is written in TypeScript under MIT. OpenViking has attracted 8% as many forks as stars, markdoc 3%. 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.
← all 20902 open source comparisons
Side by side
| OpenViking | markdoc | |
|---|---|---|
| GitHub stars | ★ 41K | ★ 8.5K |
| License | AGPL-3.0 | MIT |
| Written in | Python | TypeScript |
| Last push | 2026-11-02 | 2026-10-26 |
| Forks | ⑂ 3.4K | ⑂ 263 |
| 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 markdoc if
- You want the markdoc feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and markdoc 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 markdoc
A powerful, flexible, Markdown based authoring framework. Markdoc is a Markdown based syntax and toolchain for creating custom documentation sites and experiences. We designed Markdoc to power Stripe's public docs, our largest and most complex content site. Installation To get started with Markdoc, first install the library: or and import it in your app: or if you are using ESM then use Markdoc in your app or tool: Check out our docs for more guidance on how to use Markdoc. TypeScript This is the minimal tsconfig.json required to use Markdoc in your TypeScript project: React If you are using React, install…
read the full markdoc 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 markdoc more popular?
OpenViking has 41,383 GitHub stars and markdoc has 8,520. OpenViking has the larger community by that measure.
Are OpenViking and markdoc free?
Both are open source. OpenViking is licensed under AGPL-3.0 and markdoc under MIT. Neither carries a licence fee.
What is the difference between OpenViking and markdoc?
OpenViking is written in Python and markdoc in TypeScript. 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 markdoc?
Choose OpenViking if you want the larger community (41,383 stars) or its AGPL-3.0 licence terms. Choose markdoc if its feature set, stack or MIT licence fits better. Both are self-hostable.