OSSHunt

Checked 2026-10-21

Notion vs AFFiNE (mixed-license stack; review required)

Fit:

Migration notes

Docs and canvas approach; local MIT editor is useful, but full self-hosted collaboration has mixed licensing and seat/plan questions. Pilot database parity and export/import round trips.

Sources: affine.pro, affine.pro · checked 2026-10-21

NotionPaid incumbent

Entry priceNot established
Pricing modelper-seat, billed monthly
OwnerNotion Labs, Inc.

Paid Plus exists; page auto-selected EUR 9.50/member/month and billing state was ambiguous. USD entry intentionally unverified; free SaaS tier is not OSS. Source

Notion plans reviewed
PlusentryUSD 120 / user / yr
BusinesspopularUSD 240 / user / yr
BusinessbusinessUSD 240 / user / yr
EnterpriseenterpriseQuote only
Fit for Notion
License
Paid-feature tier U
Self-host
Paid-feature limits2 noted
AFFiNE (mixed-license stack; review required) plans reviewed
Local editor / Freefree local editor/coreFree
Self-Hosted Teampaid self-hosted TeamUSD 120 / user / yr
Enterprisecommercial self-hosted/cloud contractsQuote only

What you may give up

  • Official enterprise page says self-hosted Team required for more than 10 seats; multiple admin roles and priority support in Team.
  • Non-CE backend/native code has commercial EE production and redistribution restrictions.

Tier U: MIT covers code outside backend/native. Backend EE license explicitly exempts CE-distributed and specified client-side portions under MPL-2.0. Official marketing calls backend source-available, while blogs acknowledge MPL CE carveout. Full current CE boundary not independently reconstructed: do not present full stack as verified OSI OSS. MIT local editor is clearly OSS. License source

What running it takes

  • Application and migration job plus persistent storage/config volumes

Hover or focus an icon for its name. Dashed means not established; struck through means no; grouped icons are alternatives.

Local-first editor usable independently; server uses PostgreSQL/Redis in stable-image compose. Backend source-available/component-specific licenses; check release CE/EE boundaries. Canary-branch compose read deploys stable images. Infrastructure and staff time are not priced here; this page does not compare total cost.