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.
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.
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.
- In the console, open Enroll. Pick the group the device joins and the Wi-Fi network it uses during setup. Generate the QR code.
- On the factory-reset device, tap the welcome screen six times to open the QR scanner. Scan the code.
- The device joins Wi-Fi, downloads the agent from your server and installs it as Device Owner.
- The agent makes a key pair in the device’s secure hardware and gets its own certificate from your server.
- The device shows up in the console within seconds and applies its group’s policies on the first check-in.
04 What it does
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.
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:
| What | Port | Who connects |
|---|---|---|
Admin console at atlas.<your-domain> | 443 | You, in a browser, behind Authentik |
| Device channel (mutual TLS) | 8449 | Enrolled devices |
| Agent download during setup | 80 | A 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.

