01 · IPHONE · IOS 15+◼
iPhone. Free on the App Store.
iOS 15 or later. Accountless — no sign-up, no email, nothing to create.
Radio over Bluetooth (RNode) is currently an iPhone feature — see Troubleshooting for pairing notes.
02 · ANDROID · 7.0 AND UP◼
Android. Direct APK.
Android 7.0 and up. Take the first file — a 32-bit phone will refuse it, and the second will install.
First install: open the APK and allow installs from your browser when Android asks — once.
APK and Play are separate installs. Android identifies an app by who signed it, and these APKs are signed by us while the Google Play copy is signed by Google. Android will not install one over the other, so an APK install cannot update itself from Play later, and vice versa. Pick one and stay with it. To switch, first use Settings → Identity backup → Export identity backup to save a .stolobk file, then uninstall, install the other, and restore from it — otherwise you lose your identity and your messages.
03 · MACOS · APPLE SILICON◼
macOS. For M-series Macs.
M1 or later. Open the image, drag Stolo to Applications.
First launch: open the .dmg, drag Stolo to Applications, double-click. Signed and notarized by Stolo Systems Inc. — macOS asks once to confirm, then it just opens.
04 · WINDOWS · 10/11 · 64-BIT◼
Windows. Installer or portable.
64-bit Windows 10/11. The installer needs no admin rights; the portable zip runs from anywhere — unzip and start Stolo\stolo.exe.
First run: the builds are not yet code-signed, so SmartScreen shows “Windows protected your PC” — click More info, then Run anyway. When the firewall asks, allow access: that is the mesh talking to peers on your network.
05 · LINUX · X86-64◼
Linux. AppImage or tarball.
GTK 3. The AppImage is one file and needs FUSE (most distributions ship it); the tarball extracts and runs as ./stolo. A keyring — GNOME Keyring or KWallet — protects the message-database key when one is available.
First run: make the AppImage executable — chmod +x, or Properties → allow executing — then run it.
06 · VERIFY◼
Check what you downloaded.
SHA-256 for every file, also published at dl.stolo.io/SHA256SUMS. Compare with shasum -a 256 <file> on macOS/Linux or certutil -hashfile <file> SHA256 on Windows.
b6e8f10dc129a5ad52485b9fb4e07a91c668b074c0d1df6904cea98cbf8b7d79 Stolo-Android-arm64-v8a.apk
a92e0be9ce877ec4d7aa34e106ad8cb4526b6e0b112baa1f4dd8809146c9a138 Stolo-Android-armeabi-v7a.apk
9c05f7ac3c9e192e269f307af595afc5663e65e19912e36f4989e4e301ce9e86 Stolo-Linux-x64.tar.gz
cd3ed2c4c8b42ece13e81dfca378cd04d38d40be8a3ea3db71df1ef4d759f93c Stolo-Linux-x86_64.AppImage
e1e7062de2acd2ef9664f7c81723ccb6dc277dc4e2ee9a305737e9c74c815be3 Stolo-macOS-arm64.dmg
1bbe2e3ebeacb683d43e8ded38c2a9388410f71737ec01cb2955f847931cabdf Stolo-Setup-x64.exe
2cf92bc9f06bb5e2077a75d072da124987de307bfe793edb998d32fa18f51357 Stolo-Windows-x64-portable.zip
07 · NOTES◼
New builds, honest caveats.
The Android, Windows, and Linux builds are new. Every desktop build talks to RNode radios over USB; the files are large because the whole world basemap and the mesh stack ship inside the app — Stolo works with no connectivity at all.
Something misbehave? Email [email protected] with your platform and what you saw — that is usually enough for us to spot it.