Modern self-hosted wiki for infrastructure teams

Problem Context

Infrastructure teams need a secure, modern wiki to document API keys, runbooks, and configs. They rely on these docs daily to avoid downtime and security risks, but existing tools either feel outdated, lack critical features, or are abandoned. Teams waste time switching between clunky interfaces or dealing with broken updates, which slows down their workflows and increases risk.

Pain Points

Current tools like BookStack and WikiJS have outdated UIs, while DocuWiki and xWiki feel too complex. Users struggle with stale projects (e.g., WikiJS v3 never released) and lack modern features like Markdown support, API key encryption, or OIDC authentication. Manual workarounds—like using Notion or Google Docs—don’t provide the security or versioning needed for infrastructure docs.

Impact

Downtime from misconfigured docs costs teams thousands per hour. Security risks from exposed API keys or outdated runbooks can lead to breaches. Frustration with clunky tools wastes 5+ hours per week per engineer, and the lack of a modern solution forces teams to stick with subpar alternatives that don’t scale with their needs.

Urgency

Infrastructure teams can’t afford to lose access to their docs. Every hour spent fighting a wiki’s UI or waiting for updates is time not spent improving systems. The risk of a single misconfigured API key or undocumented runbook can cause outages that directly impact revenue. Teams need a reliable, modern solution now—not in six months.

Target Audience

DevOps engineers, SREs, and IT admins at mid-size to large companies document infrastructure in wikis. Startups and scale-ups also face this problem but lack the budget for enterprise tools like Confluence. Open-source advocates and self-hosting enthusiasts in r/selfhosted and r/devops actively seek alternatives to proprietary or outdated solutions.

Solution Approach

A self-hosted, modern wiki built for infrastructure teams. It combines a clean, React-based UI with Markdown support, API key encryption, and OIDC authentication—all in a Docker container for easy deployment. The product focuses on security, usability, and versioning to replace clunky or abandoned tools while keeping costs low for teams that self-host.

Key Features

1. Modern UI: Dark/light mode, mobile-friendly, and built with React for a fast, intuitive experience.
2. Versioning + Diffs: Tracks changes like Git, so teams can see who modified what and when.
3. OIDC/Single Sign-On: Integrates with GitHub, Google, or company SSO for secure team access.
4. API + Webhooks: Lets teams trigger actions (e.g., Slack alerts for doc updates) or pull data into other tools.

User Experience

Teams install the wiki via Docker in minutes. They create docs in Markdown, mark sensitive content as ‘confidential’ (encrypted automatically), and share it with their team via OIDC. Changes are versioned, and conflicts are resolved with diff tools. Admins get alerts for unauthorized access attempts, while engineers access runbooks or API keys securely from anywhere. No more clunky interfaces or outdated software.

Differentiation

Unlike BookStack (outdated UI) or WikiJS (abandoned), this wiki is modern, secure, and actively maintained. It’s the only self-hosted solution that natively supports API key encryption + OIDC + Markdown in a single package. Competitors either lack features (e.g., Notion’s self-hosted version is proprietary) or require complex setups (e.g., MediaWiki). The Docker-based deployment makes it accessible to non-devs.

Scalability

Starts as a single-team wiki but scales to enterprise with team-based access controls, LDAP integration, and *cloud backups- for critical docs. Pricing tiers (e.g., $29/mo for teams, $99/mo for enterprises) unlock features like advanced analytics or priority support. The open-core model allows teams to self-host for free but pay for premium features if needed.

Expected Impact

Teams save 5+ hours/week by ditching clunky tools. Downtime risks drop as docs are always up-to-date and secure. Engineers spend less time fighting software and more time improving infrastructure. For companies, the cost of a $29/mo subscription is negligible compared to the risk of a single outage—making this a no-brainer for DevOps/SRE teams.