GOTAK GATEWAY · DESKTOP BRIDGE
v1.0 · WINDOWS + MACOS

Radio Relay Bridge

BTECH TNC, multicast CoT, and TAK Server TCP paths in one local console — running on the laptop already in your kit. Per-contact routing decides what goes where. Bidirectional out of the box. No phone in the loop.
Buy Radio Relay Bridge → ▶ Talk to Sales
✓ Bidirectional
✓ Per-Contact Routing
✓ Windows + macOS
✓ BTECH UV-Pro · Benshi
RADIO RELAY BRIDGE · v1.0

Radio in.
TAK out.

BTECH TNC, multicast CoT, and TAK Server TCP paths in one local console. Per-contact routing decides what reaches the LAN, the server, and back to the radio. No phone tethered. No plugin per device. One executable.

RADIO RELAY BRIDGE · v1.0 BRIDGE OPERATIONAL

Desktop Radio-to-TAK Gateway

BTECH TNC · multicast CoT · TAK Server TCP · per-contact routing · web console

BIDIRECTIONAL YES RF ↔ TAK · both ways
TAK SERVERS 3 TAK_OS · OpenTAK · GOTS
PHONES NEEDED 0 no Android in the kit
PLATFORMS 2 Windows · macOS
LIVE BRIDGE SESSION LIVE
  • T+0.0s Bridge starts · scanning BLE for BTECH UV-PRO INIT
  • T+1.2s UV-Pro paired · bond persisted to OS keychain · TAKPacket parser ready BLE BONDED
  • T+8.7s Inbound RF · contact IMPAC decoded · TAKPacket → CoT RF → COT
  • T+8.7s Routed: To Multicast + To TAK Server · 10 ATAK contacts updated ROUTED
  • T+8.8s TCP push → eud.gotak.dev:8089 · CoT delivered · cert auth OK TAK SERVER
  • T+12.3s Reverse · ATAK contact CHARLIE · CoT → TAKPacket → BLE write BIDIRECTIONAL
CAPABILITY MANIFEST 06 · INSTALLED · OTA
BTECH TNC winrt_rfcomm

Native BLE TNC for BTECH UV-Pro and Benshi UV-Pro variants. Pairs once with the OS Bluetooth stack — bond persists across reboots.

Multicast CoT 239.2.3.1

Standard TAK multicast on UDP 6969. Every ATAK, WinTAK, and iTAK on the LAN auto-discovers — no per-device config.

TAK Server TCP TLS · 3 SERVERS

TLS + cert auth to TAK_OS, OpenTAK Server, and the official GOTS TAK Server. Switch between them in the web console.

TAK Client Server TCP

Local TAK endpoint for iOS, WinTAK, and desktop ATAK clients that need a direct TCP target instead of multicast.

Contact Routing PER-CONTACT

Decide per contact which paths each message takes — To Radio · To Multicast · To TAK Server. RF-READY or COT-ONLY per ATAK contact.

Web Console localhost:8080

Browser-based dashboard, setup, radio, chat, TAK server, license, and settings — all in one local console.

Buy Radio Relay Bridge Windows + macOS · BTECH UV-Pro · Benshi · Licensed software
01 FORWARD BRIDGE

Radio in.
LAN and TAK Server out.

Every other radio gateway needs a phone tethered to the radio with an Android plugin in the loop. The Bridge runs on the laptop already in your kit, decodes BLE in software, and fans out to multicast and TCP simultaneously.

01 RF in. No glue code, no phone middleman.

The Bridge speaks BTECH/Benshi BLE natively. UV-Pro pairs once with the laptop's OS Bluetooth stack — Windows native, macOS browser-assisted — and the bond persists. Every TAKPacket the radio receives over the air is decoded and fanned out the moment it lands.

02 Multicast for every ATAK in the room.

Standard TAK multicast on 239.2.3.1:6969. ATAK on a teammate's tablet, WinTAK on the TOC laptop, iTAK on the iPad — all auto-discover the Bridge with zero per-device configuration. One radio operator covers the whole LAN.

03 TLS for the server. Whichever server you run.

Push encrypted CoT to TAK_OS, OpenTAK Server, or the official GOTS TAK Server with cert authentication. The same Bridge configuration switches between them. Internet path optional — only required if your server is remote.

Buy Radio Relay Bridge
FORWARD BRIDGE RADIO → MULTICAST + TLS
02 REVERSE BRIDGE

TAK in.
RF out.

Most radio gateways are one-way: RF flows up to TAK and dies there. The Bridge runs the reverse path natively — server-side CoT, chat, and geofences encoded back into TAKPacket and written over BLE to every radio in the net.

01 Server messages back to the net.

Operator types a chat in TAK_OS or drops a marker in WinTAK — the Bridge encodes it as a TAKPacket and writes it to the paired UV-Pro over BLE. Every radio in the net hears it on the next RF cycle. The server-side workflow extends to operators who only carry a radio.

02 Geofences and rules that radios respect.

Server-side rules — geofences, alerts, command directives — are encoded into TAKPacket and pushed back through the Bridge. Radio operators get the same situational awareness as ATAK clients without ever opening an app.

03 One Bridge. One license. Every server you run.

A single Bridge install relays whichever paired UV-Pro is online and pushes to whichever TAK Server is configured. Run it on the TOC laptop. Run it on a hardened mini-PC. Run it as a Windows service for unattended operation.

Buy Radio Relay Bridge
REVERSE BRIDGE TAK → BRIDGE → BLE → RF
WHO IT'S FOR

Any net.
Any TAK Server.

Radio Relay Bridge isn't built for a single mission profile — it's built for any team that runs RF in the field and TAK at the top. From special operations to search and rescue to municipal law enforcement to disaster response, the Bridge connects the two without phones, plugins, or custom integration.

01 · TACTICAL OPERATIONS

BTECH net. Full COP. Zero phones in the kit.

A squad on UV-Pros — no Android phones, no plugins, no per-operator licenses. The TOC laptop runs the Bridge. Every chat, geo-position, and chat reply over RF lands on the COP map at the TOC inside a second. Every server-side directive flows back over the air without anyone touching a phone.

BLE PairTAKPacket DecodeMulticast LANTLS PushReverse Path
MISSION · 01 TACTICAL OPERATIONS

02 · BORDER · SAR

Backcountry net. Bridge at the trailhead.

A SAR team carries UV-Pros into terrain with no cell signal. The team coordinator parks at the trailhead with a laptop, the Bridge, and a Starlink. Every position update from the searchers, every find call, every coordinated turn flows over RF to the Bridge and out to TAK_OS — and command back at the operations center sees the full picture in real time.

BLE PairUDP MulticastTLS PushOpenTAK ServerWeb UI
MISSION · 02 BORDER · SAR

03 · LAW ENFORCEMENT

Patrol radios on the wall map.

Every patrol vehicle carries a UV-Pro. A laptop in dispatch runs the Bridge with a TLS push to the agency's TAK_OS server. Every patrol position, every hot-stop call, every BOLO flows from RF to the wall map without dispatch needing to manually log a thing. Geofences pushed from the server alert deputies on the same radios they already carry.

TCP CoT ServerTAK_OSReverse PathGeofencesWeb UI
MISSION · 03 LAW ENFORCEMENT

04 · DISASTER · EM

Comms-out scenario. Radio + Bridge keeps IC synced.

Cell towers down, public safety net saturated, internet intermittent. Incident command runs the Bridge on a laptop with a local OpenTAK Server — fully self-contained on the LAN. Every responder on a UV-Pro radio appears on the IC map without a single packet needing to leave the staging area.

Multicast LANOpenTAK ServerMeshWeb UIAir-gapped Activation
MISSION · 04 DISASTER · EM
THE DIFFERENCE

Radio gateways before.
Radio gateways now.

The phone-plugin pattern works — but it scales poorly, locks you to Android, and only flows one direction. The Bridge moves the gateway off the phone, onto the laptop, and runs the round trip both ways.

CAPABILITY  
PHONE PLUGIN

Without Radio Relay Bridge

RADIO RELAY BRIDGE

With Radio Relay Bridge

01 Phone in the loop
Without Radio Relay Bridge

One Android per radio. Each operator carries a phone running an ATAK plugin to translate RF to CoT.

With Radio Relay Bridge

None. The Bridge runs on the laptop already in your kit. Operators carry radios. That's it.

02 Reach on the LAN
Without Radio Relay Bridge

RF only. Whoever is on the radio hears the message. ATAK clients on the same LAN are not in the loop.

With Radio Relay Bridge

Multicast on 239.2.3.1:6969. Every ATAK, WinTAK, and iTAK on the LAN auto-discovers and receives the same CoT.

03 TAK Server push
Without Radio Relay Bridge

Custom integration per server vendor. Different config for each TAK_OS, OpenTAK, or GOTS deployment.

With Radio Relay Bridge

TLS to TAK_OS, OpenTAK Server, and the official GOTS TAK Server out of the box. Switch between them in the web UI.

04 Direction of flow
Without Radio Relay Bridge

RF → TAK only. Server-side directives, chats, and geofences never reach the radio operator.

With Radio Relay Bridge

Bidirectional. Server CoT and chat are encoded as TAKPacket and written back to the radio over BLE.

05 OS support
Without Radio Relay Bridge

Android-only. The phone plugin pattern locks the gateway to the Android lifecycle and the per-device install footprint.

With Radio Relay Bridge

Windows 10/11 and macOS 12+. Signed installers. Optional Windows service mode for headless operation.

06 Setup
Without Radio Relay Bridge

Install ATAK on each phone. Install the plugin. Pair the radio. Configure the server. Repeat per device.

With Radio Relay Bridge

Run one executable. Open localhost:8080. Pair the radio. Pick the server. Done.

One executable. Both directions. Every TAK Server you run.

Buy Radio Relay Bridge
FAQ

Six questions
operators ask first.

Full documentation in the GoTAK knowledge base. Community support on Discord. Government and enterprise procurement support direct from sales.

06 · QUESTIONS

BTECH UV-Pro and Benshi UV-Pro variants — the BLE-controlled BTECH and Benshi product line. Pairing uses the OS Bluetooth stack (native on Windows, browser-assisted on macOS). Additional BLE radios are on the roadmap as benlink protocol coverage expands.

No. The Bridge multicasts to every ATAK, WinTAK, and iTAK on the LAN, and pushes TLS to your TAK Server. ATAK does not need to be installed on the laptop running the Bridge — though it works fine if it is.

TAK_OS (GoTAK's managed TAK Server), OpenTAK Server (the open-source option), and the official Government Off-The-Shelf TAK Server distribution. All three over TLS with cert authentication. Switch between them in the web UI without changing the install.

Yes for the LAN side — multicast on 239.2.3.1:6969 doesn't need internet. The TAK Server push only needs whatever path your server requires. For fully air-gapped deployments, run the Bridge alongside an on-LAN OpenTAK Server and the entire system operates without ever leaving the local network.

Windows 10/11 with native BLE bond support, and macOS 12+ with browser-assisted pairing. Both ship as signed single-file executables — no Python install required on the target machine. Linux is on the roadmap. Optional Windows service mode is available for unattended/headless operation.

Each Bridge install is activated against the GoTAK licensing service with a license key purchased at checkout. Offline activation is available for air-gapped deployments — contact sales for the air-gapped activation flow. Licenses are per-install, not per-radio.

More questions? Ask on Discord or email sales@getgotak.com.

GoTAK Discord
RADIO RELAY BRIDGE

Radios that talk to TAK.
Without the phone tax.

One executable on the laptop already in your kit. Multicast for the whole LAN. TLS to TAK_OS, OpenTAK, or GOTS. Bidirectional, both ways, every direction. The phone plugin pattern was a workaround — the Bridge is the answer.

Buy Radio Relay Bridge Talk to Sales
Includes WINDOWS + MACOS · BTECH + BENSHI BLE · TAK_OS · OPENTAK · GOTS-READY · WEB UI
Radio Relay Bridge $200.00
Sold Out