Folio vs. a conventional wiki
In Folio, Git and agents are first-class participants in the wiki. Here, a conventional wiki means a common internal product with a page tree, web editor, search, permissions and history; actual products vary.
The workflow difference
Teams often maintain a second copy or integration between a database-backed wiki and the repository.
In Folio, a synchronized browser edit becomes a Git commit, an IDE edit returns to the wiki, and an agent reads or writes through MCP within the token owner's permissions. Folio shows ahead, behind and conflict states; after synchronization, changes converge.
Side by side
| Area | Folio | Conventional wiki |
|---|---|---|
| Source of truth | Files in the team's Git repository | Usually the wiki's database; products vary |
| Page format | Readable Markdown and related files | Product-specific storage or markup |
| Developer workflow | IDE, branch, diff, blame and merge tools | Usually centered on the web editor and integrations |
| Collaboration | Real-time browser editing plus synchronization | Web editing, comments and page history; products vary |
| Structured data | Markdown-backed tables and forms | Depends on the product and plugins |
| Visual work | Mermaid and editable Excalidraw files | Depends on built-ins, embeds or plugins |
| Agents | Built-in Ask/Agent, .agent pages and MCP | Depends on the product or a custom integration |
| Self-hosting | Required | Managed, self-hosted or both |
| Exit path | Keep the readable repository | Depends on export formats and product semantics |
What Folio changes
- Git stops being a downstream copy and becomes the working content history.
- People, IDEs and agents converge on the same pages.
- Sync state is explicit: clean, ahead, behind or conflict.
- The trade-off is operating Folio and resolving Git conflicts when they happen.
Where Folio is the better choice
Choose Folio when Git and agents should be first-class participants in your wiki. A browser edit becomes a Git commit, an IDE edit returns to the wiki, agents read and write through permission-scoped MCP, and sync state is always explicit. Your content stays readable Markdown you can leave with at any time, on infrastructure you self-host.
Try it with one real workflow
- Pick one page that developers and non-developers both change.
- Move only that page and its nearest dependencies.
- Run one browser-to-Git and one Git-to-browser sync.
- Test an agent with the minimum permissions it needs.
- Compare maintenance cost before moving anything else.
Other comparisons
Try Folio with one real team wiki.
Clone it, run it, and test the workflow with your own files.