Features/Network Bridge
Network Bridge
BETAPROENT

One picture across every network.

The bridge connects the LoRa mesh to whatever else your operation runs — a TAK Server, a local LAN, a MANET, or another mesh stack — so data flows both ways between off-grid teams and connected infrastructure, without making the field depend on any of it.

Beta — a bridge is a natural choke point, so we're still validating it across large groups, devices and scenarios before calling it final.
MESH ⇄ NETWORK
MESHoff-grid
LANCE
BRIDGEconnected EUD
IP
NETTAK · LAN · MANET
Directiontwo-way
Field dependencynone
ScopePro light · Ent full
01

The mesh stays the source of truth

Bridging is additive, never required. The field side runs fully off-grid on LoRa; the bridge simply lets a connected node carry the picture onward to another network — and bring data back. If the uplink drops, nothing in the field changes.


02

Bridge to whatever you already run

A TAK Server is the most common case — reconstructed positions and events from off-grid teams appear in your existing TAK infrastructure alongside everything else. But the bridge isn't limited to it. Through a connected device it can also exchange data with other networks:

SERVER
TAK Server

Sync the mesh picture into your TAK infrastructure, both ways.

LOCAL
Local LAN

Share with devices joined over a local router or switch.

MANET
MANET / Wi-Fi mesh

Link professional MANET radios with smartphones over Wi-Fi to the LoRa mesh.

RESEARCH
Other mesh stacks

Bridging across MeshCore, Reticulum and Meshtastic is under research.


03

Scope that matches the edition

Pro offers an optional light bridge scope for individuals and small teams. Enterprise extends this to full organizational scope, governed by policy and aligned with fleet deployment — so a whole organization can connect its mesh edge to its networks under control.

EditionNetwork bridging is a Pro and Enterprise capability. Free keeps the focus on the core off-grid mesh.

04

More radios, more bridges — in research

We're researching connecting more than one radio to a single phone over Bluetooth. That opens the door to bridging directly between different mesh networks at the edge — a node sitting on Meshtastic, MeshCore and Reticulum at once, carrying the same Lite-family data across all of them. See the roadmap for where this is heading.

FAQ

Network bridge, answered.

Do I need a server or other network to use LANCE?
No. LANCE is fully usable off-grid on the LoRa mesh alone. The bridge is an optional way to connect that mesh to another network — a TAK Server, a LAN, a MANET — when one is reachable.
Which networks can it bridge to?
A TAK Server is the primary case, but through a connected device the bridge can also exchange data with a local LAN (devices on a router) or a professional MANET where smartphones are linked over Wi-Fi. Bridging across other mesh stacks — MeshCore, Reticulum, Meshtastic — is under research.
Does data flow both ways?
Yes. The bridge carries the mesh picture out to the connected network and brings that network's relevant data back into the mesh — while the mesh stays the authority in the field, so a dropped uplink changes nothing for off-grid teams.
Which editions include bridging?
An optional light scope on Pro, and full organizational scope on Enterprise with policy and fleet alignment. Free focuses on the core mesh.

Connect the mesh edge to every network.