head to head · open source
wiki vs repowise
wiki has 29,128 GitHub stars, 3,335 forks, 182 open issues and last shipped yesterday. repowise has 8,107 stars, 981 forks, 436 open issues and last shipped yesterday. wiki leads on adoption by 259% (29,128 vs 8,107 stars). wiki is written in TypeScript under AGPL-3.0; repowise is written in Python under AGPL-3.0. wiki has attracted 11% 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. The two share 2 topic tags (documentation, open-source), so they are genuine substitutes rather than adjacent tools.
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
| wiki | repowise | |
|---|---|---|
| GitHub stars | ★ 29K | ★ 8.1K |
| License | AGPL-3.0 | AGPL-3.0 |
| Written in | TypeScript | Python |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 3.3K | ⑂ 981 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick wiki if
- You weight community size — 29K stars and counting
- You want the AGPL-3.0 license terms
- Your stack matches TypeScript
- 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 wiki
A modern, lightweight and powerful wiki app built on NodeJS Official Website Documentation Requirements Installation Demo Changelog Feature Requests Chat with us on Discord Translations (We need your help!) Special Thanks Contribute Follow our Twitter feed to learn about upcoming updates and new releases! Donate Wiki.js is an open source project that has been made possible due to the generous contributions by community backers. If you are interested in supporting this project, please consider becoming a sponsor, becoming a patron, donating to our OpenCollective, via Paypal or via Ethereum (
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 wiki or repowise more popular?
wiki has 29,128 GitHub stars and repowise has 8,107. wiki has the larger community by that measure.
Are wiki and repowise free?
Both are open source. wiki is licensed under AGPL-3.0 and repowise under AGPL-3.0. Neither carries a licence fee.
What is the difference between wiki and repowise?
wiki is written in TypeScript 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, wiki or repowise?
Choose wiki if you want the larger community (29,128 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.