Every device on the map
OpenTAK Tracker turns an Android phone into a dedicated TAK-compatible position beacon. It sends location as PLI over CoT to your TAK Server without requiring every user, vehicle, or asset to run a full ATAK client. Simple setup. Reliable reporting. Less noise on the network.
Any Android becomes a TAK contact — no ATAK required
Scan one QR. The device configures itself.
Administrators encode server host, ports, credentials, callsign, team colour, role, and the certificate workflow into a single QR. The operator scans once — the app prefills every field and enrolls its TLS certificate automatically. Under two minutes from box to reporting.
PLI over CoT, straight to your TAK Server.
CoT XML over TCP/TLS with client-certificate auth — the same security model ATAK uses. Lightweight position only: no map tiles, no chat, no mission packages. A persistent foreground service keeps reporting through reboots and reconnects.
Every person, vehicle, and asset on one map.
Each device shows up as its own TAK contact with its own callsign, team, and role. When ATAK opens on the same handset the companion plugin pauses the tracker, so command sees one clean position report per device — never two.
Enroll. Report. Appear.
01 ENROLL QR enrollment — scan once, done
Administrators encode server host, ports, credentials, callsign, team colour, role, and the certificate workflow into a single QR. Operators scan once — the app prefills every field and initiates TLS certificate enrollment automatically. Under 2 minutes from box to reporting.
02 ENROLL Every TAK enrollment format
opentaktracker:// URI, ATAK tak:// links, iTAK-style CSV payloads, and ATAK JSON server payloads. Whatever enrollment infrastructure your team already uses, OpenTAK Tracker understands it.
03 FLEET Identity updates without touching the device
Configure-only deep links push callsign, team colour, and role to any enrolled device. Reconfigure 50 devices for a new exercise without walking each one through manual settings.
04 SECURE TLS with client certificates
CoT XML over TCP/TLS with client-certificate authentication — the same security model ATAK uses. Certificates are enrolled via CSR workflow and stored on device. UDP multicast is available for local-network deployments where TLS is not required.
05 MULTI Multiple servers, independent control
Store multiple server configurations, each with its own connection state, credentials, and certificate enrollment. Enable or disable servers individually — useful for teams operating across training networks, live ops, and mutual aid without rebuilding the device setup each time.
06 COMPANION ATAK-aware — pauses when ATAK opens
When ATAK is active on the same device, the companion plugin signals OpenTAK Tracker to pause PLI transmission, then resumes when ATAK closes. No duplicate position reports, no competing contacts on the server. The plugin can also sync callsign and server profile from ATAK.
07 EMERGENCY Emergency alerts and hardware SOS
TAK-compatible emergency events: 911 Alert, Ring the Bell, and In Contact. Emergency CoT transmits to every configured server immediately. Hardware SOS fires from rapid volume-key presses without opening the app — which matters for lone workers and operators who can't look at the screen.
08 DEVICE Dedicated device mode
Persistent foreground service, boot startup, kiosk lock, auto-reconnect, and on-device diagnostics. Built for vehicle-mounted handsets, issued trackers, and kiosk-locked devices that should simply keep reporting.
09 BANDWIDTH Lightweight by design
One CoT XML packet per reporting interval — no map tiles, no chat, no mission packages. On large teams with many trackers the bandwidth savings are significant and the TAK Server gets clean, focused position data.
Not every device needs
all of ATAK.
ATAK is the full situational awareness client. OpenTAK Tracker is for devices that need to be seen — personnel, vehicles, equipment, and dedicated trackers that should report position without the overhead of a full TAK deployment on every handset.
Full ATAK on every device
OpenTAK Tracker
Full ATAK-capable EUD — $300–$1,000+ per device, configured for the mission.
Any Android 8+ device. A spare phone, a vehicle handset, a dedicated tracker — any Android works.
Manual ATAK install, server import, certificate enrollment, plugin setup — 15–30 min per device.
Scan a QR or tap a deep link. App configures itself and enrolls certificates automatically. Under 2 minutes.
Full ATAK data sync — map tiles, chat, markers, mission packages, plus PLI. Heavy on large teams.
Lightweight PLI only — one CoT XML packet per reporting interval. Minimal bandwidth, minimal server load.
Risk of duplicate PLI if ATAK and a tracker app run on the same device simultaneously.
ATAK-aware companion mode pauses OpenTAK Tracker when ATAK is active. No duplicates. Clean handoff.
ATAK is not practical for vehicle-mounted handsets, issued trackers, or kiosk-locked devices.
Built for it. Foreground service, boot startup, and kiosk compatibility for devices that just keep reporting.
Changing callsign, team color, or role on 50 devices requires touching each one manually.
Configure-only deep links push identity updates to any enrolled device. No physical access required.
Use both. OpenTAK Tracker handles the trackers. ATAK handles the operators. One map. No duplicates.
Download OpenTAK TrackerSix questions
admins ask first.
Full documentation in the GoTAK knowledge base. Community support on Discord.
No. OpenTAK Tracker is a dedicated tracker. It is built for devices and users that need to report location into TAK without the full ATAK interface — map tools, chat, drawing, mission packages. ATAK remains the full situational awareness client. Use them together: OpenTAK Tracker for the trackers, ATAK for the operators.
Yes — with the companion ATAK plugin. When ATAK is open and transmitting PLI, the plugin signals OpenTAK Tracker to pause. When ATAK closes, OpenTAK Tracker resumes normal tracker behavior. No duplicate position reports on the TAK Server. The plugin also supports syncing callsign and server profile details from ATAK to OpenTAK Tracker.
Three paths: QR code — administrator generates a TAK enrollment QR carrying server address, port, credentials, callsign, team, role, and certificate workflow. User scans once, app prefills and enrolls automatically. Deep link — opentaktracker:// URI or compatible ATAK/iTAK enrollment links. Manual — enter server details directly in app settings.
Yes. OpenTAK Tracker supports TLS connections with client certificate authentication — the same security model ATAK uses. Certificates are enrolled via CSR workflow and stored on device. UDP multicast is also available for local network deployments where TLS is not required.
Yes. OpenTAK Tracker supports TAK-compatible emergency alert events: 911 Alert, Ring the Bell, and In Contact modes. Emergency CoT events transmit to all configured servers immediately. Hardware SOS is available via rapid volume-key presses — activates without opening the app, which matters for lone workers and operators who can't look at the screen.
Yes. OpenTAK Tracker supports multiple server configurations, each with independent connection state, credentials, and certificate enrollment. Enable or disable servers individually — useful for teams operating across training networks, live ops, and mutual aid environments without rebuilding the device setup each time.
Put it
on the map.
Any Android device. Scan a QR. Reporting PLI to your TAK Server in under two minutes. Free download. No subscription. Works standalone or alongside ATAK. Every person, vehicle, and asset that needs to be seen — seen.