Back to catalog
TiddlyWiki
BSD-3-ClauseTiddlyWiki is an open-source non-linear wiki that replaces Confluence with single-file portability, flat-file storage, and total data sovereignty.
Open-source alternative to — compare it against:
Overview
Jeremy Ruston released TiddlyWiki in 2004 as an experimental personal notebook that packaged its code, content, and interface into a single standalone HTML document. That architecture eliminated database servers and cloud dependencies, establishing a non-linear knowledge system that users own entirely. For small teams, agencies, and operations leads, it remains a durable self-hosted wiki where technical documentation stays private, portable, and immune to SaaS sunsets.
Why TiddlyWiki instead of Confluence
Confluence binds documentation to Atlassian Cloud, subjecting team knowledge to per-seat fees, telemetry, and proprietary databases. TiddlyWiki provides complete data sovereignty instead. Running as a single HTML file or a Node.js service storing plain text notes on disk, it gives operations leads and agencies physical custody of their records without cloud dependencies.
The divide is collaboration versus overhead. Confluence excels at real-time concurrent editing, granular permissions, and Jira integration. TiddlyWiki omits native multi-user drafting and enterprise access controls, requiring teams to coordinate edits through Git branches or reverse proxies. In return, licensing costs vanish, and an entire wiki can be backed up or cloned with basic filesystem commands.
What it does well
- Single-file portability: Compiles logic, interface, and content into an independent HTML file that opens offline in any browser, letting agencies hand off complete documentation packages to clients without accounts.
- Flat-file filesystem storage: Stores individual notes as plain text files under Node.js, letting operations leads version-control wikis with Git and review changes through standard pull requests.
- Non-linear transclusion: Links, tags, and dynamically embeds modular tiddlers across guides, letting teams assemble complex runbooks from reusable procedural snippets without duplicating text.
- Zero database overhead: Operates without PostgreSQL or MySQL, eliminating database maintenance, shrinking attack surfaces, and running on modest virtual servers or local drives.
- Hackable interface: Exposes layouts, views, and styling through WikiText macros, letting teams build custom dashboards and documentation templates without third-party plugins.
- Static site rendering: Provides command-line tools to compile wikis into static HTML files or JSON payloads for automated publishing to web servers.
