Anytype

intermediate

Local-first, E2E encrypted workspace.

Overview

Anytype Heart is the core synchronization infrastructure that powers Anytype's decentralized, local-first workspace ecosystem. Built on the Any-Sync protocol, it enables users to maintain their own sync nodes for enhanced privacy and data sovereignty while participating in Anytype's encrypted object-graph network. This self-hosted node handles peer-to-peer synchronization of encrypted workspace data between Anytype clients without ever accessing the actual content due to end-to-end encryption. This Docker stack deploys an Any-Sync node that connects to Anytype's main network while maintaining full control over your synchronization infrastructure. The node operates as a relay point for your Anytype clients, managing encrypted object synchronization, conflict resolution, and network topology maintenance. Unlike traditional cloud storage, the sync node never decrypts your data - it simply orchestrates the movement of encrypted blocks between your devices. This configuration is ideal for privacy-conscious organizations, teams requiring data sovereignty, and power users who want to eliminate dependency on third-party sync services. By running your own sync infrastructure, you gain complete control over data residency, network topology, and synchronization policies while maintaining compatibility with the broader Anytype ecosystem and its innovative object-relation paradigm.

Key Features

End-to-end encrypted object synchronization without server-side data access
Any-Sync protocol implementation for decentralized workspace coordination
Peer-to-peer node discovery and network topology management
Conflict-free replicated data type (CRDT) synchronization for object graphs
Multi-device workspace state reconciliation across desktop and mobile clients
Encrypted block storage and retrieval for Anytype's object-relation model
Network participant authentication and encrypted channel establishment
Real-time collaboration support through operational transformation

Common Use Cases

1Enterprise teams requiring on-premises workspace synchronization with zero-trust architecture
2Educational institutions managing student and faculty knowledge graphs on controlled infrastructure
3Research organizations synchronizing encrypted project data across distributed teams
4Privacy-focused individuals eliminating dependency on third-party sync services
5Remote teams in regulated industries requiring data residency compliance
6Developer teams managing technical documentation and project knowledge bases locally
7Consulting firms maintaining client-specific workspaces on isolated infrastructure

Prerequisites

Minimum 2GB RAM for efficient object graph synchronization and CRDT operations
Stable internet connection with ports 4830 and 4730 accessible for peer communication
Docker host with persistent storage capability for encrypted block data retention
Anytype desktop or mobile clients configured to connect to custom sync nodes
Understanding of Anytype's object-relation model and workspace concepts
Network configuration allowing P2P connections if deploying in restrictive environments

For development & testing. Review security settings, change default credentials, and test thoroughly before production use. See Terms

docker-compose.yml

1services: 
2  anytype: 
3    image: ghcr.io/anyproto/any-sync-node:latest
4    container_name: anytype-node
5    restart: unless-stopped
6    ports: 
7      - "4830:4830"
8      - "4730:4730"
9    volumes: 
10      - anytype_data:/data
11    environment: 
12      ANY_SYNC_NETWORK: main
13
14volumes: 
15  anytype_data:

.env Template

.env

1# Use Anytype desktop client for full experience

Usage Notes

1Docs: https://tech.anytype.io/
2Self-hosted sync node for Anytype network
3Use with Anytype desktop/mobile clients
4E2E encrypted - server never sees your data
5Objects: notes, tasks, bookmarks, with relations
6Graph view for visualizing connections

Quick Start

terminal

1# 1. Create the compose file
2cat > docker-compose.yml << 'EOF'
3services:
4  anytype:
5    image: ghcr.io/anyproto/any-sync-node:latest
6    container_name: anytype-node
7    restart: unless-stopped
8    ports:
9      - "4830:4830"
10      - "4730:4730"
11    volumes:
12      - anytype_data:/data
13    environment:
14      ANY_SYNC_NETWORK: main
15
16volumes:
17  anytype_data:
18EOF
19
20# 2. Create the .env file
21cat > .env << 'EOF'
22# Use Anytype desktop client for full experience
23EOF
24
25# 3. Start the services
26docker compose up -d
27
28# 4. View logs
29docker compose logs -f

One-Liner

Run this command to download and set up the recipe in one step:

terminal

1curl -fsSL https://docker.recipes/api/recipes/anytype/run | bash

Troubleshooting

Clients cannot connect to sync node: Verify ports 4830 and 4730 are accessible and not blocked by firewall rules
Sync node fails to join ANY_SYNC_NETWORK: Check internet connectivity and ensure the main network is reachable from your host
Object synchronization appears stuck: Restart the container to reset peer connections and reinitialize network topology
High memory usage during sync operations: Increase container memory limits as CRDT operations can be memory-intensive
Anytype clients show offline status: Verify the sync node container is running and check client configuration for correct node address
Data volume permission errors: Ensure the anytype_data volume has appropriate read/write permissions for the container user

Community Notes

Loading notes...

Download Recipe Kit

Get all files in a ready-to-deploy package

Includes docker-compose.yml, .env template, README, and license

Components

anytype-heart

Related Recipes

Ad Space

Shortcuts: C CopyF FavoriteD Download