When to choose Outline or Docmost for a self-hosted team wiki
Choose Outline when your team can accept the Business Source License 1.1 on the community edition, already runs an identity provider, and is prepared to fund SAML through a Business or Enterprise license. Outline's community edition forbids offering it as a Document Service or a commercial hosted offering, so a reader who plans to resell wiki access must read the license terms before committing. Outline does not support email and password sign-in natively, so the identity provider must exist before installation day. The license also changes to Apache License 2.0 on October 12, 2030 for the 1.11.0 release, a date your legal team should confirm against the current Outline license file.
Choose Docmost when you prefer an AGPL-3.0 core, want email and password or LDAP sign-in with TOTP multi-factor authentication, or need Confluence import. Docmost's documentation lists email and password, LDAP, SAML or OIDC and TOTP as authentication methods, but SAML 2.0, OIDC, LDAP, SCIM and MFA sit in the paid-edition feature list, so confirm which of these your chosen edition actually includes. The Business plan is priced per seat at $6 per seat per month billed annually with a 10-seat minimum, which suits a team that can count its users in advance. Its Confluence importer is also a paid-edition feature, so budget for it if migration from Confluence is part of the plan.
The decision turns on five things: the license reading your legal team accepts, the login method your identity estate supports, which import sources you must migrate from, the number of seats you will pay for, and the operations budget for running PostgreSQL and Redis yourself. Both products need PostgreSQL and Redis, and Docmost's compose template expects PostgreSQL 18 and Redis 8 images, so confirm your database and cache support policy before you compare prices. Ask each vendor for a written quote that lists the edition, seat count, support level and any import services, so the comparison reflects the same scope.
Which wiki fits which team scenario
This table maps common team situations to the wiki that fits better and the condition that makes it so. Read each row against your identity provider, migration source and hosting rules, since several answers depend on whether a paid license is part of the plan.
| Scenario | Better fit | Condition that decides it |
|---|---|---|
| Company with an existing Entra ID or Google tenant | Outline | Outline supports Microsoft Entra and Google sign-in in its community edition, so no paid license is needed for those methods. Confirm your tenant setup against Outline's authentication docs. |
| Team migrating from Confluence | Docmost | Docmost's documentation lists a Confluence importer as a paid-edition feature, so budget for a Business plan or higher. Outline's listed importer covers Notion, so Confluence would need a separate export path. |
| Organization that must avoid BSL hosting restrictions | Docmost | Docmost's core is AGPL-3.0, while Outline's community edition is under the Business Source License, which forbids offering it as a service. Enterprise-licensed code paths in Docmost still need review. |
| Small team that wants local accounts | Docmost | Docmost's documentation lists email and password as an authentication method. Outline does not support email and password natively and needs an external provider such as Google, Microsoft or OIDC. |
| Regulated team needing SAML or SCIM | Neither without a paid tier | Outline's SAML login is available only in its Business and Enterprise licenses. Docmost lists SAML 2.0 or OIDC, LDAP and SCIM provisioning as paid-edition features. Confirm the exact edition and the features you need before you decide. |
| Team that wants Notion import with no paid license | Outline | Outline's Notion importer is available in all editions from v0.83.0. Docmost's Notion export ZIP import is listed in its import dialog, but confirm whether your plan requires a paid edition for it. |
| Team that needs per-seat budgeting for a hosted plan | Docmost | Docmost lists a Business plan at $6 per seat per month billed annually with a 10-seat minimum, per its pricing page. Outline's hosted plans are priced separately, so request a current quote before comparing totals. |
How Outline and Docmost are built and deployed
Both platforms are self-hosted wikis that depend on PostgreSQL and Redis, so the database and cache are shared planning items. The differences sit in what each needs around that core: a domain and identity provider for Outline, and proxy, secret and file storage choices for Docmost.
PostgreSQL and Redis baseline
Outline requires PostgreSQL 14 or newer and Redis 4 or newer, so your database and cache versions must meet those minimums before you install. Docmost's Docker template runs PostgreSQL 18 and Redis 8 images. Confirm whether your platform team will host these as managed services or containers, because backup, patching and failover for both databases stay with you in either case.
Memory and host sizing
Outline needs at least 512MB of memory, with 1GB or more recommended, and runs only on Unix-compatible systems. Size the host for the Node process, the database and Redis together rather than for the wiki alone. Ask Docmost's vendor for its minimum memory and CPU figures, since the supplied documentation does not set them.
Domain and identity provider
Outline needs a dedicated domain and an authentication provider, and it does not offer native email and password sign-in. Plan for Google, Microsoft Entra, OIDC or another supported provider before go-live. Docmost supports email and password sign-in out of the box, so an identity provider is optional there, though SSO remains a paid-edition feature.
Docmost secrets and proxy
Docmost's compose template requires an APP_SECRET of at least 32 characters, so generate and store it in your secrets manager before first start. Its real-time editor also needs WebSockets enabled on any reverse proxy, which is a common gap when the wiki sits behind an existing ingress. Test collaborative editing through the proxy before users rely on it.
File storage options
Docmost stores attachments on local disk by default, with S3-compatible or Azure Blob storage as alternatives. Outline supports local or S3-compatible file storage and horizontal scaling. Decide early where attachments will live, because moving files later adds migration work and backup scope for your team.
Production operating effort
Outline's hosting documentation states that it requires dev-ops experience to run in production. Budget for upgrades, backups and monitoring across the app, database and cache. Ask Docmost's vendor for its production guidance, including its supported upgrade path, backup procedure and scaling model, and compare those answers with Outline's before choosing.
Side-by-side capabilities and login methods
This table compares license terms, sign-in options, import paths, storage and integrations for Outline and Docmost as documented in each project's own materials. Read the login and import rows first, because the paid-edition boundaries decide what a free self-hosted build can do for your identity and migration plan.
| Capability | Outline | Docmost |
|---|---|---|
| License and change date | Community edition under the Business Source License 1.1, not an OSI-approved open source license. The license names Apache License 2.0 as the change license with a change date of October 12, 2030. | Core under AGPL-3.0. Code in the ee directories falls under the Docmost Enterprise license. Confirm which modules your build includes before deployment. |
| Login methods without a paid license | Google, Microsoft Entra, Slack, OIDC, Discord, GitLab, passkeys and email magic link. No native email and password sign-in. | Email and password, LDAP, SAML or OIDC single sign-on, and TOTP multi-factor authentication, as listed in its documentation. Confirm which of these run on the free Community build. |
| SAML single sign-on | Available only in the licensed Business and Enterprise editions. | Listed as a paid-edition feature alongside SCIM provisioning, LDAP and MFA. Confirm whether your Community build includes SAML before relying on it. |
| SCIM and LDAP | Not listed in the hosting docs reviewed for this comparison. Confirm with Outline before planning directory sync. | SCIM provisioning and LDAP are listed as paid-edition features. Confirm the edition boundary with Docmost before design. |
| Notion import | Notion importer available in all editions from v0.83.0. | Accepts a Notion export ZIP through the import dialog. Check the export format against your Notion workspace before migration. |
| Confluence import | Not listed as a supported importer in the sources reviewed. Confirm with Outline. | Confluence importer listed as a paid-edition feature. Ask Docmost whether it is available in your chosen plan. |
| File storage options | Local or S3-compatible file storage, as covered in its hosting docs. | Local storage by default, with S3-compatible or Azure Blob storage as options. |
| Integrations listed in docs | GitHub, Linear, Figma, Slack, Jira and webhooks. | Draw.io, Excalidraw, Mermaid diagrams, and embeds from tools such as Airtable, Loom and Miro. Confirm any API or SSO-linked integrations in the current docs. |
| Latest release referenced | Outline v1.11.0, published October 12, 2026. | Docmost v0.96.0, tagged September 8, 2026. Check the tags page for later releases before you decide. |
What the BSL and AGPL licenses allow
Outline's community edition is licensed under the Business Source License 1.1, which is not an OSI-approved open source license. The source is available and you can self-host it for your own use, but the license restricts certain commercial uses, and those restrictions decide whether the community edition fits your plan.
- Document Service restriction: The license forbids using Outline to provide a Document Service.
- Third-party teams: It also forbids a commercial offering that lets third parties create their own teams and documents.
- Hosting as a service: Outline's hosting documentation says that selling, reselling or hosting Outline as a service breaches the terms and automatically terminates your license rights.
- Change license: For version 1.11.0, the license names Apache License 2.0 as the change license, with a change date of October 12, 2030. The change date is when that version converts, so the BSL terms govern it until then.
- Paid licenses: Business and Enterprise licenses add functionality and guarantees, and SAML login is only available in those editions.
Check whether your intended use stays inside internal staff access or whether any customers, partners or outside organizations would receive accounts.
Docmost's core is licensed under AGPL-3.0, which is an OSI-approved copyleft license. Code in three locations is handled differently: apps/server/src/ee, apps/client/src/ee and packages/ee are covered by the Docmost Enterprise license, so the repository contains two license regimes that you need to separate in your review.
- Core code: Files outside the enterprise directories fall under AGPL-3.0, including its obligations for modified versions offered to users over a network.
- Enterprise directories: The three paths named above fall under the Docmost Enterprise license, which has its own terms.
- Paid tier pricing: The pricing page lists a Business plan at $6 per seat per month billed annually with a 10-seat minimum. Enterprise is custom-priced and adds SCIM, audit logs, SIEM integration, security controls and a page verification workflow.
- Paid-edition features: The documentation lists SAML 2.0 or OIDC single sign-on, LDAP, SCIM, MFA, page-level permissions, and the Confluence, DOCX and PDF importers as paid-edition features.
- Build provenance: Record which repository, tag and license files apply to the exact build you deploy.
Ask the vendor in writing which features in your target build fall under the enterprise license.
Both vendors sell paid tiers, but they gate different features and publish different levels of pricing detail. Outline sells self-hosted Business and Enterprise licenses and hosted plans, while Docmost publishes a per-seat Business price and a custom Enterprise tier. The right comparison is between the features you need and the amount you would pay for them over the life of the deployment.
- Outline paid scope: The licensed tiers add SAML, guest users, branding removal and a support contract, according to the sibling topic on Outline editions.
- Docmost per-seat cost: The listed Business price recurs per seat, so cost rises with headcount and the 10-seat minimum applies even to small teams.
- Docmost Enterprise cost: Enterprise is custom-priced, so the quote depends on the features, support and terms you negotiate.
- Outline pricing gap: No Outline price was supplied for this comparison, so ask the vendor for the current self-hosted license price.
- Infrastructure costs: Hosting, storage, PostgreSQL, Redis and your authentication provider are separate recurring costs under either option.
Request a written quote that lists license fees, support terms, renewal conditions and what happens if your seat count changes.
License interpretation is your organization's task, and this page does not give legal advice. The restrictions in the Outline BSL and the split between AGPL-3.0 and enterprise code both depend on how you plan to use the wiki, so counsel should review the terms against your specific intended use before you select a platform.
- Describe the use: Write down who will get accounts, whether customers or partners are included, and whether any part of the service will be offered to others.
- Test the BSL wording: Ask counsel to compare the Document Service and third-party team restrictions with that description.
- Review AGPL duties: If you modify Docmost and offer it to users over a network, have counsel review the source obligations that apply to your deployment.
- Keep the paper trail: Retain the license file version, release tag and signed order form for the build you run.
- Plan the change date: For Outline 1.11.0, have counsel confirm how the October 12, 2030 change date affects your upgrade and renewal plans.
Complete this review before the platform decision, because changing a wiki after content and integrations are in place costs more than changing it during evaluation.
Why the license reading matters more than the feature list
Start with what each license allows you to do with the wiki, because the answer changes with who uses it. Outline's community edition is under the *Business Source License 1.1*, which forbids using it for a Document Service or for a commercial offering that lets third parties create their own teams and documents. Running Outline for your own staff is a different question from hosting it for customers or partners, and that boundary is where counsel should look first. Docmost's core is AGPL-3.0. The AGPL does not limit who inside your organization can use the software, but it attaches source obligations to modified versions that users interact with over a network. A partner portal built on a changed Docmost therefore carries its own duties. Offering either product as a hosted service for others is the case where both licenses need the closest reading.
The second check is which code you will actually run. Docmost's README places code in apps/server/src/ee, apps/client/src/ee and packages/ee under the Docmost Enterprise license, so the AGPL label covers only part of the product (docmost/docmost on GitHub). Docmost's documentation lists SAML 2.0 or OIDC single sign-on, LDAP, SCIM provisioning and the Confluence importer among paid-edition features, so a team that turns on directory integration may be running enterprise-licensed code. Build a module inventory: list each authentication, provisioning, import and audit feature you need, map it to a directory path or edition, and confirm that mapping with Docmost before you commit. Outline has a parallel issue, since SAML sits only in its licensed Business and Enterprise editions.
Take both readings to counsel while the decision is still open. Give counsel the deployment model in writing: who signs in, whether people outside your organization see pages, whether a managed service is planned, and whether your team will distribute modifications. Ask for a view on the production-use terms in Outline's LICENSE file, including the change date of October 12, 2030 and the Apache License 2.0 change license that apply to version 1.11.0, and on the AGPL network-use obligations as they apply to any changes you make. Also ask whether buying a paid Outline license or a Docmost Business or Enterprise plan changes the answer for your use. Your lawyers own the legal reading. Your implementation partner can supply the deployment facts and module inventory they will need.
Moving content between Outline and Docmost
This sequence moves pages, attachments and access rules from one wiki to the other with a tested sample first, so the cutover date rests on verified content and working logins rather than on an assumed migration.
Inventory spaces, pages and permissions
The wiki owner and an administrator list every collection or space, page count, attachment type, embedded tool and the groups or individuals with access to each. Keep the list in a spreadsheet with one row per space. Done means every space has a named owner, a permission summary and a note on which pages contain embeds, comments or nested hierarchies that may not carry over. Use this inventory as the baseline for the checks in the later steps.
Choose and test a sample space
Select one representative space that includes a deep hierarchy, attachments, tables, diagrams and at least one restricted page. Export it from the source and import it into a non-production instance of the target. The administrator compares page titles, body text, images and links against the source. Done means the sample reads correctly in the target and the team has a written list of defects to fix before the full run.
Export content from the source
Export from the source in the format the target imports most cleanly. Docmost exports pages or whole spaces as Markdown or HTML, and its import dialog accepts Markdown and HTML files, ZIP archives, Word DOCX documents, Notion export ZIPs and Confluence exports. For Outline sources, confirm the export format with your Outline version, since the Notion importer is a Outline import path rather than an export path. Done means each space has an archive stored in a controlled location with a checksum and a file count matching the inventory.
Import content into the target
Run the import in the target instance, space by space, starting with the sample space already tested. Import attachments alongside pages and record any files the importer skips or renames. Docmost's importers cover the formats listed in its import documentation, so confirm each source format is supported before you start. Done means every space shows the expected page count and the import log contains no unexplained errors.
Rebuild groups, collections and permissions
Recreate the groups, spaces or collections and the access rules from the inventory in the target, since permission models differ between the two platforms and are not expected to transfer as-is. Assign page-level restrictions manually where the target requires it. Done means a sample of users from each group can see and edit exactly the spaces the inventory recorded, and the owner signs off on each space.
Re-point links and attachments
Search the imported content for links to the old domain, relative links that broke during conversion and attachment references that point to the source. Update them to the target URLs or replace them with the imported file. Done means a scripted or manual link check returns no references to the source domain for the pages in scope, and a random sample of attachments opens in the target.
Test SSO and multi-factor sign-in before cutover
Confirm the identity provider configuration in the target with test accounts from each group, including users who need multi-factor authentication. For Outline, confirm that the chosen sign-in method is available in your edition, since SAML requires a licensed Business or Enterprise plan. For Docmost, confirm that SAML 2.0 or OIDC, LDAP and multi-factor settings match the paid or community features you chose. Done means each test account signs in, lands in the right space and is denied outside its groups.
Cut over and verify the final state
Freeze edits in the source, run a final delta export for pages changed since the initial export, import them, and redirect users to the target. Keep the source read-only for an agreed period so teams can check for missing content. The owner compares the final inventory against the target and records any items that did not transfer, such as comments, page history or embedded third-party content, and how each was handled. Done means the signed-off checklist lists every exception and the source is archived.
What drives the running cost of each wiki
Most of the running cost of either wiki is infrastructure and staff time, not the license. Both self-hosted editions are free to install, so the budget is driven by what you run underneath them. Outline needs PostgreSQL 14 or newer, Redis 4 or newer, at least 512MB of memory (1GB or more recommended), a dedicated domain, file storage that is local or S3-compatible, and an authentication provider. Docmost's compose template runs PostgreSQL 18 and Redis 8 images, stores files locally by default, and can use S3-compatible or Azure Blob storage. Ask each vendor or your platform team to size the database, cache, application hosts and storage for your page count, attachment volume and concurrent editors, then price those components in your own cloud or data center. These are recurring costs that scale with usage.
Seat fees apply only if you move to a paid tier, and the two vendors price differently. Docmost lists a Business plan at $6 per seat per month billed annually, with a 10-seat minimum, and Enterprise at custom pricing. Its paid features include SAML 2.0 or OIDC SSO, LDAP, SCIM provisioning, MFA, and the Confluence and DOCX importers, so check which of these you actually need before choosing a tier. Outline's paid Business and Enterprise plans are priced by the vendor, so request a written quote covering seat count, what is included (including SAML, which is limited to the licensed editions), support terms, and whether the price renews annually. Also confirm whether your identity provider already covers SSO. If it does not, add the licensing cost of that identity provider to the total, since neither wiki bundles one.
One-time costs and recurring staff time are where estimates usually go wrong. Migration is a one-time cost: Docmost imports Notion export ZIPs, Confluence exports and DOCX files, and Outline's Notion importer is available in all editions, but any Confluence content or permission model you need to rebuild will take labor. Recurring costs include staff time for version upgrades, database and attachment backups, reverse proxy configuration (Docmost requires WebSockets for its real-time editor), and monitoring. Ask any implementation partner for a fixed-scope quote that separates setup, migration, hardening, backup testing and ongoing support, and state in the written scope who owns each recurring task after go-live.
Questions buyers ask before choosing Outline or Docmost
Can I self-host Outline for free without SAML?
Yes. Outline's community edition is free to self-host under the Business Source License, and it runs without SAML because SAML login is only available in the licensed Business and Enterprise editions. Outline does not support email and password sign-in natively, so you must connect an authentication provider such as Google, Microsoft Entra, Slack, generic OIDC, GitLab, passkeys or email magic link. Build that provider into your plan from the start, since a dedicated domain and an authentication provider are required to run Outline. Confirm with Outline which sign-in options your identity setup needs before you commit to the community edition. Outline authentication documentation lists the supported methods.
What single sign-on does Docmost include in the free edition?
Docmost's documentation lists email and password, LDAP, SAML or OIDC single sign-on and TOTP multi-factor authentication among its authentication methods. Its paid features list also names SSO with SAML 2.0 or OIDC, LDAP and MFA, so the two lists overlap and do not settle the question alone. Before you assume the free build covers your provider, test the exact SSO path on a lab installation of the community build and check the current editions documentation. SCIM provisioning, audit logs and SIEM integration appear only in the Enterprise tier on the Docmost pricing page. Ask Docmost to confirm in writing which SSO and MFA features each edition includes.
Are the Notion and Confluence imports equal in Outline and Docmost?
No, they are not equal, and the difference depends on which source you are moving from. Outline's Notion importer is available in all editions from v0.83.0. Docmost's import dialog accepts a Notion export ZIP in its standard import flow, but its Confluence importer is listed among paid-edition features. The researched facts do not cover a Confluence importer for Outline, so confirm that with Outline before planning. Fidelity depends on the export format, embedded attachments, internal page links, permission mapping and user accounts, and none of these transfer perfectly. Run a test import of one representative space on a copy and review links, tables and attachments before you commit to a full migration.
How much PostgreSQL and Redis administration does each wiki need?
Both wikis need PostgreSQL and Redis, so both shift database and cache administration onto your team. Outline requires PostgreSQL 14 or newer, Redis 4 or newer, at least 512MB of memory with 1GB or more recommended, and a Unix-compatible host. Docmost's Docker compose template runs PostgreSQL 18 and Redis 8 images, requires an APP_SECRET of at least 32 characters, and needs WebSockets enabled on any reverse proxy for the real-time editor. The recurring work is similar: version upgrades, tested backups and restores, monitoring, TLS, network controls and capacity planning as page counts and users grow. Outline's hosting docs say running it in production requires dev-ops experience, so budget that skill set before you choose. See the Outline requirements for the full list.
Can I offer Outline to my customers under the Business Source License?
No, not as a hosted service for third parties. The Business Source License forbids using the community edition for a Document Service and for a commercial offering that lets third parties create their own teams and documents. Outline's hosting docs state that selling, reselling or hosting Outline as a service breaches the license and automatically terminates your license rights. The license for Outline 1.11.0 names Apache License 2.0 as the change license with a change date of October 12, 2030, but that date does not permit service use before it arrives. If your business model involves customer-facing knowledge bases, have counsel review the license text and Outline's commercial terms before you build anything. Docmost's AGPL core carries its own obligations, so review that license too.
How long does a wiki migration take, and what drives the timeline?
The researched facts do not give a migration duration for either wiki, so the timeline depends on your content and your decisions. The main drivers are the number of spaces and pages, the volume and type of attachments, the import path (Notion ZIP, Confluence export, Markdown, HTML or DOCX), how many internal links need rewriting, and how permissions and groups map onto each platform's model. Identity work also adds time, because user accounts and sign-in must match the new system before people can use it. Ask each vendor and your implementation partner for a written migration plan that includes a sample import, a link and permission check, and a cutover window. Use the sample results to estimate the full effort, not an assumed figure.
Can a team run Outline or Docmost without outside help?
Yes, a team can run either one without outside help if it already has Linux, container, database, reverse proxy and identity skills. Outline's own documentation says running it in production requires dev-ops experience, and Docmost recommends Docker for installation, so plan for ongoing operations from the first day. Outside help is optional. DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work begins, and ongoing support and upgrades are available as retainers. DeployOpen does not publish a price list, and a quote follows from the written scope.
How DeployOpen helps choose, implement and migrate a team wiki
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a team weighing Outline against Docmost, that work starts with a written scope that tests each product against your identity provider, content sources and hosting constraints before anything is installed.
How we scope
- Confirm which login methods your identity provider needs, and whether SAML or SCIM must work on the edition you choose.
- Inventory the Notion, Confluence, Word and Markdown content to move, including attachments, permissions and page history.
- Agree in writing which edition, licence terms and hosting model apply, and what each option requires you to run yourself.
How we build
- Deploy the chosen wiki with PostgreSQL and Redis in your environment, with the file storage and reverse proxy settings it needs.
- Configure single sign-on, groups and permissions, and test WebSocket behavior for the real-time editor through your proxy.
- Run a pilot import on a copy of representative spaces and check that links, images and permissions survive the move.
How we hand over
- Document the install, configuration, secrets handling, backup and restore steps in a form your operations team can repeat.
- Deliver a test record covering login, import results, permission checks and recovery from a backup, for your own review.
- Hand over administration with a clear list of what your staff own, including licence renewals and version upgrades.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover, scoped separately in writing.
- Plan version upgrades against the release notes of the platform you run, with a rollback path agreed before the change.
- Ask for a written quote built from the agreed scope, since DeployOpen does not publish a price list.
