1
Step 1Open the server Apps tab
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.
Back to all templates
Any-Sync Node
Application512MB+ RAM
Self-hosted sync node for Anytype — minimal single-container setup. Production deployments typically require a multi-service stack (coordinator, file node, consensus node, MongoDB, Redis, MinIO).
applicationnotesanysyncnodeopen-sourceself-hosteddocker
Deploy Any-Sync Node in 3 Steps
1
Connect Your VPS
Add your server credentials to Server Compass
2
Select Any-Sync Node
Choose from our template library
3
Deploy & Configure
Fill in settings and click Deploy
No Docker knowledge required
Step-by-step deployment guide
Deploy Anytype Self-Hosted Sync on a VPS with Server Compass
Use the Anytype Self-Hosted Sync template in Server Compass to deploy the official multi-service Anytype sync network on your VPS, then verify the generated client config and netcheck service.
About 10 minutesBrowser verified
2
Step 2Choose an app template
Click New App and choose the template deployment path so Server Compass can load the built-in catalog.
3
Step 3Search for Anytype Self-Hosted Sync
Use the template picker search to find Anytype Self-Hosted Sync in the Server Compass template catalog.
4
Step 4Select the Anytype Self-Hosted Sync template
Choose the Anytype Self-Hosted Sync template. Server Compass fills the coordinator, filenode, consensus node, three sync nodes, MongoDB, Redis, MinIO, config generator, and netcheck services.
5
Step 5Review the Anytype Self-Hosted Sync settings
Confirm the app name and compose services. In this run, the app was named anytype-demo; Anytype sync exposes service ports instead of a browser UI.
6
Step 6Deploy Anytype Self-Hosted Sync
Review the generated public host, MinIO credentials, sync ports, and compose services, then click Deploy.
7
Step 7Watch the deployment progress
Keep the deployment modal open while Server Compass clones the official Anytype compose support files, uploads the compose file, builds the config generator, pulls images, starts services, and verifies the stack.
8
Step 8Confirm Anytype Self-Hosted Sync is running
After deployment finishes, return to the Apps tab and confirm the Anytype Self-Hosted Sync app is marked Running.
9
Step 9Verify Anytype Self-Hosted Sync from the VPS
Verify the sync containers are running, the config generator and coordinator bootstrap completed, the generated client.yml lists the VPS addresses, and netcheck reports success.
After Any-Sync Node Opens
- Copy the generated etc/client.yml file from the stack directory and import it into Anytype clients.
- Open firewall access for TCP 1001-1006 and UDP 1011-1016 only where your Anytype clients need to connect.
- Keep MongoDB, Redis, MinIO console, metrics, and node API ports unpublished unless you have a specific private-network reason to expose them.
- Back up the storage and etc directories before relying on the sync network for production notes.
Verified Result
The sync nodes, coordinator, filenode, consensus node, MongoDB, Redis, MinIO, and netcheck containers were running; init and coordinator bootstrap exited successfully; client.yml existed; and netcheck logged success.
Any-Sync Node deployment questions
What does the Anytype Self-Hosted Sync template deploy?
It deploys the official Anytype any-sync stack with three sync nodes, coordinator, filenode, consensus node, MongoDB, Redis, MinIO, config generation, and netcheck.
Which port did the tutorial use?
Anytype sync does not expose a browser UI. The template uses TCP ports 1001-1006 plus UDP ports 1011-1016 for sync traffic; internal API, metrics, database, cache, and MinIO console ports are not published.
Does Anytype Self-Hosted Sync need setup after deployment?
Yes. After deployment, copy the generated client.yml from the VPS and configure Anytype clients to use that private sync network.
Should this become a blog post?
No. The deployment guide should live on the Anytype Self-Hosted Sync template detail page and be linked from the reusable template deployment docs page.
After Deployment
After deploying Any-Sync Node with Server Compass, complete these steps to finish setup
1
Review the official Anytype self-hosting docs at https://tech.anytype.io/
2
For a complete production setup, deploy the full any-sync-dockercompose stack
3
Configure DNS and TLS for client connections
Need help? Check out our documentation for detailed guides.
Any-Sync Node FAQ
Common questions about self-hosting Any-Sync Node
How do I deploy Any-Sync Node with Server Compass?
Simply download Server Compass, connect to your VPS, and select Any-Sync Node from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.
What are the system requirements for Any-Sync Node?
Any-Sync Node requires a minimum of 512MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.
Can I migrate my existing Any-Sync Node data?
Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard Any-Sync Node backup and restore procedures.
How do I update Any-Sync Node to the latest version?
Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest Any-Sync Node image will be pulled and deployed with zero downtime.
Is Any-Sync Node free to self-host?
Any-Sync Node is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.
Ready to Self-Host Any-Sync Node?
Download Server Compass and deploy Any-Sync Node to your VPS in under 3 minutes. No Docker expertise required.
Download Server Compass