Your Meshtastic mesh,
now a TAK network.

Three things
loraTAK does well.

OUTCOME 01

Make every mesh node a TAK contact

Mesh node positions flow onto ATAK, WinTAK, iTAK, and baseTAK maps in real time as SA markers. The mesh device doesn't need any TAK awareness — it beacons its position normally, and loraTAK translates.

• Operator-chosen icon per node — assign a team color, role, and icon to each Meshtastic user: full MIL-STD-2525C symbology, or any standard ATAK iconset. Icons reflect the role on the team, not the radio model.
• Position liveness — keepalive beacons keep mesh markers visible every 60 seconds even when stationary radios beacon every few hours.
• Synthetic positions — GPS-off mesh devices still appear at the gateway location so they're chat-able.
• Telemetry on the map — battery, voltage, channel utilization, temperature, SNR all visible in TAK position details.

OUTCOME 02

Make mesh chat and TAK chat the same chat

Mesh chat lands in TAK chat. TAK chat lands on mesh devices. DMs work both ways.

• Mesh primary channel → TAK All Chat Rooms — broadcast text from any mesh device reaches every TAK client on the network.
• TAK chat → mesh — broadcast TAK chat relays to the mesh primary channel.
• Addressable DMs — TAK users can DM individual mesh nodes by name; mesh users can DM TAK team names or callsigns.
• Multi-part outbound to LoRa users (in development) — messages longer than the Meshtastic packet limit will split into multiple LoRa sends so the receiving mesh user gets the full message. (Current build truncates with a "…" suffix.)
• Read receipts — TAK clients get acknowledgment checkmarks when mesh nodes confirm delivery over LoRa.

OUTCOME 03

Pair with digiTAK — mesh users and ham operators on the same thread

loraTAK and digiTAK are full mesh partners on the TAK network. A SAR volunteer with a $40 Meshtastic radio can DM a ham operator with an APRS handheld; a weather-station beacon on APRS sits next to a hiker's LoRa node on the same map. Every TAK client (baseTAK, ATAK, WinTAK, iTAK) sees both feeds as native contacts.

• LoRa users chat with APRS users (and every TAK client) — a Meshtastic message routes from LoRa → TAK GeoChat on the LAN → digiTAK → APRS-IS or RF, end to end. Both products speak the standard TAK protocol, so the same chat thread carries Meshtastic users, APRS users, and TAK-client users together.
• Run a Meshtastic gateway and an APRS gateway side-by-side with no port collisions or echo loops.
• Multi-NIC appliance-as-AP setups handled correctly — works when the gateway has a wired LAN and a Wi-Fi AP on the same appliance.
• Drop loraTAK onto a netTAK field mesh and every appliance-node becomes a Meshtastic gateway — no LAN required.

What's in the box.

loraTAK is a bidirectional Meshtastic-to-TAK gateway. Field teams running stock Heltec, T-Beam, RAK, or Station-G2 hardware appear as first-class TAK contacts with positions, chat, and telemetry.

• Meshtastic SDK integration — works with stock firmware. No custom radio build required.
• Operator-chosen icons — assign any team color, role, and icon to each Meshtastic user. Use the full MIL-STD-2525C symbol set, or load any standard ATAK iconset (firefighter, SAR, medic, etc.) and assign it. Icons reflect the role on the team, not the radio model.
• Bidirectional position + chat — full round-trip between TAK clients and the mesh.
• 60-second keepalive beacons anchor mesh-node presence in TAK even when nodes go quiet.
• Multi-part outbound to LoRa (in development) — outgoing messages longer than the Meshtastic packet limit will split across multiple LoRa sends. Current build truncates long messages with a "…" suffix.
• Multi-part inbound reassembly — long mesh-origin messages that arrive as multiple LoRa packets reassemble cleanly on the TAK side.
• Read receipts and addressable DMs across the LoRa link.
• Synthetic positions for GPS-off mesh nodes — anchored from gateway location so they stay chat-able.
• Mesh telemetry on the map — battery %, voltage, channel utilization, SNR — emitted as <__mesh_telem> JSON in every beacon.
• Multi-NIC appliance-as-AP mode — eth0 for upstream, wlan0 as a soft AP for the mesh team to associate with.
• Bidirectional TAK protobuf RX from radios that speak it — no XML round-trip.

What loraTAK needs.