Knowledge workspace / PRODUCT DOSSIER

Anytype

Local-first object-based knowledge spaces with encrypted sync and space-level roles.

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

Official website ↗Explore in graph →10 cited claims ↓

Anytype clients and a chosen Anytype or self-hosted network; per-object permission boundaries are excluded. · Source available · Any Source Available License 1.0 for desktop client; allowed-network restrictions and component licenses apply.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?
Immediate sync is documented, but simultaneous same-document co-editing semantics have not been established in this package.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.; Desktop repository revision 14cf1e6efcb4e3bf2d425afe92fdfecc1f603574. · Anytype clients and a chosen Anytype or self-hosted network; per-object permission boundaries are excluded.

Applicability, 2 recheck triggers & verification plan

Applicability

Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.; Desktop repository revision 14cf1e6efcb4e3bf2d425afe92fdfecc1f603574.

Anytype clients and a chosen Anytype or self-hosted network; per-object permission boundaries are excluded.

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 2026-10-15

Verification plan

Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
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 2026-09-15

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Capability claims · 10 / 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 →

Creates pages from composable content blocks.

Scope: Desktop client capabilities.

[1]

Shared knowledge spaceYes

Explore Shared knowledge space →

Shares knowledge within collaborative spaces.

Scope: Membership and editor-seat limits apply.

[3]

Access control

Distinct collaborator rolesYes

Explore Distinct collaborator roles →

Assigns viewer, editor, admin and owner roles.

Scope: Roles apply to a whole space.

[3]

Per-document accessNo

Explore Per-document access →

Cannot assign permissions separately for each object.

Scope: All space members can view every object in that space.

[3]

Organization

Structured records and viewsYes

Explore Structured records and views →

Provides custom Types and structured data views.

Scope: Supported object types and views.

[1]

Continuity & portability

Offline editingYes

Explore Offline editing →

Edits locally and synchronizes when connectivity returns.

Scope: Previously available local content; remote updates wait for connectivity.

[3]

Portable contentYes

Explore Portable content →

Exports content to local formats but omits chats and discussions.

Scope: Desktop export; member references may not survive migration.

[4]

Web publication or public linkYes

Explore Web publication or public link →

Can publish an object as a browser-readable webpage.

Scope: Public publication differs from encrypted private sharing.

[3]

Self-hosted collaborationYes

Explore Self-hosted collaboration →

Supports a self-hosted sync network configuration.

Scope: Configure every device; client license restrictions remain applicable.

[5]

End-to-end encrypted syncYes

Explore End-to-end encrypted sync →

Encrypts shared content before synchronization.

Scope: Keys are shared with invited participants; security not independently audited.

[3]

Unknown · 7 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 · 5

[1]Anytype desktop overview ↗Pinned2026-09-152 / 10 claims

repository · locator & rights

14cf1e6efcb4e3bf2d425afe92fdfecc1f603574

Offline-first storage; blocks; custom Types