Wiki.js

Open-source self-hosted wiki and knowledge-management content platform.

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Wiki.js-maintained DigitalOcean cloud image, Docker or Helm

  2. Operated by

    Your team

    Customer manages the DigitalOcean project, Droplet or Kubernetes runtime, PostgreSQL, storage, TLS, identity, backups and upgrades.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodWiki.js-maintained DigitalOcean cloud image, Docker or Helm
InfrastructureServers / containers
Wiki.js uses long-lived application and PostgreSQL workloads on a Droplet or Kubernetes cluster.
Licensing modelOpen Source / Open Core
The reviewed Wiki.js upstream license is GNU AGPL version 3.
LicenseAGPL-3.0

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
AvailableEvidence and scope for Marketplace delivery

The DigitalOcean 1-Click Droplet catalog packages Wiki.js 3.3.0 and PostgreSQL 18. This package version differs from the directory upstream release snapshot. Review the image and upgrade path before provisioning; marketplace presence does not imply vendor support or commitment credit.

DigitalOcean Wiki.js Droplet package generated 2026-11-11 · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

The current authentication guide documents SAML 2.0, OIDC, OAuth2 and Microsoft Entra ID strategies. Enable a strategy and activate it for each site; reverse proxies must forward the correct host and scheme for callbacks.

Current Wiki.js 3.x administration; older 2.x strategy names differ · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official 3.x guide supplies Docker Compose and an OCI Helm chart. Its bundled PostgreSQL StatefulSet is a convenience deployment; production database HA is separate. Replace example secrets and pin compatible versions; the latest image tag is not assigned in 3.x.

Upstream 3.x Compose example and Helm deployment; not a validated HA package · Deployment artifact ↗ (Current 3.x installation examples and oci://ghcr.io/requarks/charts/wiki) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The requirements page says one CPU core can run Wiki.js, recommends two or more for workers, and specifies at least 1 GB RAM on Linux plus 1 GB application storage. Database, image and uploaded-content storage are additional; this is not HA sizing for 1 TB of data.

Upstream application starting requirements; not a load or availability guarantee · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The reviewed upstream Wiki.js core is licensed under AGPL version 3. This identifies the software terms, not a bundled hosting, support or marketplace-image price; those services and components require separate review.

Upstream scarlett branch license; separately distributed packages may have other charges · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Show all fields (7 not researched)
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

The current installation documentation covers Wiki.js 3.x and warns against the unversioned latest container tag. Pin a supported release, replace default administrator credentials, use a production PostgreSQL deployment and confirm the DigitalOcean image version and upgrade path.

Community & maintenance

Wiki.js release 3.4.0 was published on November 15, 2026, and the upstream contributor history records continuing project participation. The release evidence does not establish the version currently packaged in DigitalOcean Marketplace.

Category fit

Content management & CMS
Provides a self-hosted wiki and collaborative knowledge-management CMS with structured pages, permissions and search.

Compare within Content management & CMS

  • ApostropheCMSCustomer-operated content management and website application framework.
    • Heroku
    Customer-operated · Open Source / Open Core
  • Cockpit CMSSelf-hosted structured content and API management application.
    • Railway
    Customer-operated · Open Source / Open Core
  • Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CrafterCMSSelf-hosted content authoring and delivery platform.
    • AWS
    Customer-operated · Open Source / Open Core
  • Directus Self-HostedSelf-hosted content and data management with APIs over your SQL database.
    • Railway
    Customer-operated · Source Available
  • dotCMS Cloud AnywhereVendor-operated content platform deployed into a customer cloud account.
    • AWS
    • Azure
    • Google Cloud
    Vendor-operated BYOC · Commercial Only
  • DrupalOpen-source content management system for building and operating websites.
    • AWS
    Customer-operated · Open Source / Open Core
  • Ghost Self-HostedOpen-source publishing and membership CMS with documented customer-operated Linode and DigitalOcean deployments.
    • DigitalOcean
    • Linode
    Customer-operated · Open Source / Open Core

Showing 8 of 25 other listings in Content management & CMS. These products address related workflows; read their category-fit notes before comparing scope. See all of Content management & CMS →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Wiki.js-maintained DigitalOcean cloud image ↗ · DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.

      Wiki.js lists DigitalOcean under its maintained cloud-image installation paths. DigitalOcean separately documents the Marketplace image and deployment into a customer DigitalOcean project.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory