Download
Get Etoki
Signed, compiled artifacts — the Android app and the server binaries you need to run your own relays.
Android
2-hop routing, multiple profiles, groups, files, voice and video calls, the Etoki push-to-talk tab, panic mode and app lock.
- Requires
- Android 7.0+
- Architectures
- arm64-v8a, x86_64
- File
- etoki-0.1.6.apk
- Play Store
- No — direct APK
SHA-256 4b921ade75f590be461b7ac825229e06ab458f34669f71c40cd1e16174e29060
Installing
- 1Download the APK to your phone, or copy it across with adb.
- 2Open it. Android will ask you to allow installs from this source — allow it for your browser or file manager.
- 3Install, then open Etoki and pick a display name.
- 4Optional: point it at your own relays under Settings → Servers & relays.
Staying updated
The app checks for updates itself. Each update manifest is Ed25519-signed with a key pinned inside the app, and the downloaded APK must match the SHA-256 in that signed manifest before Android is asked to install it.
A network attacker can therefore block an update, but cannot substitute one.
Servers
Server binaries
Everything needed to run your own relays. Each archive contains the etoki and etoki-botrelay binaries — no runtime dependencies, no build toolchain.
Both archives are statically linked against musl: one file per binary, no libc to match, nothing to install alongside them.
Linux x86_64
etoki-server-0.1.0-linux-x86_64.tar.gz
SHA-256 691f9f457fc56c33bdce73140296c6d2f893cd0126baa758c873d157af2abb0a
Linux arm64
etoki-server-0.1.0-linux-arm64.tar.gz
SHA-256 23c7e8a08f2fb863a0a379c16b70ff21cbc478ee5081f321fe5a87e2fa52c69c
Verify your download
# Every artifact's digest is listed in one file next to them.
# Fetch it, then let sha256sum do the comparison for you.
curl -sO https://etoki.chat/download/SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS
# Or check a single file by eye against the digest on this page
sha256sum etoki-0.1.6.apkIf the checksum does not match, do not install the file.
Now stand up your relays
A fresh Ubuntu 24.04 VPS to a working router, file relay, directory and TURN server — in six steps, using the binaries above.
iOS and desktop clients are not available yet. The protocol, the Rust core and the headless daemon are cross-platform, so those clients are a matter of build effort rather than redesign.
