Internal docs
engineering runbooks, onboarding, architecture decisions
// official site: js.wiki ↗
PRODUCTIVITY · PRO TIER
Wiki.jspro
Wiki.js is a modern wiki engine on Node.js — Markdown-first, Git-syncable, with 50+ authentication strategies and a polished editing experience. It's the spiritual successor to MediaWiki for teams that want a wiki without PHP, plugins, or 2005-era UX.
// What it is
A closer look.
Wiki.js is a modern wiki engine on Node.js — Markdown-first, Git-syncable, with 50+ authentication strategies and a polished editing experience. It's the spiritual successor to MediaWiki for teams that want a wiki without PHP, plugins, or 2005-era UX.
Built to host internal documentation, public knowledge bases, and onboarding hubs with full Git history when needed.
// Use cases
What it's for.
Concrete scenarios where teams pick Wiki.js over the SaaS alternative.
Public knowledge bases
product documentation, FAQ, support content
Multi-team wikis
separate spaces with per-section ACLs
Markdown content
write in Markdown, render rich, link cleanly
Git-backed sync
back content to a Git repo for version control + portability
// Who it's for
Built for these teams.
If your team profile matches one of these, Wiki.js is a strong fit out of the box.
Engineering teams
wanting Confluence ergonomics without Atlassian licensing
Open-source projects
publishing user-facing docs from a Git repo
Mid-size companies
consolidating scattered Google Docs into one searchable place
Communities
running public wikis (alternative to Fandom/MediaWiki)
Privacy-conscious orgs
keeping docs self-hosted
// Differentiators
Why teams pick Wiki.js.
When evaluating self-hosted options for this category, here are the dimensions on which Wiki.js consistently lands above the alternatives.
- ✓AGPL-3.0 — open-source, no enterprise gating
- ✓Modern UX — fast SPA, real-time preview, no jarring full-page reloads
- ✓Markdown + Visual + WYSIWYG — three editing modes for different writers
- ✓50+ auth strategies — local, OAuth (GitHub/Google/Microsoft), LDAP, SAML, OIDC
- ✓Storage modules — local, Git, S3, Box, Dropbox for content sync/backup
- ✓Active 3.x development — major rewrite incoming with better performance
// Integrations
Connects to.
The stack you'll plug Wiki.js into — services, protocols, and adjacent apps in the BluixApps catalog.
◇
Git sync
bidirectional sync with GitHub/GitLab/Bitbucket
◈
Search providers
built-in, ElasticSearch, Algolia, AWS, Azure
◆
Auth
50+ providers via OAuth/OIDC/SAML/LDAP/local
▣
Notifications
Slack, Discord, Telegram, email
▦
Analytics
Google Analytics, Matomo, Plausible compatible
▩
Storage
S3, Box, Dropbox, Disk for asset/content backup
// Adoption & deployment
Notable users & community
- 25k+ GitHub stars
- Powers public wikis at Mozilla, Open Source projects
- Active Discord with 5k+ members
- Plugin ecosystem with 30+ integrations
- 3.x major version in development (Vue + GraphQL rewrite)
What we ship
- Docker: Wiki.js + Postgres 15 in shared network
- Pinned
ghcr.io/requarks/wiki:2 - Auto-generated DB password
- Port 3081 (HTTP), reverse-proxy ready
- Persistent volume for postgres data
- Install report with admin setup instructions
- Backup hook covers postgres + asset uploads
// Tips & operations
Run it properly.
Operational guidance from running this in production — what to lock down, what surprises people.
// PERFORMANCE
Use Postgres
SQLite works for single-user, Postgres needed for teams
// SECURITY
First admin = first user
register first to claim admin
// OPERATIONS
Storage module setup early
enable Git sync before bulk content imports
// RELIABILITY
HTTPS in production
needed for OAuth callbacks and modern features
// DEPLOYMENT
Backup = postgres + content
DB has page content; storage modules add redundancy
// SCALING
Locale support
50+ languages; set default in admin
512
// min ram (MB)
4
// min disk (GB)
3081
// access port
http
// protocol
pro
// bluixapps tier
// Alternatives in Productivity
Compare with
Project resources
Official sitejs.wiki ↗