What is Ratspeak?
Ratspeak is a family of communication tools built around Reticulum. The desktop and mobile app gives you private messaging, file sharing, Channels, turn-based games and experimental voice calls. You create an identity on your device; there is no account to register or phone number to provide.
Ratspeak is published under the Reticulum License and runs on rsReticulum and rsLXMF, Rust ports of Mark Qvist's Reticulum and LXMF reference implementations; see Licenses.
You can connect over the internet, a local network, Bluetooth or compatible LoRa radios. Which connections you can use depends on your device and setup. Reticulum can work without the public internet, but there still needs to be a usable path between the people or nodes communicating.
New here? Start with Choosing Your Setup, then Install and Platform Setup and Your First Session.
Explore the docs
What is Ratspeak?
Guides for using Ratspeak, Reticulum, LoRa, hardware devices, deployment, and private mesh networking.
Getting started
Choose your setup, install Ratspeak, and send your first message.
Using Ratspeak
Day-to-day guides for messaging, peers, settings, and games.
Concepts
How Reticulum, LXMF, and the Ratspeak ecosystem work under the hood.
Networking
Configure LoRa, Bluetooth, serial, IP, and I2P interfaces.
Hardware
Supported boards, firmware flashing, antennas, and range planning.
Deployment
Deployment patterns from friend groups to city-scale meshes.
Products
App, firmware and library reference pages.
Reference
Configuration reference, IPC API, build instructions, FAQ, and troubleshooting.
What's in the box
- Ratspeak is the desktop and mobile app.
- Ratspeak Handheld is the unified firmware for T-Deck Plus, T-Pager, Cardputer Adv and M9. The available modes depend on the board. It succeeds the historical rsDeck, rsPager and rsCardputer projects.
- rsReticulum and rsLXMF provide the Rust networking and messaging stack, with standalone tools for operators and libraries for developers.
- rsLXST supplies experimental voice and media transport over Reticulum.
- LRGP, LXMFace and Ratkey cover game messages, identity avatars and experimental hardware identity work.
You do not need to install all of these to use the app. The ecosystem guide explains how the pieces fit together and distinguishes standalone releases from the libraries bundled in Ratspeak.
Built on Reticulum
Reticulum handles identities, packets and paths across different kinds of connection. LXMF adds messages and delivery methods. A TCP connection can carry traffic across the internet; a radio connection can carry it without an internet service. Transport nodes can forward packets between those connections.
Direct conversations are end-to-end encrypted. An Offline Inbox uses a propagation node to store recipient-encrypted messages for later pickup. Channels use hubs that can read the messages they distribute. These are different roles, so choose the one that fits the conversation.
A connection is still required to send or receive. Offline Inbox delivery also depends on a reachable propagation node and its storage and retention policy; it cannot guarantee delivery through a disconnected network.
Who it's for
- People who want messaging without a central account or a phone number tied to their identity.
- Field operators using radios where cellular or internet service is unavailable.
- Community network builders connecting neighbors and maintaining transport or propagation nodes.
- Tinkerers, radio operators and developers building tools on Reticulum and LXMF.
For radio hardware, start with RNode and Supported Boards. For an always-on node, see Infrastructure & Ops.
Limits to understand
Ratspeak is in alpha, and handheld firmware is in beta. Voice features are experimental. Check the relevant product and setup pages for platform, hardware and interoperability limits.
Encryption does not make you anonymous. Other nodes can observe network activity, and IP-based connections still use IP addresses. Read Cryptography & Protection before relying on Ratspeak for a particular privacy need.
For questions about current behavior, see the FAQ. If something is not working, use Troubleshooting.
Where to next
- Learn the terminology in Key Concepts & Glossary.
- Choose a connection in Interfaces Overview & Design.
- Read Protocol Architecture if you want to understand the stack.