What's already running after deployment
The one-click template brings up the any-sync stack in Docker: a sync node handling client connections, MongoDB as the primary data store, and Redis for caching and coordination between components. Two ports matter most for connectivity: TCP 33010 for the DRPC protocol and UDP 33020 for QUIC —. Everything restarts automatically on reboot via the container's restart policy.
Connecting your first device
Anytype doesn't have a web admin panel you log into with a username and password — the "access" you need is a network configuration file (client-config.yml), generated during the container's first run. Open the Anytype desktop or mobile app, go to the onboarding screen, click the gear icon in the top corner, choose "Self-hosted" under Networks, and upload that file. Save it, then create a new identity — this identity and every space you build under it now lives exclusively on your own network, separate from any account you may have had on the default Anytype Network.
A few practical notes
Every additional device — laptop, phone, tablet — needs the same client-config.yml uploaded manually; there's no automatic device discovery. If you ever migrated from the free Anytype Network, remember your old spaces stay behind unless you exported and re-imported them under the new identity — the two networks don't share data automatically.