Tiny server
A self-hosted server for one community, with tinyclient as its app: text channels, direct messages, voice rooms and one picture.
tinyserver is open source under the MIT license and written in Rust. One deployment is one community. Its owner runs it; the tinyclient project does not host it, does not take its credentials, and does not carry its messages. See it in pictures, or read the source on GitHub.
The project is early, and it has had no independent security review. Each page here says what is not built and what is not tested.
Where to start
| You want to | Read |
|---|---|
| Join a server someone invited you to | Join and use a server |
| Start a server for your people | Run a server, then open the media port |
| Decide how members sign in | Sign-in and passkeys |
| Set up roles, channels and invites | Manage a community |
| Keep it running | Operate and upgrade |
| Know what the server can read | Server privacy and security and End-to-end encryption |
What a server does
| Area | What works today |
|---|---|
| Text | Text channels in categories and direct conversations between two members: replies, files, reactions, edit, delete, typing and read state |
| Voice | Voice rooms people drop into, and calls between two members. Mute, deafen and who is speaking. |
| Video | One picture per listener: a screen share, or one other person’s camera |
| Encryption | Calls end to end when every app in the call can. Text and files end to end in conversations created encrypted. |
| Sign-in | No passwords. Passkeys the server checks itself, an OpenID Connect provider, or both. |
| People | Owners, roles with permissions, overrides per room and channel, invites with uses and an expiry |
| Moderation | Server mute and deafen, move, disconnect, timeout, kick, ban and an audit log |
| Files | Uploads scanned before anyone can fetch them; images re-encoded; risky types refused |
| Bots | Application bots that can read and manage rooms and read the member list |
How it fits together
- tinyclient is the app. A member adds the server beside their other networks; tinyclient talks to it directly from their computer.
- tinyserver is one program: an HTTP API, a live socket for events and call setup, the sign-in pages, and the call server.
- Postgres holds accounts, messages and settings. Files live on a volume. ClamAV scans uploads.
- Web traffic reaches the server through a Cloudflare tunnel, or a reverse proxy of your own. Call audio and video go straight to one port on the host.
- tinyclient.io takes no part. Its invite page only opens the app, and the invite’s secret never reaches it.
What it is not
- Not federated. A server is one community, and two servers do not talk to each other.
- Not hosted by the project. Someone runs each server and can read what is not end-to-end encrypted.
- Not usable from a browser. tinyclient is the app; the only pages a server shows are for signing in.
- Not able to carry calls from a host that cannot open a port. A relay is not built yet.
In the repository
These pages cover running and using a server. The contracts an app builds against, and the designs, stay in the repository:
deploy/README.md: every deployment detail, and what each upgrade needsdocs/server.md: the API for server management, messages, files and botsdocs/calls.md: the live socket, calls, and call encryptiondocs/e2ee-text.md: text encryption and device linkingdocs/auth-passkeys.md: passkey sign-in and the move from Pocket IDdocs/privacy/: guarantees, threat model and open findings