RETICULUM RESILIENT RESPONSE TACTICAL KIT

Democratizing Situational Awareness

R³AKT brings sovereign situational awareness to the field with REM, RCH and YARA. Fabric, formerly LXMF-rs, provides the communication foundation. FreeTAKTeam’s Rust implementation of Reticulum (RNS) and LXMF includes reusable libraries, a typed SDK and daemons.

Watch the reveal trailer
End-to-end encryption Offline-first Open source
R³AKT // REM
TEAM 04OPERATIONAL
R³AKT // RCHNODE ONLINE
12 peers04 routes
RNode
TCP
TAK
MESH ACTIVE
NETWORK ILLUSTRATION
R³AKT ECOSYSTEMANDROID CLIENTFabric / RUST RNSRETICULUM + LXMFRADIO / TCP / LORAOPEN SOURCE

REVEAL TRAILER

When every second counts.

Watch on YouTube

THE FOUNDATION / FREETAKTEAM

Our RNS implementation.
Reticulum, in Rust.

Fabric is FreeTAKTeam’s reusable communication infrastructure, formerly known as LXMF-rs. Its current Rust implementation of Reticulum (RNS) and LXMF connects R3AKT applications and can also be used independently.

Published · v0.16.1

RNS + LXMF + SDK

Communication infrastructure in Rust. Reusable libraries, a typed SDK, daemons and developer tools for Reticulum and LXMF.

01 / NETWORK

Reticulum networking in Rust

Identity and destination handling, transport, interfaces, links, channels and resources. The reticulum-rs crates expose the RNS implementation directly to applications.

02 / MESSAGE

LXMF messaging and delivery

Wire formats, direct and propagated messaging, delivery states and opt-in durable custody. The same workspace provides the messaging layer above RNS.

03 / BUILD

Libraries, SDK and daemons

22 public packages, including the new durable event broker, plus a typed SDK, reticulumd and command-line tools. Choose native libraries or a daemon API for your application.

REM

Embeds the Rust Reticulum/LXMF runtime in the Android field client.

RCH 3.0 / Rust

The Rust preview connects coordination services to reticulumd through the typed SDK and ZeroMQ. Published RCH 2.9.6 uses the Python runtime by default.

YARA

Exercises the Rust daemon through a MeshChat-compatible HTTP/WebSocket interface.

Compatibility is backed by versioned tests and field evidence. The stable reference baseline is Reticulum 1.5.2 and LXMF 0.9.6; selected 1.5.5 updates do not establish full forward parity. Hardware and embedded support vary by target.

MEASURED / NOV 2026

Put the stack
to the test.

Compare Fabric’s Reticulum/LXMF implementation, measured as LXMF-rs, with the Python reference across 18 matched workloads. Switch metrics to see how the results change.

RUST / PYTHON COMPARISON

Performance by workload

P50 median latency · P95 / P99 tail latencyP50 · Lower is better
  1. LXMF message decode + verify
    Rust 2.71×
    Rust 33 µsPython 89.44 µs
  2. LXMF message encode + sign
    Rust 2.69×
    Rust 13.83 µsPython 37.22 µs
  3. LXMF large message decode + verify
    Rust 2.59×
    Rust 36.59 µsPython 94.59 µs
  4. LXMF large message encode + sign
    Rust 2.14×
    Rust 21.18 µsPython 45.26 µs
  5. LXMF resource-sized message decode + verify
    Rust 1.89×
    Rust 63.36 µsPython 119.79 µs
  6. LXMF resource-sized message encode + sign
    Rust 1.30×
    Rust 65.72 µsPython 85.59 µs
  7. Reticulum packet pack
    Rust 141.84×
    Rust 14.6 nsPython 2.07 µs
  8. Reticulum packet unpack
    Rust 46.47×
    Rust 26.26 nsPython 1.22 µs
  9. Reticulum resource segmentation 16 KiB
    Rust 2.71×
    Rust 1.1 µsPython 2.98 µs
  10. Reticulum resource reassembly 16 KiB
    Rust 2.43×
    Rust 222.82 nsPython 541 ns
  11. Reticulum announce create
    Rust 2.30×
    Rust 14.2 µsPython 32.7 µs
  12. Reticulum announce validate
    Rust 2.33×
    Rust 34.83 µsPython 81.26 µs
  13. Reticulum announce validate batch 64
    Rust 2.42×
    Rust 2.22 msPython 5.36 ms
  14. Reticulum identity sign
    Rust 1.77×
    Rust 18.53 µsPython 32.78 µs
  15. Reticulum identity verify
    Rust 2.15×
    Rust 35.29 µsPython 75.92 µs
  16. Reticulum identity encrypt
    Rust 1.35×
    Rust 52.48 µsPython 70.98 µs
  17. Reticulum identity decrypt
    Rust 1.03×
    Rust 38.35 µsPython 39.52 µs
  18. Reticulum resource request window
    Rust 111.06×
    Rust 20.84 nsPython 2.31 µs

Bar length shows the speed ratio on a logarithmic scale: 1× means equal performance. The measured values are shown alongside each bar.

Intel Core Ultra 7 165H · Linux x86_64 · Rust 1.99.1 · Python 3.14.4

Five interleaved runs with equivalent signing, verification and cache behavior. Python uses the PyCA cryptography backend. These local tests measure specific operations; radio range and whole-system performance require separate tests.

01 / THE PLATFORM

One product family.
An expanding field ecosystem.

From the operator’s device to the coordination node: explore published apps, testing previews and the next integrations.

R3AKT / REM RELEASE · 1.6.2

MOBILE CLIENT / ANDROID

Reticulum Emergency Management

The field application for communications, team location and a shared operational picture over Reticulum.

  • 01 Encrypted chat and peer discovery
  • 02 Dashboard, events and team status
  • 03 Shared markers and provisional sensor geometry
  • 04 RNode and radio link support
R3AKT / RCH PYTHON · 2.9.6

COMMUNITY HUB / SERVER

Reticulum Community Hub

The Python edition provides desktop packages. The separate RCH 3.0 Rust preview includes a matched server, UI, TAK service and Reticulum daemon in its current Linux AMD64 packages.

PUBLISHED / Python 2.9.6 · PREVIEW / Rust 3.0.0-preview.38

  • 01 Shared topics, groups and missions
  • 02 Telemetry and operational picture
  • 03 Federation and TAK interoperability
  • 04 Cross-platform server and desktop

02 / CAPABILITIES & ROADMAP

Available today.
Taking shape next.

From Android and desktop to radios, wearables and field sensors. Follow what is released, what you can test and what comes next.

ROADMAP UPDATE /

Preview builds are for testing. Features in development have no committed release date.

15 capabilities shown

Publishedv0.16.1

FOUNDATION / NETWORK STACK

Our Reticulum and LXMF implementation in Rust.

Fabric, formerly LXMF-rs, is FreeTAKTeam’s reusable communication infrastructure. Its Rust implementation of RNS and LXMF powers REM, RCH Rust and YARA. The stable release aligns 22 public packages and adds a reusable durable event broker, more efficient propagation storage, and readiness notifications for reticulumd under systemd. Packages are available for Linux, macOS and Windows.

Fabric release & downloads
Previewv0.16.2-rc.1

FOUNDATION / NETWORK STACK

Fabric release candidate

Test the next maintenance update.

The candidate reclaims idle SDK sessions while preserving durable identities and accepted work. It also updates SQLite and rustix and fixes interface and shutdown behavior. Use the stable release for the standard distribution.

Candidate packages & notes
Published1.6.2

ANDROID / FIELD COORDINATION

A shared picture, from your phone.

Create and share persistent map objects with your active team. REM 1.6.2 also displays provisional R3S/1 sensor geometry and origin positions from authorized plugins. It runs on LXMF-rs 0.16.1; the Complete APK includes four optional plugin installers, while Light omits them.

Release & Android downloads
Published2.9.6

PYTHON / COMMUNITY HUB

RCH — Python edition

The released Python-based community hub.

Published Python-based RCH package with group and topic communications, mission data, telemetry, files, chat, maps and TAK integration. Release 2.9.6 keeps the Python runtime as the default; its optional Rust mission-sync bridge is disabled by default. Desktop packages are available for Windows, macOS and Linux.

Python release & downloads
Preview3.0.0-preview.38

RUST / COMMUNITY HUB

RCH 3.0 — Rust edition

Your community's coordination node.

Preview.38 ships Linux AMD64 packages with the UI, RCH server, TAK service and matching LXMF-rs 0.16.2-rc.1 daemon. It adds SDK session recovery that preserves durable custody and team-scoped mission commands. Debian upgrade and restart checks passed; physical radio and sustained production operation still need qualification.

Linux AMD64 packages & notes
Previewv1.0.0-beta.3

DESKTOP / RETICULUM MESSAGING

YARA

A practical window into the Rust mesh.

Yet Another Reticulum Application is a MeshChat-compatible desktop messenger with a bundled Rust daemon. Beta.3 adds separate identity profiles and a Backbone Client interface. New profiles connect to the R3AKT backbone by default; existing interfaces stay as saved. Unsigned beta builds are available for Windows, macOS and Linux, including Raspberry Pi OS 64-bit.

Download the desktop beta
Preview

WEARABLE / REM TACTICAL

Amazfit T-Rex 2

Keep essential status on your wrist.

REM Tactical 1.3.29 and REM Sync 0.1.32 have documented Zepp build and setup steps. Tap REM on the watch to opt into live status through the companion and Android plugin. Compass, altitude, pressure, heart rate and battery work locally where supported. The source build is available; Zepp Store availability is unconfirmed.

Watch face & companion source
Published1.1.5

ANDROID / WEARABLE BRIDGE

REM Watch Status plugin

Bring REM status to the watch face.

The signed Android plugin ships with REM Complete and as a separate APK. It exposes connection, operator, team and event status locally to REM Sync, which relays it to the T-Rex 2 watch face. The Zepp companion and watch face are installed separately.

Download Watch Status APK
Preview0.2.0-beta.2

RADIO / REM PLUGIN

goTenna Mesh beta

Another connection for the field.

The optional Android beta pairs with goTenna Mesh over Bluetooth LE to exchange addressed chat, MECP event codes and positions. Forwarding to public Mesh is off by default. Radio headers are plaintext, sender claims are unverified, and physical range and delivery still need qualification.

Download the beta APK
Published0.4.5

OBSERVATION / REM PLUGIN

ATN BinoX & rangefinders

From an observation to a shared point.

Connect ATN BinoX 4K over Bluetooth to turn measurements into REM markers and show permitted points on the BinoX display. Version 0.4.5 updates the native build for 16 KiB alignment and ships with REM 1.6.2. Other models and firmware need separate validation.

Download ATN Rangefinder APK
In development

NIGHT VISION / LIVE VIDEO

Night vision streaming

Live video and audio from an NV30 night-vision device.

A local Wi-Fi test kept the NV30’s RTSP stream connected for 10 minutes, with some missing and corrupt frames. Relaying the feed to remote viewers via MediaMTX is planned.

NV30 streaming test notes
In development

OPTICS / REM PLUGIN

ATN BinoX video streaming

Bring the BinoX 4K’s live view into REM over Wi-Fi.

Local RTSP playback from the BinoX 4K was verified on a laptop. The ATN plugin roadmap starts with live video and an on-screen overlay in REM, followed by a MediaMTX relay for remote viewers.

BinoX live-view specification
In development

DRONES / RETICULUM CONTROL

Drone control over Reticulum

Extend the mesh to drone operations.

Drone command and status exchange over Reticulum is under development for the R³AKT ecosystem. Supported vehicles, available controls, link requirements and field-validation results will be documented as the integration progresses.

Development updates to follow

Published

ANDROID / EXTENSIONS

REM plugin system

Add a capability with explicit trust.

REM Complete includes optional BLE Heart Rate, Watch Status, ATN Rangefinder and goTenna Mesh beta installers. Each plugin is also available as a separate APK. Approve the publisher and grant only the capabilities you want to enable.

Plugin system & SDK
Published1.0.1

ANDROID / SENSOR

BLE Heart Rate plugin

Read heart rate from a Bluetooth sensor.

The optional REM plugin connects to a BLE heart-rate sensor. Version 1.0.1 improves recovery when Bluetooth connection setup fails and releases monitoring resources when the Android service stops.

Download BLE Heart Rate APK
BINOCULARS ↔ SHARED MAP

BinoX measurements → REM markers → team replication. Selected and permitted nearby REM points → BinoX display.

Set up the BinoX plugin ↗

03 / REM IN PRACTICE

Know what to do
when it counts.

REM is emergency coordination for families, neighbors, farms, outdoor groups and small trusted teams when normal communications are limited or overloaded.

PREPARE
CONNECT
REPORT
COORDINATE
01READY

Prepare before it matters

Check the Ready indicator, choose a clear call sign, save trusted peers and run a short communication test before an emergency.

02STATUS

Report condition at a glance

Action Messages summarize security, capability, supplies and power, health, movement and communications as green, yellow, red or unknown.

03EVENTS

Keep the timeline clear

MECP events turn clear choices into compact emergency codes. Household reports show All Home, Someone Missing, Evacuated or Needs Help; SOS activation and cancellation also appear as events.

04TASKS

Turn plans into checklists

Prepare power-outage, evacuation and shelter-in-place playbooks while conditions are calm. Under stress, follow tasks instead of relying on memory.

05MAP

Share the operational picture

Create and share map markers with your active team. Team membership controls operational replication; saved contacts outside the team can still chat and receive household status and SOS.

06SOS

Escalate real distress

SOS can send trusted peers an emergency message, battery state and location, with repeated updates while the emergency remains active.

COMMON WORKFLOWS

One shared picture. Six practical situations.

Chat handles specific one-to-one details. Events keep the group timeline concise. The Dashboard turns structured reports into a quick view of who is safe, limited or needs help.

01
Power outage

Report limited power, check batteries and generator, reduce loads and confirm group status.

02
Evacuation

Coordinate routes, people, medication, pets, fuel and destination check-ins.

03
Shelter in place

Schedule check-ins and track supplies, health and communications without repetitive chat.

04
Severe weather

Report blocked roads, flooding, visibility, air quality and local resource needs.

05
Outdoor groups

Coordinate camp, trail conditions, delays, rest stops and safe return when separated.

06
Communications drill

Once a month: check Ready, announce, confirm peers, send chat and test events, map and SOS safely.

REM supports your trusted group. It does not replace emergency services.

If 911 or official assistance is available, use it. Test SOS only with a clear drill warning, agree location-sharing rules in advance and keep paper contacts, rally points and fallback communications.

04 / USE CASES

Built for the real world.

When the network is intermittent, coordination cannot be.

01

FIELD OPS

Field operations

Positions, team status, events and essential messages in one shared operational picture.

02

EMERGENCY

Emergency response

Structured communications and operational checklists when Internet or mobile networks are unreliable.

03

COMMUNITY

Resilient communities

An independent network to coordinate local groups, volunteers and distributed infrastructure.

04

INTEGRATION

Interoperability

Connect Reticulum nodes, TAK systems and Meshtastic networks without locking operators to one transport.

05 / HOW IT WORKS

A network that adapts
to the available link.

The Reticulum protocol is implemented here by FreeTAKTeam’s Fabric Rust stack. REM embeds it locally; the RCH 3.0 Rust preview uses the daemon and typed SDK; YARA uses the daemon’s HTTP/WebSocket adapter. Applications share the networking foundation while retaining their own workflows.

01FIELD CLIENT
02RUST RNS + LXMF
03RCH 3.0RUST EDITION / PREVIEW
reticulum-rs librariesTyped SDK / ZeroMQreticulumdRNode / TCP interfaces

06 / RCH MANIFESTO

Communication is a commons.
Resilience is a choice.

RCH supports autonomous communities that need to coordinate, preserve knowledge and remain connected when centralized systems become unavailable or hostile.

“RCH begins from a simple refusal: we do not accept that this is inevitable.”

Modern communications have become managed services: centralized, monitored and subject to withdrawal. RCH rejects that dependency and provides infrastructure for civic, humanitarian, mutual-aid, rural and off-grid groups.

The hub is not another social network or a flat swarm of interchangeable devices. It starts with real communities of trust, each able to operate locally, retain its identity and federate selectively with others.

Designed over Reticulum for scarce bandwidth, intermittent power and fragmented links, RCH favors continuity, cryptographic trust and local responsibility. Networks may split and rejoin without forcing a community to surrender control.

Read the full manifesto

07 / MEDIA

See R³AKT in action.

Introductions, demonstrations and field-oriented material from the project.

BUILT IN THE OPEN

Situational awareness
should not be a privilege.

The R³AKT family is developed openly by the FreeTAKTeam community. Study the code, propose an idea or build with us.

Contribute on GitHub