Most wikis die of flat page-and-tag sprawl; BookStack's defining decision is enforced structure - an MIT-licensed PHP/Laravel platform (over MySQL) where content lives in a hierarchy of shelves, books, chapters, and pages, the way a physical library works. A shelf maps to a department, a book to "Engineering Runbooks," a chapter to "Database Procedures," a page to the actual document. That opinionation removes the "where does this go?" friction and keeps knowledge bases tidy as they grow. Editing works both ways: a clean WYSIWYG editor for most users, a Markdown editor with live preview for those who prefer it - switchable per page. Full-text search spans all books or scopes to one, with direct links to individual paragraphs, and include tags let you embed one page's content inside another so shared blocks update everywhere at once. Every edit creates a diffable, revertible revision. Page templates standardize recurring formats, tags add cross-cutting categorization, and built-in diagrams.net integration draws architecture diagrams in place. Authentication covers email/password plus OIDC, SAML2, LDAP, and social login; a full role and permission system locks content down per shelf, book, or page. Pages and books export to PDF, HTML, plain text, and Markdown, a REST API automates content, and the whole thing runs happily on the cheapest VPS you can find.

Graduated as an Apache Software Foundation Top-Level Project with over 15,500 GitHub stars and 100,000+ Docker Hub downloads, Apache Answer delivers the structured Q&A platform that Stack Overflow and Discourse popularized — fully self-hosted under Apache 2.0 with zero vendor lock-in. The Go backend with React frontend serves questions, answers, and knowledge articles with real-time Markdown preview using CommonMark syntax, inline @mentions to ping domain experts, and transparent revision history tracking every edit. Version 2.0 introduced AI workflows including an integrated AI assistant that helps draft and improve answers, a Model Context Protocol server for connecting AI agents to your knowledge base, API key management, and editor plugin support for extending the writing experience. Advanced search filters by tags, usernames, scores, and date ranges, while real-time suggestions surface relevant existing questions as users type to reduce duplicates. The reputation system rewards quality contributions with configurable privilege thresholds, and admin/moderator/user roles control access across the platform. A plugin architecture enables community-built extensions for third-party OAuth login, caching backends, search engines, and storage providers. Theming supports custom layouts, dark mode, and responsive design across devices, with content available in 15+ languages translated by the community. Bulk user import, email domain restrictions, and content access controls secure the platform for enterprise deployment. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Run a Stack Overflow of your own: Apache Answer brings the question-and-answer format in-house, maintained under the Apache Software Foundation with an Apache-2.0 license. You use it to run a community forum, product help center, or internal knowledge base where content lives as questions and answers rather than wiki pages. It ships the mechanics that make that format work: voting, accepted answers, a reputation system with privilege levels, tagging, full-text search with filters, revision history on every edit, and admin/moderator/user roles. Content is written in Markdown with real-time preview and code syntax highlighting. A plugin system covers OAuth login (Google, GitHub), S3 storage, external search backends like Algolia, and Akismet anti-spam, and a REST API exposes platform data for integration. The backend is Go, the frontend React, and it runs against SQLite, MySQL, or PostgreSQL. Self-hosting replaces per-seat tools like Stack Overflow for Teams with a flat-cost instance where you own all the content.

Team and product documentation on a fast Vue frontend with PostgreSQL storage: Wiki.js is a Node.js wiki engine. Its distinguishing trait is per-page editor choice: authors pick Markdown with live preview, a WYSIWYG visual builder for non-technical writers, or raw HTML, page by page. Native Git synchronization commits every page change to GitHub, GitLab, Bitbucket, Azure DevOps, or any Git remote - bi-directionally, so edits made in the repository flow back into the wiki - giving documentation version-controlled backup for free. Authentication coverage is among the broadest of any self-hosted wiki: local accounts with self-registration, social login via Google, GitHub, Discord, and Slack, and enterprise SSO through LDAP/Active Directory, SAML, CAS, Auth0, Okta, Azure AD, Keycloak, and generic OAuth2/OIDC, with optional MFA. Built-in full-text search runs on PostgreSQL with zero setup, and external engines like Algolia or Solr can substitute. Page history with visual version comparison, granular group-based permissions per path, nested navigation menus, 50+ integration modules, and full localization round it out. AGPLv3-licensed with a 28k-star community.

Every page in Otter Wiki is a plain Markdown file and every save is a git commit, so a small team gets a simple wiki whose history never goes missing. The editor highlights Markdown as you type, offers a toolbar for headings, lists, tables, code, alerts, and images, and can show a live preview beside the source. Paste or drop an image into the editor and it is stored as a page attachment. History, blame, and changelog views, with RSS and Atom feeds, show who changed what and when. Beyond standard Markdown you get footnotes, task lists, math formulas, Mermaid diagrams, alert boxes, and spoiler or folded blocks, plus experimental embeddings such as sortable data tables, info boxes, image frames, videos, and included pages. A customizable sidebar shows a menu, a page index, or both. Search offers case-sensitive and regular expression options. Dark mode is built in. Admins decide whether anonymous visitors, registered users, or approved users may read, write, or upload, grant rights per user, close registration, or require email confirmation. An optional, experimental git web server lets people clone, pull, and push the wiki, and changes can be pushed to or pulled from a remote repository over SSH. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

In seven wizard steps, PandaWiki sets up a product docs, manual, FAQ, or blog site whose built-in AI answers visitors using only your own content. Those visitors can chat with an assistant that cites its sources and accepts image questions, or switch to a docs-only search that lists ranked pages with summaries. Publishing stays under control: each document has three switches, visible in navigation, reachable by URL, and answerable by AI, and nothing appears or gets learned until it is published. Authors write in a Markdown and HTML editor, or import from URLs, RSS and Atom feeds, sitemaps, offline .txt, .md, .xlsx, .docx, and .pdf files, Notion, Yuque, SiYuan, Wiki.js, Feishu, Confluence, and DingTalk. Pages export to Word, PDF, or Markdown. The wizard covers models, domain, HTTP or HTTPS ports, import, publishing, answer testing, and page decoration. One knowledge base can also feed a web widget and DingTalk, Feishu, WeCom, and Discord bots. Administrators get a dashboard of visits, questions, visitor regions, hot documents, and referring domains. Chat models come from Baizhi Cloud, DeepSeek, OpenAI, or Ollama, while vector and reranking models are built in. The open-source edition covers one wiki site, 300 documents, and one admin, and its console and documentation are in Chinese. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Enterprise documentation discipline without enterprise infrastructure: Documize Community is the Confluence alternative built on exactly that trade. The entire platform - Go backend, Ember.js frontend - compiles to a single executable binary for Linux, Windows, and macOS with zero runtime dependencies: no Elasticsearch, no Redis, no JVM. Point it at PostgreSQL, MySQL, MariaDB, Percona, or Microsoft SQL Server (rare in open source, decisive in Microsoft shops), and schema migrations run on launch with native full-text search on whichever engine you chose. Content organization rejects nested-folder sprawl for Spaces, categories, and labels, and the section-based composable editor mixes rich text, Markdown, code blocks, PDFs, diagrams, and embedded Jira or Trello content in one document, with reusable blocks and templates so teams start from standards rather than blank pages. It deliberately unifies internal team docs and customer-facing documentation in one system with granular space-, document-, and action-level permissions deciding who sees what. Where wikis stop, Documize continues: content approval workflows (draft, review, approve, publish), version management, lifecycle control, feedback capture, PDF export, analytics showing what gets read and ignored, activity streams, and audit logs. Keycloak, LDAP, and SSO integrate for enterprise auth. AGPL-licensed.

Confluence and Notion both want your team's documentation in their cloud; Docmost, an open-source collaborative wiki platform, keeps it on your server. The centerpiece is a Notion-style block editor with CRDT-based real-time collaboration: multiple people edit the same page simultaneously and changes merge without conflicts or overwrites. Content lives in spaces - per team, project, or department - with nested page trees, role-based permissions, groups, inline comments, page history with restore, and full-text search across everything. The editor covers tables, code blocks, callouts, KaTeX math, and file attachments, and diagramming is built in rather than bolted on: Mermaid, Draw.io, and Excalidraw all render inside pages, alongside embeds for Airtable, Loom, Miro, and more. Migration paths include Notion, Markdown, HTML, and ZIP archive imports (Confluence, PDF, and DOCX importers ship in the Enterprise edition, along with SSO via SAML/OIDC/LDAP and MFA). The stack is TypeScript with PostgreSQL and Redis, deploys via Docker Compose, runs in air-gapped environments with no external dependencies, and is translated into 10+ languages. The AGPL-3.0 community edition carries no per-seat fees; the project has passed 20,000 GitHub stars since its 2024 launch.

Engineering teams and technical writers maintain operational runbooks, system documentation, and knowledge bases using LeafWiki, an open-source self-hosted wiki that stores page contents directly as human-readable Markdown files on the local filesystem. Authors can compose documentation through a dual-pane editor equipped with live HTML preview, keyboard navigation, autocomplete for internal links, and native rendering for Mermaid diagrams, KaTeX mathematical formulas, and collapsible callout containers. The navigational tree organizes complex documentation into explicit directory hierarchies and custom drag-and-drop page sequences tracked in lightweight configuration files rather than arbitrary alphabetical lists. An integrated SQLite engine indexes page content and custom taxonomy tags for fast full-text searches, automatic incoming backlink tracking, and automated broken link detection. System operators can deploy the single-binary application without external database servers or runtime dependencies, backing up the entire repository by copying the data directory. Administrators can provision granular user roles, configure reverse proxy header authentication for single sign-on gateways, and manage read-only API access keys for automated documentation scripts and continuous integration pipelines. Public viewers can browse technical notes without authentication or switch between dark and light high-contrast themes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 3,200 GitHub stars, 900 forks, and backing from the team behind ERPNext, Frappe Helpdesk delivers a modern, streamlined alternative to Zendesk and Freshdesk with unlimited agents, no per-seat pricing, and full source code access under the AGPL-3.0 license. Built on the Frappe Framework with a Python backend and Vue 3 frontend using Frappe UI, the application collects customer inquiries from email, web forms, and the customer portal into a centralized ticketing queue with complete conversation history and threaded replies. Customizable SLA rules define response and resolution timelines by ticket type or team, triggering automatic alerts and escalations when deadlines approach or are missed. Assignment rules route incoming tickets to the appropriate agents based on priority, issue type, or workload balancing, while manual reassignment and transfer between teams remains available at any time. The customer self-service portal lets users submit tickets, track status, and search a knowledge base of published help articles that reduce repetitive support requests. Agents access saved reply templates for consistent, rapid responses to common queries. Custom fields, configurable workflows, and saved views adapt the interface to match each organization's support process. Real-time updates via WebSocket push ticket changes instantly to all connected agents. The PWA-compatible interface provides mobile access without a native app. Frappe Framework compatibility spans versions 15 and 16. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

A deliberately simple ticketing system standing in for both Zendesk and Jira: Peppermint handles internal staff requests and external customer support alike. The stack is modern full-stack TypeScript: Next.js and React over Prisma and PostgreSQL, which makes it light to run and approachable for developers extending it. Ticket creation is straightforward - a markdown editor with file uploads, assignment, status tracking, and a logical workflow that new agents grasp without a manual. Mailbox integration converts email into tickets automatically: configure SMTP/IMAP per mailbox and incoming messages become trackable tickets. Each client accumulates an interaction history, giving agents context on every past request before replying. Two touches distinguish it from bare-bones ticketing: a built-in markdown notebook with todo lists for internal documentation and knowledge sharing, and OIDC authentication so agents sign in through your existing identity provider - Keycloak, Okta, Authentik, or Azure AD. Configurable webhooks and email notifications push ticket events to third-party services. The UI is responsive from mobile to 4K, and everything works fully offline in air-gapped environments. Docker-native and scalable via Kubernetes, with an active community of 3,000+ GitHub stargazers.

Unlimited agents, unlimited tickets, unlimited mailboxes, forever, on a $4 VPS - FreeScout's pricing inversion is why it became the most popular self-hosted Help Scout alternative, a PHP/Laravel help desk and shared inbox developed from scratch over eight years. The inbox deliberately behaves like Gmail or Outlook, so new support agents need close to zero training. The email-support core is genuinely complete: seamless IMAP/SMTP integration including modern Microsoft Exchange authentication, collision detection that warns when two agents open the same conversation, canned responses, auto-replies, internal notes, open tracking, starring, forwarding, merging, and moving conversations between mailboxes, phone-call logging, push notifications, and an auto-refreshing conversation list - plus screenshot pasting straight from the clipboard into replies. It's 100% mobile-friendly, fully screen-reader accessible, and translated into 28 languages. Beyond the core, an ecosystem of 100+ modules (mostly one-time $12-20 purchases) adds knowledge base, workflows with Gmail-filter-style automation rules, satisfaction ratings, time tracking, tags, custom fields, LDAP, Slack, WhatsApp and Telegram channels, and an API with webhooks - pay only for what your team needs. Web installer and updater included. AGPL-licensed.

With 5,700+ GitHub stars and over a decade of active development since 2012, Zammad is the open-source helpdesk platform that unifies every customer communication channel — email, live chat, telephone, WhatsApp, Telegram, Facebook, SMS, and web forms — into a single ticket management interface backed by PostgreSQL, Elasticsearch, and Redis. Version 7.0 introduced native AI features including automated ticket categorization, priority assignment, and title rewriting via AI agents that plug into triggers, macros, and scheduler jobs, plus one-click AI ticket summaries and a writing assistant — all configurable with your choice of LLM provider: OpenAI, Anthropic, Mistral AI, Azure AI, Ollama for local models, or any custom OpenAI-compatible endpoint with full audit logging of every AI action. Define service level agreements with first response, update, and solution time tracking tied to business hours calendars, with automatic escalation notifications. The knowledge base provides multilingual FAQ management with internal and public visibility. Core workflows enable dynamic ticket masks with conditional field dependencies per group. Text modules let agents insert predefined responses via the double-colon shortcut, while macros execute multi-step actions with one click. Security includes two-factor authentication, S/MIME and PGP email encryption, and single sign-on via SAML or OpenID Connect. Integrations connect to GitHub, GitLab, Microsoft 365, LDAP with nested group support, and Exchange. Deploy via Docker Compose, Kubernetes with the official Helm chart, or DEB/RPM packages. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPLv3 licensed.

Unleash the power of Chatwoot, the open-source superhero in the world of customer experience! This platform is perfect for businesses craving to connect with their customers across a multitude of channels without breaking the bank. Wave goodbye to the high-and-mighty likes of Intercom, Zendesk, and Salesforce Service Cloud, and say hello to a wallet-friendly powerhouse. Chatwoot turns your agents into customer service ninjas, armed with the latest in workload management, performance tracking reports that refresh themselves (because who has time for that?), and automations that work smarter, not harder. Zap through conversations with lightning-fast responses and manage your social media and email interactions in a single bound. Plus, with Chatwoot, you get to be the Sherlock of customer satisfaction, deducing your CSAT scores on autopilot. All this hosted on RepoCloud, where the cost is as tiny as the effort you'll need to switch over. Get ready to engage, enlighten, and entertain your customers with Chatwoot!

When a customer emails your support address, starts a live chat, or asks a question from your help center, opendesk lands it in one shared ticket inbox where every change appears live for the whole team. Agents work a single queue where tickets carry status, priority, assignee, team, tags, and an SLA clock, with internal notes, merging, snoozing, and bulk edits for busy days. Customers chat through a widget that offers identity verification, typing indicators, and 14 languages, and each widget can route to its own team and topics. Support leads publish collections and articles to a public help center, set SLA targets per priority, run automation rules on ticket events, and read reports on volume, response and resolution times, breaches, and CSAT. Ollie, the built-in AI, uses that help center to answer chats, draft replies, summarize threads, triage tickets, and translate both ways, through any Anthropic or OpenAI-compatible provider including local models. Admins can switch it off. Replies leave from your own address through Google, Microsoft, or any SMTP server. Developers connect Linear, GitHub, Jira, Sentry, Slack, Stripe, and any MCP server, or build on the REST API, signed webhooks, and a realtime socket. Desktop apps for macOS, Windows, and Linux and a native iPhone app keep agents reachable. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.