testedknowhowLAB

Find a space, target or capability

Search every research space and the entities inside them.

Knowledge workspace / PRODUCT DOSSIER

AFFiNE

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

Investigation: Where should a small team keep shared knowledge? →

Official website ↗Explore in graph →5 cited claims ↓
AFFiNE clients with a selected cloud or self-hosted backend; pin edition and team entitlements. · Source available · Mixed repository licenses: MIT for much of the code; backend/native paths have separate AFFiNE EE terms and stated exceptions.Revision 2026-09-15.1 · unreviewedNeeds recheck · recheck 2026-10-150 attestations · checked 2026-09-15

What we do not know yet · 4 open gaps

  • 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.

Applies to: 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.

Applicability, 2 recheck triggers & verification plan

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.

Excludes: Executed collaboration, recovery or migration tests; Unlisted third-party plugins and integrations; AI quality, security certification and performance rankings; Unlisted editions and plan entitlements

Recheck when

  • Changes to app versions, plan entitlements, sharing policies or license terms.
  • Changes to offline caching, synchronization, recovery retention or export formats.

Needs recheck · due

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.

Provenance & review

Testedknowhow collaboration research

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

Revision 2026-09-15.1 · unreviewed · checked

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Capability claims · 5 / 17 sourced

Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.

Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.

Collaboration

Document authoringYes
Explore Document authoring →

Combines editable documents and a canvas.

Scope: AFFiNE client; selected build and backend.

[1]
Live co-editingYes
Explore Live co-editing →

Documents real-time collaboration across clients.

Scope: Configured collaboration backend; convergence untested.

[1]
Shared knowledge spaceYes
Explore Shared knowledge space →

Provides a shared team document workspace.

Scope: Team plan and backend edition must be pinned.

[4]

Organization

Structured records and viewsYes
Explore Structured records and views →

Supports multi-view databases as content blocks.

Scope: Supported client data views; no database-engine claim.

[1]

Continuity & portability

Self-hosted collaborationYes
Explore Self-hosted collaboration →

Documents operating an AFFiNE deployment yourself.

Scope: Pin image, edition and applicable backend license; self-hosting does not establish unrestricted production rights.

[1]

Unknown · 12 capabilities without evidence

Interface images & local attachments
Screenshots & attachments
Image index

Official project screenshots and your own reference images. Images illustrate a UI; they do not verify feature behavior. Uploads stay in this browser.

No screenshots gathered yet.

Sources · 4

[1]AFFiNE repository overview ↗Pinned4 / 5 claims
repository · locator & rights

2af30773aecd567f09b346e7b72fc69143144057

Features; local-first and real-time collaboration; self-hosting

Link and original paraphrase only; upstream rights retained.

[2]AFFiNE license routing ↗Pinned0 / 5 claims
repository · locator & rights

2af30773aecd567f09b346e7b72fc69143144057

Backend/native paths; MIT remainder

Link and original paraphrase only; upstream rights retained.

[3]AFFiNE backend license ↗Pinned0 / 5 claims
repository · locator & rights

2af30773aecd567f09b346e7b72fc69143144057

Production subscription terms; Community Edition and client-side exceptions

Link and original paraphrase only; upstream rights retained.

[4]AFFiNE team workspaces ↗1 / 5 claims
vendor-documentation · locator & rights

Team docs, database and collaboration; cloud versus self-hosted

Link and original paraphrase only; upstream rights retained.