Outline is a team knowledge base and wiki for internal documentation, meeting notes, onboarding material, project decisions, and operating procedures. Documents live in nested collections and use a Markdown-compatible editor with collaborative features, version history, comments, mentions, templates, and embedded content. Workspace search and AI-assisted answers help teammates retrieve information from their own documents instead of relying on scattered chat history. The product is relevant to developer and platform teams because it combines structured knowledge management with an API, webhooks, integrations, and a self-hosted deployment path.
Teams can use Outline as a managed cloud service or operate it on their own infrastructure. The current cloud pricing page lists team-size bands rather than per-seat billing: $10/month for 1–10 members, $79/month for 11–100, and $249/month for 101–200, with a 30-day trial and annual pricing available. The higher bands add organizational controls such as SSO, groups and permissions, API or webhook access, and audit capabilities according to the current plan matrix. Buyers should verify the exact feature boundary and quote at execution time because plan packaging can change independently of the open repository.
The repository is active and substantial: the official GitHub API returned 39,892 stars, archived=false, disabled=false, a push on 2026-07-29, and latest release v1.9.2 published on 2026-07-21. Those signals support an active lifecycle classification but are not a service-level guarantee. Self-hosting gives an organization more control over data residency, authentication, backups, upgrades, and availability, while also transferring those operational responsibilities to the operator. Teams without platform capacity may prefer the managed service even though the source is publicly available.
Outline is source-available, not OSI open source today. Its Business Source License 1.1 includes a restriction on operating a competing multi-tenant “Document Service” and names 2030-07-13 as the Change Date to Apache License 2.0. The CMS field isOpenSource is therefore intentionally false; the public copy explains the future license conversion without treating it as present-day Apache licensing. The open-source tag is also intentionally omitted. Buyers considering commercial embedding, a competing service, or redistributed modifications should review the license and obtain legal guidance rather than relying on the catalog summary.
