Wiki-Go

Modern, feature-rich, databaseless flat-file wiki platform.

Steady · 60
60/100
Steady

Maintained, but at a slower pace than the leaders in its category.

Maintenance 15/40
Releases 25/25
Community 5/20
Momentum 15/15

Commit activity more than 37% of tracked projects; popularity more than 27%. How this is calculated.

Commits, last 11 months

2025-12: 43 commits 2026-01: 16 commits 2026-02: 8 commits 2026-03: 7 commits 2026-04: 9 commits 2026-05: 10 commits 2026-06: 10 commits 2026-07: 1 commits 2026-08: 3 commits 2026-09: 59 commits 2026-10: 2 commits
2025-12 168 total 2026-10
Stars628
Latest releasev1.9.6 · 15 Nov 2026
Repo updated15 Nov 2026
LicenceGPL-3.0
Built withGo, Docker

Is Wiki-Go actively maintained?

Development is ongoing. The repository recorded 168 commits over the same window, and the last three months alone account for 64 of them.

Activity is accelerating: the last quarter carried 205% more commits than the one before it.

The most recent tagged release, v1.9.6, shipped within the last month — a current, installable version exists today.

Wiki-Go ranks #10 of 24 in Wikis, placing it mid-table for maintenance activity.

What Wiki-Go actually does

Wiki-Go is a flat-file wiki platform written in Go that stores information directly on disk without requiring an external database. It provides a structured space for teams or individuals to document knowledge and manage documentation through a web interface. Being a databaseless application, it relies on local file systems to persist all content.

Best fit: Self-hosters who prefer lightweight documentation tools that avoid the operational overhead of running a separate database server.

Worth knowing: Flat-file storage can struggle with concurrent edits and high-volume search performance compared to dedicated database-backed wiki systems.

Deployment notes

You can typically deploy this using Docker, ensuring that you map a persistent volume to the container for your markdown files and configurations. A reverse proxy such as Nginx or Caddy is usually required in front of the container to handle TLS termination.


Alternatives to Wiki-Go

Projects in the same categories, ordered by health score.