1. LandOffer
  2. Blog
  3. All articles
  4. Outline Wiki Review: Hosted or Self-Hosted Team Knowledge with Clear Ownership Costs

Productivity & Workflows

Outline Wiki Review: Hosted or Self-Hosted Team Knowledge with Clear Ownership Costs

Compare Outline Cloud with Community and paid self-hosted editions using a complete ten-person ownership budget and a rejected, revised recovery manifest. Separate subscription prices from operating work and documented backups from actual restoration evidence.

10 min readLandOffer team

Outline is worth evaluating when a team wants collaborative knowledge documents with clear access and maintenance ownership. Cloud is the stronger starting candidate when nobody has accepted responsibility for operating the service. Self-hosting can fit an approved infrastructure requirement, but a zero-priced Community license does not remove authentication, upgrades, storage, recovery or staff time. Choose the edition that meets your access requirements, then budget the operating work an identified owner accepts.

This LandOffer.ai review checks official documentation and personally inspected Cloud and On-Premises pricing tabs on October 27, 2026. Both ten-person budgeting and recovery records below are original fictional examples. No Outline instance, identity connection, server, backup, restore, account, subscription or public link was created or changed. The review establishes documented responsibilities and a completed planning decision, not a functioning deployment or verified service level.

Two conservators compare a maintained archive room with the tools needed to operate a separate archive themselves.

Separate the service from the software edition

The current pricing page offers Cloud tiers by team size. The observed monthly prices are $10 for one to ten members, $79 for eleven to one hundred and $249 for one hundred one to two hundred. The page says annual pricing is available; this review did not obtain an annual quote or checkout total.

The On-Premises tab shows Community Edition at $0 with limited features and no support, Business at $4/user/month billed annually with a ten-user minimum, and Enterprise at $5 with a one-hundred-user minimum. Buying a paid self-hosted license is not buying the hosted service. Infrastructure and operating responsibility remain with the deployment owner.

The observed comparison also excludes guest users, additional security controls and SAML from Community while including them in Business and Enterprise. A general SSO row is not a promise that every authentication method belongs to every edition. If those controls are required, comparing Cloud with Community's zero license price would compare different requirements.

Outline's license guidance identifies BSL restrictions for Community and directs users to the actual license. Public source availability is not unrestricted permission to sell or host the software as a service. Have the responsible company reviewer confirm the intended use and edition rather than treating a marketing “open source” label as the entire licensing decision.

Operating ownership starts before the first login

The hosting guide explicitly says production operation requires DevOps experience. Its requirements include a Unix-compatible environment, PostgreSQL, Redis, a domain and a compatible authentication provider. Hardware minimums are starting requirements, not sizing evidence for your actual workload or a promise that a cheap server is enough.

The authentication guide says Outline does not natively support email-and-password authentication. Choose a supported identity route for the relevant edition and get the identity owner involved early. A login button, an email address in a roster and a usable identity-provider integration are different things.

Cloud transfers application hosting work to the provider, but your team still owns content, membership decisions and the authority to grant access. Self-hosting adds operational duties. Assign upgrades, dependency health, certificates, storage growth, authentication failures and recovery to named owners so an absence does not leave the service unsupported. Confirm recurring time with the proposed operator; technical ability alone does not allocate that work.

The Docker guide recommends version pinning and warns that database migrations run on startup by default. The backup guide says migrations may not be backward compatible. Pulling an older application image therefore does not establish a safe rollback after a database change. This review provides no installation or rollback commands.

Worked asset: one ten-person team, two responsibility budgets

The fictional Vale learning-design team has ten internal members and needs a wiki for reusable workshop instructions. It has no current requirement for external guests, SAML, AI answers or private-server hosting. All dollar amounts and labor estimates below are teaching assumptions unless explicitly identified as observed subscription prices. No spending, staffing assignment or hosting work occurred.

Content owner Renata accepts two hours per month to maintain instructions under either option. Identity owner Hadi would handle the approved company-provider setup. Platform engineer Celeste can scope self-hosting, while substitute operator Pavel must receive a usable handoff. Department lead Astrid controls the proposed budget and workload allocation.

For comparison, the team values planned staff time at an invented $80/hour. That is an internal planning value, not a salary, contractor quote or measured maintenance rate. Both options include the same content work; the self-hosted option is not made artificially cheaper by dropping it.

First-year category Cloud at the observed ten-member monthly tier Self-hosted Community planning case
Subscription or license $10 × 12 = $120; twelve monthly bills, not an annual discount quote $0 Community license, subject to license and feature fit
Hosting, storage and backup allowance No separate customer-operated server in this case; confirm contract and storage terms Invented $25/month combined infrastructure allowance = $300; not a vendor quote
Initial identity, access and setup work Two hours × $80 = $160 Eight hours × $80 = $640 for configuration, identity and handoff
Content ownership, common to both Two hours/month × 12 × $80 = $1,920 Same $1,920
Recurring administration or operations Half an hour/month × 12 × $80 = $480 for membership and provider coordination Two hours/month × 12 × $80 = $1,920 for administration, updates, monitoring and planned recovery review
Stated first-year planning total $2,680 $4,780

The $2,100 difference follows from these assumptions, not a market-wide cost study or measured Outline savings. Cloud requires thirty-two planned staff hours across setup, content and administration; self-hosting requires fifty-six. Infrastructure and exceptional incidents could cost more. Neither allowance establishes an uptime commitment, security approval or successful restore.

The ten-member boundary matters. At the observed next Cloud tier, eleven members would mean $79/month, or $948 across twelve monthly bills: $828 more than the current ten-member subscription calculation. That is a tier change, not an extra $10 seat. Confirm the actual billable membership definition and pending invitations before relying on the lower tier.

For ten paid self-hosted Business users, the stated annual-equivalent license calculation is $480 before adjustments. Adding only that fee to the Community operating assumptions would produce $5,260, but the actual workload and purchased scope still need review. Enterprise's hundred-user minimum is not a ten-seat $600 annual offer.

Astrid's completed fictional decision is to request a Cloud evaluation. Renata accepts content maintenance, and Hadi accepts checking the identity route. Celeste's self-hosting proposal remains a documented alternative rather than an unowned future service. No trial or purchase is approved yet. Reopen self-hosting if an actual infrastructure requirement justifies the operating commitment and Astrid explicitly allocates its time.

A backup needs the material the service depends on

A document export, a database snapshot and a recoverable application are different deliverables. The backup guide recommends regular database backups and preserving changed environment configuration in protected storage. It specifically warns that losing the encryption key makes encrypted database data inaccessible. Do not paste actual secrets into a wiki recovery checklist; retain a reference to the approved protected store and its access owner.

Outline's file-storage documentation separately describes uploaded files stored on the local filesystem or an object-storage service. With Docker, persistence needs the appropriate storage mapping. A database file alone does not demonstrate that the illustrations attached to a workshop instruction will be available after recovery.

The security guide describes provider-side backups and exportable document text/images. Those are vendor descriptions, not a customer restoration result or an agreed recovery deadline. Ask how the hosted service would handle the specific incident and request. Keep a usable authorized export for continuity without claiming it reconstructs every permission, integration or historical state.

An archivist compares a database ledger, file portfolio and protected key reference before accepting a recovery packet.

Worked asset: reject an incomplete recovery packet

Vale's second asset is a completed paper review of an original synthetic recovery proposal. It is not a failed or successful Outline recovery test. The packet contains no credentials, real documents or live infrastructure identifiers.

The proposed wiki sample has document W1, a workshop preparation instruction; attachment A1, a diagram; and a restricted review collection. Renata needs W1's text and A1 to remain connected. Hadi requires an authorized member to sign in through the approved provider and a person outside the restricted group to remain unable to read that collection.

Celeste's initial proposal lists only a nightly database snapshot. Pavel reviews it against the service dependencies and records this complete disposition:

Required recovery component Initial proposal finding Completed planning decision
Database and compatible application version Snapshot listed, but release/version relationship not recorded Celeste must retain the version record and document migration compatibility; database existence alone is insufficient
Uploaded diagram A1 No upload-store copy or retrieval route listed Reject the packet as incomplete; add the chosen file store and recovery method with Celeste as owner
Protected configuration and encryption-key reference No protected-store reference or substitute access listed Hadi owns the approved protected-store route; Pavel needs an authorized recovery access procedure, not copied secrets
Identity-provider configuration “Company login works” is asserted without an accepted integration owner Hadi accepts responsibility for provider configuration and authorized sign-in checks; no integration is established by this statement
Documents, attachments and intended audience W1, A1 and the restricted group's expected state are specified; no observed result exists Renata checks content and attachment readability; Hadi checks allowed and denied readers in an isolated approved exercise

The completed result is not ready for recovery acceptance. The initial database-only proposal omits A1’s file storage and the protected configuration reference, and it lacks the application release record. Naming those omissions is a useful outcome; it would be misleading to mark the packet restored because the database row is present.

Celeste revises the proposed manifest to cover database, uploads, release record, protected-configuration reference and identity configuration reference. Pavel's second paper review finds all five categories accounted for. That is manifest completeness within this authored example, not proof that files exist, a key can be retrieved or a restored service works. No secrets are present in either manifest.

They also complete the acceptance specification: in an isolated authorized environment, restore the chosen release-compatible data and uploaded sample; open W1 and A1; check the approved reader can view the permitted collection; check the excluded reader cannot reach the restricted collection by its direct route; and verify the authorized editor can make a harmless sample revision. Stop if identity, attachment or access behavior differs from the specification.

A login-page screenshot would not satisfy those checks. Outline's troubleshooting guide notes that an instance may load while editing fails because the proxy does not support required WebSocket connections. Readable content and working collaboration therefore need separate observations. The guide also describes the consequences of losing the encryption key; this article does not recommend resetting encrypted data to bypass an incomplete recovery plan.

Pavel accepts the written handoff scope, while the actual isolated exercise remains pending. Astrid must allocate the operating time before Celeste runs it. For the Cloud candidate, Hadi and Renata still need identity, audience and export checks, plus confirmation of the provider's restoration process. Choosing hosted service narrows the team's infrastructure responsibility; it does not make content or access acceptance unnecessary.

Choose the operating arrangement you can keep maintaining

Outline offers collaborative knowledge documents through hosted and self-hosted routes. Keep the choice attached to actual requirements: edition features, supported identity, content audience, maintenance capacity and continuity. “We can run a container” answers only part of the self-hosting question.

The current Cloud FAQ describes a thirty-day trial becoming read-only until a payment method is added, with document export available then. Treat that as a documented trial boundary rather than a reason to defer the exit check. No trial expiry, payment or export behavior was observed for this review.

For Vale, Cloud is the justified evaluation candidate under the stated ten-member scope. Self-hosting remains viable only with a real requirement and accepted ownership, not because its download has a $0 label. For related workplace guidance, visit LandOffer.ai. Ask the approving owner to accept the responsibility budget and revised manifest, then complete the defined identity, content and recovery checks before accepting the service.

Sources and Further Reading