Do I need to self-host to use Tusile?
No. You can create a free hosted server directly from the app — no server, no config files, no DevOps needed. You can also join existing public community servers with one Tusile identity.
What is a free hosted server?
When you tap + and choose Free (Hosted), Tusile creates and runs the community server for you on our infrastructure. You get text channels, voice/video, screen share, roles, and file uploads — ready in seconds. Every in-app feature is included; the free hosted tier supports up to 10 members and 50 MB file uploads, can be listed in public discovery, and always receives push notifications. It shares a machine with other free communities, so while that machine is busy, calls and screen shares started on it run at reduced screen video and voice quality for everyone until it settles. Nothing is switched off by that; the 10-member limit is the only thing that refuses a join.
What is the difference between a hosted server and a self-hosted server?
Hosted (free): Tusile runs the server. No setup required. Up to 10 members and 50 MB uploads; can be listed in public discovery; always receives push notifications. Tusile stores the data.
Self-hosted: You run the server on your own VPS or hardware. You control data and retention. Unlimited members and features for free, listed in public discovery up to 25 members; a paid license (from $15/mo) keeps larger servers listed. Requires Docker and a domain.
What should I host myself if I choose self-hosting?
You self-host the community-server stack (community API + LiveKit + Caddy).
Where is my data stored?
Core Server (the shared Tusile identity service) holds your account, friends list, direct messages (text and DM file attachments), and profile avatars. That data lives in Tusile’s infrastructure, not on community servers you join. One-to-one direct messages are end-to-end encrypted, so what Core holds for those is ciphertext it cannot read; group direct messages, and anything sent before encryption was turned on, are stored as content. See the Privacy Policy for what stays visible either way.
Tusile-hosted community servers store channels, messages, file attachments, roles, and related content on Tusile’s infrastructure. You can delete your hosted server and all its data at any time from the app.
Self-hosted community servers store channels, messages, files, and voice metadata on your own infrastructure — typically Postgres plus local disk or S3. You control retention and backups; see Backup & restore for pg_dump, file exports, and moving to a new host.
Per-community server nickname and server avatar live on that community server only, not on Core. Direct messages always use your global Core display name and picture.
Can I use a free domain?
Yes. Dynamic DNS options such as Duck DNS or No-IP work for hobby/community setups.
Which ports are mandatory?
At minimum: 80/tcp, 443/tcp, 7880/tcp, 7881/tcp, and 50000-50060/udp for reliable voice/video.
How do upgrades work?
Upgrade by pulling newer container images and restarting compose. Community-server migrations run automatically at startup. Take a database backup first; see Backup & restore.