TAK & Mesh Communications
Keep the clients your team uses. Citadel connects TAK and three mesh ecosystems through defined paths. The web console manages maps, gateways and system status; messaging uses supported clients.
CITADEL · FIELD + MESH
Different networks. One place to coordinate.
Citadel connects compatible field applications, mesh networks and OverWatch so teams can exchange positions, messages and mission data across the tools they already carry. One console for the connections, identities and gateways that keep the operation moving.
- Shared map + Purge
- Device health
- Live RNS status
- Client messaging
Client messaging uses the shared room for enrolled active accounts. The web chat page is removed. Location permissions remain separate; group/team-color chat separation is planned.
Find your connection path
Choose a network to see how it connects and what the current integration carries.
ATAK · WinTAK · XTAK
Field clients
ATAK, WinTAK and XTAK can connect through the documented CoT and GeoChat interface over TLS, with private certificate enrollment. Client-specific extensions and plugins need separate compatibility checks.
- Connection
- CoT / GeoChat over TLS
- Position
- Team positions and shared map markers
- Text
- Native GeoChat through supported TAK clients
- Images
- Use media APIs and compatible clients; image display in unmodified ATAK 5.8 is not verified.

Compatible LoRa nodes
Meshtastic
Bridge a configured Meshtastic network to TAK through MQTT. Manage channel settings, uplink/downlink and PSKs, then share a channel using a QR code or URL.
- Connection
- MQTT gateway
- Position
- Supported position reports through the configured gateway
- Text
- Native channel text; long Thai and UTF-8 messages use numbered parts
- Images
- Small image files require the Citadel image receiver; standard phone apps show ordinary text.

VPS + field radio gateways
MeshCore
Run the central server without an attached radio. TCP-capable clients connect through SSH or VPN; a field computer connects its radio to the server over HTTPS.
- Connection
- Companion TCP / HTTPS gateway
- Position
- The virtual Companion endpoint is for chat and does not advertise radio positions.
- Text
- Shared channel text; long messages use numbered parts
- Images
- Compatible receivers reconstruct small image files. RF acknowledgements and automatic retransmission are not implemented.

MeshChatX · Reticulum MeshChat
Reticulum / LXMF
Bind Reticulum identities and LXMF addresses to active accounts. Download a client profile and bring readable identity names, text and compatible location telemetry into the team workflow. Monitor live RNS/LXMF status and let administrators select software updates or restore the previous runtime from the console.
- Connection
- Reticulum links / LXMF
- Position
- Compatible signed location telemetry, with existing IN/OUT group permissions
- Text
- Signed LXMF text with account and identity display names
- Images
- Native LXMF image attachments on compatible clients; radio interfaces require configured RF hardware.

Operational coordination
OverWatch
Exchange operational data through compatible interfaces and configured integrations. Coordinate across the applications your team already carries.
- Connection
- Configured compatible interfaces
- Position
- Operational data through configured integrations
- Text
- Depends on the configured interface and client
- Images
- Client and integration support must be validated

Discuss your deployment
Messaging uses supported clients; the web console has no chat page. Mesh radio delivery needs configured field hardware. Compatible mesh images are limited to 8 KiB and may take minutes to transfer. RF acknowledgements, automatic radio retransmission and group/team-color chat separation are not implemented in the current release. Client-specific behavior and field radio performance require deployment validation. AVX-512 code generation has passed; execution on AVX-512 hardware and full service startup on physical Raspberry Pi boards remain unverified.