AFFiNE

What it unlocks

AFFiNE puts block documents and an edgeless canvas in the same workspace. The official repository (opens in a new tab) describes it as a local-first, open-source alternative to document and whiteboard products, while its feature description says blocks can appear on the canvas alongside pages, shapes, embedded web content, and collections. That can reduce the friction of moving from a written brief to a visual plan without exporting between unrelated apps.

AFFiNE is available through managed, desktop, mobile, and self-hosted paths. These are different operating choices, not interchangeable privacy guarantees. The official self-hosting guide is the source for the deployment claims below; no AFFiNE instance was installed or tested for this review.

A first useful project

Unexecuted suggestion; no hands-on result is claimed. Create a fictional lab-study planning workspace:

1. Make one page describing a synthetic study question, assumptions, and three deliverables.
2. Add an edgeless canvas with sticky notes for inputs, risks, and milestones.
3. Link the canvas blocks back to the written brief and add a small collection for tasks.
4. Share it only with a test workspace or use placeholder names and data.

Success means a collaborator can find the written brief, see the same milestones visually, and trace every task back to one stated deliverable. If that structure feels heavier than a plain document, choose the simpler document tool instead.

Costs and operating effort

The official pricing page (opens in a new tab) presents a free personal path, paid Pro and Team offerings, self-hosting, and a separate AI add-on. Plan prices and allowances are volatile, so check that page before purchasing. The repository licence says that most repository content is MIT licensed while specific backend and native directories have separate terms; that is not a substitute for an organisation's licence review.

Self-hosting changes the cost model rather than eliminating it. The official deployment guide (opens in a new tab) recommends Docker Compose and lists the AFFiNE server, Postgres, Redis, blob storage, configuration, reverse proxy, and HTTPS as components to operate. It also calls for backups and restore testing before relying on production data.

Where it falls short

The combined workspace is useful precisely because it has more surface area than a standalone note editor. A learner who only needs a shared page can create unnecessary structure by introducing collections and canvas work prematurely. Local-first and self-hosting claims also do not answer how a particular team configures identity, retention, backups, or device access.

The official source checked here does not establish measured collaboration performance, migration quality from another product, enterprise support suitability, or a security audit outcome. Treat those as implementation questions to test before moving real workspaces.

Alternatives and trade-offs

Choose a plain document workspace such as Notion when a familiar document-first workflow matters more than an integrated canvas, subject to its own pricing and data terms. Choose Miro when a dedicated collaborative whiteboard is the primary requirement rather than a local-first document workspace. Choose a self-hosted knowledge base such as Outline when structured team documentation and operational support are more important than an edgeless board.

Choose AFFiNE when the document-to-canvas transition is a real workflow need and the team accepts its product and operational complexity. Do not choose it merely because it combines several categories on paper.

Learn more

Read the official repository (opens in a new tab) for the product scope and source layout, the official self-hosting guide (opens in a new tab) for production responsibilities, and the official pricing page (opens in a new tab) for current plans. The catalogue uses the repository's workspace demonstration as a credited screenshot. No independent screencast or hands-on tutorial was checked.