SpectreDynamics
ENTH
Products / Operational Interoperability Platform

Citadel

Different gear. Same team. Try to keep up.

View products

01 / Operational Interoperability Platform

Updated 13 October 2026

Citadel

Different gear. Same team. Try to keep up.

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.

  • ATAK / WinTAK / XTAK
  • OverWatch
  • Reticulum / LXMF
  • MeshCore
  • Meshtastic
  • Self-hosted / VPS
  • Raspberry Pi 4 / 5
Request a Citadel demonstrationFind your connection path
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.
See what the device actually reports. Citadel console, private values redacted.
See what the device actually reports.Connection health, retained battery readings and server traffic. Device identity, IP and username are redacted; unavailable readings remain clearly labelled.
The mesh, with its pulse showing. Citadel console, private values redacted.
The mesh, with its pulse showing.Live RNS status, resource use and interface counters from the running deployment. This is a captured state, not a claim of field radio throughput.
Connect the team. Keep the keys private. Citadel console, private values redacted.
Connect the team. Keep the keys private.Client onboarding controls with LXMF addresses and the IFAC network key redacted. Private configuration packages are never published.
An update should come with a way home. Citadel console, private values redacted.
An update should come with a way home.RNS release selection and update/restore controls. No software update was triggered while capturing this view.
Channels under control. Citadel console, private values redacted.
Channels under control.The Meshtastic channel management interface. Account names and sensitive channel values are redacted; the empty table reflects this deployment.
The server stays here. The radio goes with you. Citadel console, private values redacted.
The server stays here. The radio goes with you.MeshCore VPS mode and field gateway controls. Usernames, network addresses and credential fields are hidden; no gateway token was issued.
Know what is running before you call it ready. Citadel console, private values redacted.
Know what is running before you call it ready.Citadel server resource and runtime overview, captured from the maintained deployment. The signed-in username is redacted.

A shared operational picture

Connect compatible position reports and markers to the shared map. Manage missions and data packages through supported field clients. Purge hides disconnected or expired devices from your browser map while retaining their records.

Keep the clients your team uses

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.

Built to work with OverWatch

Exchange operational data through compatible interfaces and configured integrations. Coordinate across the applications your team already carries.

Three mesh ecosystems

Connect Reticulum/LXMF, MeshCore and Meshtastic through their configured paths. Enrolled active accounts share All Chat Rooms; position permissions use separate group IN/OUT controls.

Field radios stay in the field

Run the central server on your infrastructure or a VPS. MeshCore radios connect through field gateways with scoped, expiring credentials. The central VPS needs no attached radio.

Device health with context

Inspect connection history, battery readings, data age and server-side traffic. Native diagnostics appear when the client reports them. Missing telemetry stays unavailable, rather than becoming a made-up zero.

Live Reticulum status and managed updates

Inspect versions, uptime, interface counters, resource use and pending deliveries. Administrators can stage supported RNS releases and restore the previous runtime; failed health checks trigger rollback.

Readable text, even over small links

Long UTF-8 messages use numbered parts within Meshtastic and MeshCore payload budgets. Small mesh images need compatible receivers; ordinary phone apps do not reconstruct Citadel image fragments.

Your deployment, your infrastructure

The installer detects supported Ubuntu 24.04/26.04, Debian 13.7 and Raspberry Pi OS Trixie 64-bit hosts and selects the matching Python runtime and dependency constraints.

Old servers still get clearance for takeoff

An x86-64/SSE2 baseline supports older 64-bit CPUs and virtual machines. Optional SSE4, AVX2/FMA3 and AVX-512 NumPy paths depend on the complete feature groups exposed inside the guest. Acceleration applies where compatible kernels exist.

Small board. Full platform.

Raspberry Pi 4 and 5 use an ARMv8-A/NEON baseline on 64-bit Trixie. Pi 5 can use optional FP16 and dot-product paths where the runtime implements them. No Pi 5-only instructions are forced into the shared baseline.

Voice and video alongside

Add separately configured Mumble voice and MediaMTX video streams and recordings over IP. Manage console access, certificates and optional authenticator MFA in the web interface.

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.

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.

Real Citadel console captures, 13 October 2026. Usernames, LXMF addresses, keys, tokens, IP addresses and device identifiers are redacted before capture. Operational map overlays are hidden; map attribution is retained.

Build your evaluation around your existing setup.

Tell us your clients, radios, cameras and deployment environment. Start with a product demonstration or a discussion of integration requirements.

Contact us
Citadel | Spectre Dynamics