ATLAS: device management for ATAK

ATLAS (ATAK Tactical Lifecycle & Administration System) is a self-hosted mobile device manager (MDM) for Android phones and tablets that run ATAK. You run it on your own server, next to your TAK Server. Scan a QR code on a factory-reset device, and from then on it installs the apps, plugins, maps, certificates and settings you assign to it. No cloud subscription, no Google account on the device, no per-device license, and no data leaving your network. Free and open source (Apache 2.0).

01 Why an MDM for TAK devices

Setting up one ATAK device by hand means sideloading the APK, installing plugins, copying map packs and DTED into the right folders, importing the server certificate and preferences, and locking the device down so nobody breaks it. Do that for fifty devices and it is a week of work. A month later, no two devices are the same.

Commercial MDMs solve the fleet problem, but they expect a cloud tenant, managed Google Play and a per-seat subscription. ATLAS starts from what TAK teams actually have:

  • No Google account on the device. Apps come from your own server.
  • Connectivity that comes and goes. A device that was out of coverage for weeks catches up in one check-in.
  • Small policies that stack. A password rule, an app catalog and a Wi-Fi network are separate policies, not one big profile you copy and edit.
  • Your own hardware. Any Android 11 or later device that supports Device Owner mode, from Samsung’s rugged and enterprise lines to rugged tablets such as Tripltek’s.

ATLAS is a general-purpose Android MDM at its core, so it manages the other apps on the device too. ATAK support is built in on top.

ATLAS overviewBy the ATLAS developer

02 How it works

  • The server runs in Docker on the same box as your TAK Server, as an infra-TAK module. It holds your policies, your app library and your content files, and decides what each device should have.
  • The agent is a small app that becomes the device’s owner during setup. Device Owner is the strongest management mode Android has: it can install and update apps silently, set passwords, lock the device to one app, set up Wi-Fi, place files and restrict features, all without a Google account. It uses only standard Android management APIs, so it behaves the same on every maker’s hardware.
  • The console is a plain web app in your browser, behind infra-TAK’s Authentik login. It loads fast even on a laptop tethered to a phone.
  • Two optional apps install only when a policy asks for them: the ATLAS launcher (a kiosk home screen) and the ATLAS filter (web filtering).

Devices talk to the server only over mutual TLS, each with its own certificate. There is no login token to expire while a device is in the field.

Desired stateNot a command streamOn each check-in, the device reports the version it holds. If the server has a newer one, it sends one signed document that describes everything the device should have: apps with their file hashes, files and where they go, settings and restrictions. The agent compares that with what is on the device and fixes the difference. There is no backlog of old commands to replay.
PoliciesMerged field by fieldEach policy fills in only the categories it needs: password, restrictions, apps, networks, files, kiosk, ATAK config, tracking, compliance, web filtering and more. The stricter rule wins for restrictions and password length, lists add up, and where two policies disagree the higher rank wins and the console shows the conflict.

03 Enroll a device

Enrollment takes about two minutes per device and needs nothing on the device first. The device must start from a factory reset, because Android lets an app become Device Owner only during the setup wizard.

  1. In the console, open Enroll. Pick the group the device joins and the Wi-Fi network it uses during setup. Generate the QR code.
  2. On the factory-reset device, tap the welcome screen six times to open the QR scanner. Scan the code.
  3. The device joins Wi-Fi, downloads the agent from your server and installs it as Device Owner.
  4. The agent makes a key pair in the device’s secure hardware and gets its own certificate from your server.
  5. The device shows up in the console within seconds and applies its group’s policies on the first check-in.
QR codesShort-lived or permanentA QR code expires in 15 minutes by default, so a photo of it stops working quickly. You can also limit it to a number of uses. For bulk onboarding, print a permanent QR for the provisioning bench and retire it later with one click.
Re-enrollA wiped device keeps its recordEnroll a wiped device again and its name, group and history come back. It must first prove it is the same device, with its secure hardware or a security code from the console, so a leaked QR code cannot take over a managed device’s identity.

04 What it does

PoliciesStacking you can explainSmall policies (a password rule, an app catalog, a Wi-Fi network) stack on a device or a group. Every setting on a device names the policy that set it and what it overrode, and the console shows a conflict instead of quietly picking a winner.
ATAKATAK, plugins, maps and certificatesInstall ATAK and its plugins, set up TAK Server connections with certificate enrollment, and place map packs, DTED, data packages and preference files in ATAK’s own folders.
ATAKOne policy, a value per deviceWrite ${device.name} or a custom attribute such as ${attribute.Unit} into an app or ATAK setting, and each device gets its own value. A fleet of callsigns needs one policy. Fill names and attributes from a CSV.
AppsYour own app libraryUpload APK and XAPK files, or import ATAK plugins from the TPC and TAKwerx catalogs and apps from F-Droid, IzzyOnDroid, APKPure and Google Play. ATLAS refuses an upload that could not install in the field, and flags apps with a newer build waiting.
FieldBuilt for devices that go darkEach check-in gets one signed document with everything the device should have. A tablet that was offline for three weeks catches up in one check-in. Online devices pick up a policy change within a second.
LocationLocation and geofencesDevices report position on a schedule you set. Draw a fence and get an alert when a device leaves it.
LockdownKioskLock a device to ATAK, or to a home screen you lay out with the ATLAS launcher. Release it by editing the policy, with no hands on the device.
LockdownWeb filtering, radios and volumeAllow and block sites across the whole device, with safe search. Hold Wi-Fi or Bluetooth on or off, block NFC on Android 15 and later, and hold volume levels.
SecurityComplianceMinimum Android version, security-patch age, encryption, passcode, USB debugging off, minimum ATAK version, hardware integrity, and distrusted certificate authorities. After a grace period, a failing device can have apps suspended, be locked, or be wiped.
SecurityBreach modeOne button for a device in the wrong hands: it removes your apps, empties the folders you named, locks the device with your passcode and reports its position every minute. It is not a factory reset on purpose, because a wiped device stops telling you where it is.
AdminAlerts, reports and audit logEmail alerts for enrollment, policy failures, compliance failures, quiet devices and app updates. Fleet reports as CSV. Every console change is logged with who made it and from where.
ATAKThe ATLAS ATAK pluginSigned by the TAK Product Center for ATAK 5.6, 5.7 and 5.8. It reports from inside ATAK what is running, and lets updated plugins load without ATAK’s “Load plugin” prompt.

05 Coming next: Samsung Knox

Knox support is in progress. Everything above works without Knox, and it will stay that way: Knox adds to ATLAS, it is never required, and non-Samsung devices keep working as they do today.

Samsung’s Knox Platform for Enterprise Premium is now free. You make your own license key in the Knox Admin Portal and paste it into the ATLAS console, and the agent activates it on each Samsung device. No Samsung partnership, no reseller, no Google.

ATLAS takes only the Knox features that standard Android has no answer for.

KnoxPer-app firewallAllow, deny or redirect traffic by app, so a device talks only to your TAK Server.
KnoxPer-app VPNSend ATAK through the tunnel and leave everything else off it.
KnoxFiner restrictionsUSB by device class, Settings lockdown, microphone, camera and home key.
KnoxEnterprise Wi-FiEAP networks with certificates.
KnoxCertificate enrollmentSCEP-style issuance on the device, which maps onto TAK client certificates.
KnoxKnox Mobile EnrollmentEnrollment that survives a factory reset.

06 Get it

ATLAS installs from the infra-TAK console. Pick the ATLAS module, and infra-TAK gets the current signed release, builds the container on your server, sets up the database, and loads the agent and launcher into the app library. Updates work the same way. Do not clone the repository and run it by hand: that skips the steps that make it work.

You need one DNS name and one more open port:

WhatPortWho connects
Admin console at atlas.<your-domain>443You, in a browser, behind Authentik
Device channel (mutual TLS)8449Enrolled devices
Agent download during setup80A factory-reset device

Make an A record for atlas.<your-domain> that points to the server. The installer opens 8449 in the firewall, and Caddy gets the certificate. Devices in the field must reach port 80 during enrollment and 8449 after that, over the internet, a VPN or a private LTE network. Multi-agency setups get one hostname and one Authentik admin group per agency.

RequirementsWhat you needA server running infra-TAK. Android 11 or later devices that support Device Owner mode. ATAK 5.6 or later.
Who builds itTAK-Solutions LLCATLAS is built by Michael Leckliter (cfd2474) of TAK-Solutions LLC and released under Apache 2.0. Bug reports, feature requests and field experience are welcome as GitHub issues. Name the device model, the Android or One UI version, and what the device page showed.