Self-host

Open-source, self-hosted knowledge base

Run AFFiNE's docs-and-whiteboard workspace on your own server with Docker Compose. Self-host free for up to 10 seats per workspace; Team adds seats at $10/seat/month billed annually. Offline Installable Licenses are available through sales.

  • Your infrastructure and backups
  • Free up to 10 seats per workspace

What changes when you self-host AFFiNE?

AFFiNE combines documents and whiteboards in a workspace you can run on your own infrastructure. The desktop app works offline with local workspaces; the server backend is source-available under the AFFiNE EE license, while the editor and most client code are MIT-licensed.

Your team operates HTTPS, storage, access, backups and upgrades. AI is optional and requires your own provider keys on self-hosted workspaces. Compare the licensing and operating model before planning a rollout.

Licensing at a glance

Choose by workspace seats and network requirements; confirm commercial terms with sales.

Self-host Free

Up to 10 seats per workspace

The free self-host plan (shown on Pricing as Local FOSS + Cloud Basic) covers up to 10 seats per workspace. Community support applies.

See self-host pricing

Self-host Team

$10/seat/month billed annually

$12/seat/month when billed monthly. Team adds seats, 100 GB plus 20 GB per seat, and priority support.

Compare Team pricing

Installable License

For restricted or offline license activation

For networks that cannot reach AFFiNE's license service, an Installable License activates offline from workspace settings. Available through sales.

Plan an offline rollout

Is self-hosting right for you?

A good fit when

  • You want docs and a whiteboard on infrastructure you operate.
  • Your team can own HTTPS, backups, upgrades and provider-key configuration.
  • OIDC SSO with MFA enforced at your identity provider fits your identity plan.

Check these limits

  • Do not choose AFFiNE today if you require SAML or SCIM provisioning, built-in audit logs, or official Kubernetes deployment.
  • For larger teams, procurement or support requirements, review the Team plan and talk with sales before committing.
Review identity and support with sales

What your team operates

The official self-host path is Docker Compose. Plan these tasks before production use.

Backups and restore

Follow the documented Docker Compose backup procedure for PostgreSQL (pg_dump), storage and configuration; test a restore.

Upgrades

Follow the documented upgrade procedure and verify your own rollback and maintenance window.

HTTPS and access

Configure HTTPS on your infrastructure, set workspace roles and public-sharing policy, and use OIDC for SSO when needed.

Restricted networks

An Installable License can activate offline. Fonts from cdn.affine.pro, default client telemetry and images from ghcr.io need separate planning in disconnected environments.

Read the installation and operations guide

Pick your deployment path

Official Docker Compose

Run the documented stack on infrastructure you operate; plan storage, HTTPS, backup and upgrades.

Open the install guide

Compare operating models

Compare self-hosting with managed hosting and private-cloud conversations before choosing an operator.

Compare deployment paths

Plan a Docker Compose rollout

Use the official installation guide for current commands and configuration; validate each step in a pilot workspace.

  1. Prepare the host

    Select your infrastructure, domain, TLS termination, persistent storage and database backup location.

  2. Follow the official Compose guide

    Use the documented configuration and official images; review environment variables before starting the stack.

  3. Pilot and restore

    Sign in, test workspace access and collaboration, and confirm that your backup and upgrade process works.

Compare self-hosted knowledge base options

Compare self-hosted knowledge base options
AFFiNEOutlineBookStackDocmost
Core license
MIT editor + EE source-available backend
BUSL-1.1
MIT
AGPL-3.0 Community; paid Business/Enterprise
Deployment route
Official Docker Compose
Self-hosted on-premises edition
Community Docker images; no official Docker image
Self-managed Community and paid editions
SSO
OIDC; MFA at your IdP
Email magic link (SMTP), Google, Microsoft, Slack, OIDC; SAML in licensed Business/Enterprise
SAML2, LDAP and OIDC; built-in MFA
SSO in paid Business tier
Docs + freeform whiteboard
Docs-focused
Wiki-focused
Docs and diagrams

Authentication rechecked October 4, 2026; other vendor facts checked October 3, 2026. Verify licensing and editions before purchase.

Sources: Outline license · Outline pricing · Outline authentication · Outline SMTP and magic links · Outline OIDC · Outline SAML editions · BookStack installation · BookStack license · BookStack authentication · BookStack MFA · Docmost pricing · Docmost license

Frequently asked questions

What is a self-hosted knowledge base?

A self-hosted knowledge base is knowledge management software that runs on your own servers instead of a vendor's cloud. You control the data, the backups, the access policies and the upgrade schedule — which matters for privacy, compliance and long-term cost.

How do I self-host AFFiNE?

Use the official Docker Compose installation guide, then configure HTTPS, storage and backups on your own infrastructure. The guide also covers upgrades and backup procedures.

Is self-hosting AFFiNE free?

Self-host Free covers up to 10 seats per workspace. Team adds seats at $10/seat/month billed annually or $12 billed monthly, plus priority support. An Installable License for networks that cannot reach AFFiNE's license service is available through sales.

Compare Self Hosted plans

Is AFFiNE a self-hosted Notion alternative?

Yes, if you need Notion-style docs and databases alongside a whiteboard on infrastructure you operate. AFFiNE's editor and most client code are MIT-licensed; its backend is source-available under the AFFiNE EE license. Compare migration tradeoffs before moving a team.

Open-source and self-hosted Notion alternatives

Can a self-hosted knowledge base feed LLMs and AI agents?

AI is optional. Workspace owners can add their own provider keys (BYOK) after a server admin enables AI, admins can allow OpenAI-compatible endpoints, and AI can be disabled server-wide or per workspace. Review the provider data flow before enabling AI.

Private AI for business

Plan a self-hosted rollout

Discuss seats, identity, operations and offline license activation before deploying for your team.

Last updated: October 4, 2026