# AFFiNE

Local-first docs, canvas and structured content with cloud or self-hosted collaboration.

Revision: 2026-09-15.1 · Review: unreviewed

Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

## Applicability

Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.; Repository revision 2af30773aecd567f09b346e7b72fc69143144057; deployed release not pinned.. AFFiNE clients with a selected cloud or self-hosted backend; pin edition and team entitlements..

## Claims

- **yes · documented**: Combines editable documents and a canvas. [AFFiNE repository overview](https://github.com/toeverything/AFFiNE/blob/2af30773aecd567f09b346e7b72fc69143144057/README.md) Scope: AFFiNE client; selected build and backend.
- **yes · documented**: Documents real-time collaboration across clients. [AFFiNE repository overview](https://github.com/toeverything/AFFiNE/blob/2af30773aecd567f09b346e7b72fc69143144057/README.md) Scope: Configured collaboration backend; convergence untested.
- **yes · documented**: Provides a shared team document workspace. [AFFiNE team workspaces](https://affine.pro/teamhub) Scope: Team plan and backend edition must be pinned.
- **yes · documented**: Supports multi-view databases as content blocks. [AFFiNE repository overview](https://github.com/toeverything/AFFiNE/blob/2af30773aecd567f09b346e7b72fc69143144057/README.md) Scope: Supported client data views; no database-engine claim.
- **yes · documented**: Documents operating an AFFiNE deployment yourself. [AFFiNE repository overview](https://github.com/toeverything/AFFiNE/blob/2af30773aecd567f09b346e7b72fc69143144057/README.md) Scope: Pin image, edition and applicable backend license; self-hosting does not establish unrestricted production rights.

## Open questions

- Which client versions, plan and administrator policies apply to the team?
- What survives a representative export: links, attachments, comments, permissions and history?
- How do simultaneous edits, temporary disconnection and member departure behave on the chosen setup?
- The README describes CE as MIT, while root licensing routes backend/native code to separate terms. Resolve exact build and component licensing before deployment.

## Verification plan

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Last checked: 2026-09-15. Recheck by: 2026-10-15.

Content rights: Unlicensed prototype; redistribution decision pending.