SpectreDynamics
CITADEL · FIELD + MESH

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.

Field clientsCoT / GeoChat over TLS
MeshtasticMQTT gateway
MeshCoreCompanion TCP / HTTPS gateway
Reticulum / LXMFReticulum links / LXMF
OverWatchConfigured compatible interfaces
CitadelYour server · Your infrastructure
  • 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.
Different clients. One operational picture. Citadel console, private values redacted.
Different clients. One operational picture.Citadel map with the Purge control. Operational overlays and account names are hidden.

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.

TAK & Mesh Communications | Spectre Dynamics