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.

Talkyard combines five discussion formats in one platform: StackOverflow-style Q&A with accepted answers, Reddit-like upvote sorting for ideas, threaded forums, real-time chat channels, and embeddable blog comments. Running separate tools for each conversation type fragments community knowledge across disconnected systems, but Talkyard keeps it all searchable in one place. Question askers mark accepted answers, and community voting surfaces the best solutions for future visitors. Idea topics sort by upvotes for crowdsourced feedback prioritization and product decisions. Chat channels handle real-time day-to-day conversation, while forum threads preserve important discussions that need to remain findable months later. The embedding capability goes beyond blog comments: entire Talkyard forums can live inside iframes on your existing website with automatic deep-linking and iframe auto-resizing, adding community discussion to any page without rebuilding your site. Docker Compose containers run with dropped capabilities, no-new-privileges enforcement, non-root processes, health checks, and automatic log rotation. Multi-site hosting serves multiple communities from one installation with isolated databases and separate domains. Automated upgrades pull new images and restart services without intervention. ElasticSearch indexes every discussion format for instant full-text search. The Scala backend with TypeScript frontend stores data in PostgreSQL with automatic Let's Encrypt HTTPS. Runs on a RepoCloud VPS with guaranteed CPU, RAM, SSD, root SSH, and browser console. AGPL licensed.

Created by Jeff Atwood, co-founder of Stack Overflow, and battle-tested for over a decade with 47,600+ GitHub stars, Discourse powers community forums for GitHub, Docker, Rust, Netlify, and thousands of organizations worldwide. The platform combines long-form threaded discussion with built-in real-time chat, enabling communities to move fluidly between asynchronous conversations and live interaction. Five automated trust levels progressively unlock permissions — posting links, editing wiki posts, flagging content, and moderating — based on reading time, post count, and community engagement, reducing spam and abuse without manual intervention. The Discourse AI plugin integrates with OpenAI, Anthropic, and self-hosted HuggingFace endpoints for automated topic summarization, sentiment analysis, semantic search, and AI-assisted content triage. Over 200 official and community plugins extend functionality with features like the Data Explorer for ad-hoc SQL queries against the forum database, polls, solved-topic marking, voting, calendar events, and custom user fields. SSO and OAuth support connects Google, Facebook, Apple, GitHub, and SAML identity providers, while reply-by-email and mailing list mode let users participate entirely through their inbox. The Ember.js single-page frontend delivers responsive performance across all devices with PWA support and web push notifications. Deployment uses Docker via the official discourse_docker launcher with automatic Let's Encrypt HTTPS, resource scaling based on server hardware, and support for single-container or multi-container configurations. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL v2.0 licensed.

A Misago forum comes with threads, polls, private conversations, nested categories, and the moderation tools to keep them in order. Categories nest to any depth. Permissions follow rank, role, and category. Registration can require e-mail activation or administrator approval, and a Q&A challenge, reCAPTCHA, Stop Forum Spam, or an IP blacklist can turn away spam sign-ups. More than 50 OAuth providers, including Google, GitHub, Steam, and Facebook, can handle sign-in. Posts accept GitHub-flavoured Markdown, a BBCode subset, or both, and attachments get thumbnails. Polls allow public or private voters, multiple choices, vote changes, and deadlines. Question threads let one reply be marked as the best answer. A post-accurate read tracker flags threads with new replies. Private threads stay visible only to the people invited. Presence shows who is online, and members can hide their own activity from non-admins. Custom profile fields get their own display and validation rules. Features and settings for GDPR compliance are included. Themes restyle the forum from the admin panel, and plugins extend it through action and filter hooks. Moderators can edit, move, hide, approve, delete, or close content, and a moderation queue holds new submissions for review before other members see them. If someone empties a post, the edit log shows the original wording and can restore it. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.0 licensed.

Forum software rebuilt on the modern web stack: NodeBB runs the classic bulletin-board format - categories, threads, local accounts - in real time, on Node.js over MongoDB, Redis, or PostgreSQL. WebSockets stream new posts into open topics as they're written and deliver instant notifications for follows, likes, and subscriptions; built-in chat supports side-by-side private conversations. The headline of recent versions is core ActivityPub federation: your forum can follow, share, and converse with other NodeBB instances, Mastodon, Lemmy, and anything else that speaks the protocol, turning an isolated community into a fediverse node. Everything beyond the common core is a plugin - more than 500 plugins and themes install in one click from the admin panel, covering SSO providers, search backends like Elasticsearch and Solr, galleries, calendars, and more. The theming engine extends base templates with SCSS/CSS on Bootstrap 5, plus a drag-and-drop widget system and custom HTML/CSS/JS injection. Operators get a real-time analytics dashboard, human-readable SEO-friendly URLs with semantic markup, multilingual UI, and full read and write REST APIs for integration. Mobile-first rendering means the same install works everywhere. For communities that outgrew phpBB but don't want Discourse's weight, NodeBB is the natural middle.

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.

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.

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.

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.

Workplace and Yammer's pattern on your own server, with GDPR compliance by construction rather than contract: HumHub is an open-source enterprise social network from Germany. Built in PHP on Yii2, it organizes everything around four concepts. Users get rich profiles with follows and interactions. Spaces are the structural unit - rooms for departments, projects, events, or clubs, with per-Space permissions, notification settings, and email summaries, and operators can auto-map users into the right Spaces. Content covers posts, wiki pages, photos and video, events, and tasks, with multi-level comments, versioning, archiving, moderation reporting, and filterable full-text search across everything. Modules make it a platform: roughly 80 install-and-activate extensions including Calendar, Wiki, Polls, Tasks, Gallery, News, direct-message Mail, OnlyOffice document editing, Advanced LDAP, SAML and JWT SSO, a RESTful API, mass user import, Translation Manager, and a Theme Builder with custom pages - every one optional and toggleable at runtime. That module economy is why HumHub serves such varied deployments: corporate intranets, city governments, universities, political parties, and nonprofits all configure the same core differently. Requirements are a plain LAMP stack - PHP 8.1+ and MySQL/MariaDB - making it one of the easiest community platforms to operate long-term.

Publish the answers your team keeps repeating as a multilingual, searchable FAQ with phpMyFAQ, a knowledge base whose admin area handles writing, review, and permissions. Organize entries in nested categories that you rearrange by drag and drop, attach files, add tags and related FAQs, and let visitors leave comments. A WYSIWYG editor with an image manager writes each answer, a wiki-style revision history restores earlier versions, and a news system posts announcements. Full-text search covers every language, and optional Elasticsearch or OpenSearch backends handle larger collections. The interface covers more than 40 languages with right-to-left layouts, automatic content negotiation, and translated categories and entries. Privileges work per user and per group, so an editor can change an entry without being allowed to delete it, and categories can be limited to chosen readers. Sign in through LDAP, Active Directory, or Microsoft Entra ID, protect accounts with two-factor authentication, or try experimental passkeys. The dashboard charts 30 days of visits, lists inactive FAQs, and checks installed files against published hashes. Export entries to PDF, publish a dynamic sitemap, back up your content, and filter spam with built-in protections. Dark, light, and high-contrast themes keep the public site comfortable to read. Scripts and AI assistants reach the knowledge base through a REST API with an OpenAPI specification or an experimental MCP server, and plugins extend it. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MPL-2.0 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.

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.