tinyclient
One tiny, private app for all your chats.
For macOS on Apple silicon, Linux and Windows · Free and open source
Linux: .deb for Debian and Ubuntu · .rpm for Fedora and openSUSE · AppImage · .tar.gz
One inbox for every network
The app
The parts you use every day
Reading, replies, reactions and calls work the way each network does them. Anything not built yet opens in the official app, on that item.
-

One inbox
Unread from every network in one list, newest first.
-

Each network’s own sidebar
Servers, workspaces, folders and teams, the way each network lays them out.
-

Voice calls
Discord calls, with a camera and Go Live, and a Tiny room you run. A Tiny call is end-to-end encrypted when that server offers it. Echo cancellation is on.
-

Threads beside the chat
A thread opens in a pane, so the conversation stays where you left it.
-

Every emoji
Search them all. In a server, its own emoji come first.
-

Your phone’s texts
Android Messages, paired the way messages.google.com is. SMS and RCS go through your phone.
Principles
Small on purpose
- TinyNative. Not a browser in a box.
- PrivateNo tinyclient server or account. No telemetry.
- SecureSessions live in your OS keychain.
- OpenMIT licensed. Built in public.
Size
Five apps, or one.
The official apps use 1.4 GB of RAM and 3.1 GB of disk. tinyclient 0.2.0 used 57 MB and 55 MB.
In memory
RAM in use while signed in, measured together on an M3 Pro, 14 October 2026. tinyclient is 0.2.0. Activity Monitor’s Memory column, which also counts compressed memory, is 3.9 GB for the five and 91 MB for tinyclient. Later releases have not been measured again yet. How we measure →
On disk
App size on disk, macOS, from each vendor’s installer, 14 October 2026. Slack and Telegram ship one app for Apple silicon and Intel; tinyclient’s figure is its Apple silicon build of 0.2.0, not yet measured again for later releases. How we measure →
Keyboard
Built for the keyboard
Jump to any conversation, walk through what’s unread and run a call from the keyboard. On Linux and Windows, Command is Ctrl and Option is Alt.
- Quick Switcher⌘K
- Next unread⌥⇧↓
- Inbox, People⌘1/⌘2
- Back, Forward⌘[/⌘]
- Mark as read⇧Esc
- Mute in a call⇧⌘M
- All shortcuts⌘/
Privacy
Your messages go to the network. Nowhere else.
tinyclient sends us nothing: no telemetry, no analytics, no crash upload. It leaves out the usage tracking the official apps carry, too.
- Nothing sent to us
- No telemetry or analytics
- Keys in your keychain
Network by network
What works where
The goal is everything the official apps do. Here is where each network stands today.
| Network | Sign in | Reactions | Edit, delete | Files | Voice | Video | Screen share |
|---|---|---|---|---|---|---|---|
| Slack’s web sign-in | Yes | Yes | Yes | Not yet | Not yet | Not yet | |
| Discord’s web sign-in | Yes | Yes | Yes | In tinyclient | Camera | Go Live | |
| Microsoft sign-in | Yes | Yes | Through OneDrive | Not yet | Not yet | Not yet | |
| QR code or phone number | Yes | Yes | Yes | Not yet | Not yet | Not yet | |
| Linked as a device | Yes | Your own | Named, not shown | Not yet | Not yet | Not yet | |
| Paired with your phone | Yes | Not yet | Photos shown | On the phone | On the phone | Not offered | |
| In your browser | Yes | Yes | Yes | In tinyclient | One picture | Win, macOS, Linux |
Not built yet: video and screen share on Slack, Teams, Telegram, Signal and Messages. A Discord call carries a camera, and Go Live sends the screen. A Tiny room shows one picture, a share or one other person’s camera. The camera and screen share send on Windows, macOS and Linux. Signal photos and files are a labelled line, and Signal calls are not built. Teams personal accounts are not built. A voice message can be recorded on Telegram only.
Your own server
Tiny server
A server you run for your own community, with tinyclient as its app. Text, voice and one picture, on one Docker Compose file. Open source, MIT.
-

Rooms and channels
Voice rooms and text channels in categories, and who is in each. Direct messages between members.
-

Voice, and one picture
Drop into a room. Mute, deafen and see who is speaking. A room can show a screen share or one camera.
-

End-to-end encrypted
When every app in the call can, the server cannot hear it. A call code and safety numbers let you check.
-

Moderation
Right-click anyone: server mute, move, disconnect, timeout, kick or ban. Every one is in the audit log.
-

Roles and permissions
Drag roles into order and switch on what each may do, for the whole server or one room.
-

Invites, and no passwords
An invite gives roles, a number of uses and an expiry. People sign in with a passkey, in their browser.
Before you install
Good questions
Will my computer warn me the first time?
Yes. The macOS app is signed ad hoc, not notarized by Apple: open System Settings › Privacy & Security and choose Open Anyway. The Windows installer is not code-signed, so SmartScreen may say Windows protected your PC: choose More info › Run anyway. Installing →
Do the networks allow it?
Telegram welcomes third-party clients. Discord’s terms disallow them on user accounts; its enforcement goes after automation, self-bots and spam, and tinyclient automates nothing. Workspaces on Slack and Teams may have their own policy, and an organization can turn third-party sign-ins off on Teams. Networks & terms →
Does it connect to anything besides the networks?
One update check: about once an hour while the window is open, it asks GitHub whether a newer release exists, and sends only tinyclient/<version>. If a Wikipedia link has no preview, the window asks Wikipedia for a summary (no message text). When a Tiny call turns on screen share, camera, or watching a picture, and Cisco’s OpenH264 library is not already on disk, mediad downloads it from Cisco; a voice-only call does not. If you add a Tiny server, it also talks to that server, and your browser to the server’s sign-in page. No analytics, no crash upload. Privacy & security →
Is what it stores encrypted?
Sessions live in your system’s keychain, and Signal’s keys are sealed with a key held only there. On a Tiny server, conversations created encrypted seal message text and sealed files end to end (from v0.2.37); plaintext conversations are still readable by that server. The local message and media cache is not encrypted by tinyclient, so keep your disk encryption on: FileVault, BitLocker or LUKS.
Will it notify me?
Yes, for direct messages and mentions by default, even with the window closed. One notification per conversation, taken away once you read it. Calls ring with Accept and Decline. Settings › Notifications chooses what notifies, how much it shows, its sounds and quiet hours. The taskbar button or Dock icon shows the count. Notifications →
How does it update?
While the window is open, it asks GitHub about once an hour whether a newer release exists, and tells you when one does. With automatic install on, it downloads the release, checks it against that release’s checksums, and replaces itself when you quit. On Windows, a failed swap is rolled back and reported in About. The Linux packages are not in a repository, so install a newer download the same way. Updates →
I want another network added.
Ask for it on Discord or in a GitHub issue, so others can add their voice and we can see what people want most. Every network is one adapter in chatd, and adding one is a good way in: say on Discord that you’d like to build it, and it’s yours until it ships. Contributing →
Download
Free, with no account to make
-
macOS
Apple silicon, macOS 13 or later. A disk image.
Download for macOS -
Linux
x86_64 and arm64, as .deb, .rpm, AppImage or .tar.gz.
Download for Linux -
Windows
x86_64. An installer that needs no administrator.
Download for Windows
Every release is built by GitHub Actions from the public source. Checksums · All releases · Build it yourself
Early, and built in the open.
We’re building a community around one goal: the best chat client there is, with every feature of the official apps.