microTAK

Alpha · free & open source · AGPL-3.0

Built for wherever
the mission takes you

MicroTAK aims to be a lightweight yet fully functional TAK server, written in Rust. It is designed to run off grid on a single-board computer or an old laptop, serve the team around it, and keep that team in sync with headquarters over whatever link is left.

Alpha software. MicroTAK is under active development and has not been used in a real operation yet. Try it, test it, report what breaks; don't depend on it where lives or livelihoods are at stake.

Get started View the code
Phones connect to a MicroTAK server carried in the field; the server links to headquarters over RF or IP. RF · IP · USB HQ MicroTAK WiFi LoRa Radio

Why MicroTAK

In remote wilderness, when the grid is down, or in an area where the spectrum is contested, there is no data centre and every watt counts. A team still needs a shared picture: positions, chat, markers, missions and files.

Lightweight

Only the essentials of a TAK server, in one small binary. No bundled web interface or database server. Designed to run on single-board computers and old laptops or NUCs, on x86_64 and ARM64.

Built for stability

Written in Rust for memory safety and predictable behaviour. The goal: a server that keeps running unattended, far from anyone who could restart it.

Compatible

Speaks the official TAK Server's protocols and APIs, so the TAK clients your team already uses connect as they would to any TAK server.

Modular

Extra capabilities, such as an admin web interface or, later, RF bridges, are separate modules. Run only what you need and keep power use as low as the mission requires.

Where MicroTAK fits

Scenarios MicroTAK is designed for. They describe what we are building towards, not deployments that have happened: MicroTAK hasn't been used in a real operation yet. "Works today" means the features the story needs exist in the current alpha.

Disaster relief

The flood took out the cell towers. At each staging area a volunteer sets up a laptop running MicroTAK on a generator; rescue boats and supply teams show up on every tablet in the area. When the satellite link comes up for a few minutes an hour, each staging area syncs with the coordination centre: positions, new hazard markers, updated maps.

Needs the roadmap federation and sync between servers

Forestry and logging

The cutting block is two valleys away from the last bar of signal. A small server in the crew truck covers the landing; fellers, the skidder and the forwarder share their positions, mark hazard trees and danger zones on the map, and chat without a phone network.

Works today

Hunting

A driven hunt with twenty hunters spread along a ridge. Everyone sees where the others stand before taking a shot, the drive leader moves the line from a phone, and the recovery team gets the exact spot where game went down. The server rides along in a backpack.

Works today

EMS at large incidents

A bus crash on a rural road. The first ambulance brings a small server; arriving units see the incident layout, staging area and helicopter landing zone, and the incident commander tracks which crews are where. No patient data, just the shared picture.

Works today

Search and rescue

A hiker is overdue in the mountains. The command post assigns search sectors as a mission; each team sees its sector, its own track and where the others have already looked. Teams out of range keep working locally and their tracks merge when they reach a relay or return to base.

Needs the roadmap federation and sync between servers

Fleet management

A rural water utility's service vans and a few contractor trucks, all with phones running a TAK client. The depot runs MicroTAK on a mini PC: dispatch sees every vehicle, sends jobs as markers with notes and photos, and nothing depends on a cloud subscription.

Works today

Large outdoor events

A three-day trail race through the forest. Marshals, first aiders and supply volunteers carry phones; organisers see who is where, send everyone an update when a section gets rerouted, and the medical team knows the closest helper to every incident.

Works today

Milsim

A weekend airsoft operation on a disused training ground. Each faction runs its own MicroTAK server on a laptop, with its own channels for teams and command; game control sees everything. Maps, objectives and mission packages are set up before the game starts.

Works today

Scouting

A patrol hike with five groups on different routes. Leaders see where each group is, groups report checkpoints with a marker, and anyone can send a message to all. It's a good way to learn navigation, radio discipline and teamwork with real tools.

Works today

Surveying and field work

A survey crew in a remote area marks points, photographs features and shares data packages with each other through a server in the field vehicle. Back in range, or with a USB stick at the office, the day's work syncs to headquarters.

Needs the roadmap federation and sync between servers

One server in a backpack

One operator carries the MicroTAK server and bridges it to a data network over RF. The rest of the team reaches it over WiFi, radio or LoRa. The server keeps in sync with headquarters or a mobile HQ and distributes data, CoT and map layers in both directions.

Several small servers, each serving its own area, sync with each other whenever a link exists. Clients roam between them. When nothing else gets through, data travels on a USB stick.

Roadmap Federation, roaming, USB transfer and RF bridges are being designed now. The server itself is available today; see what works below.

  • IPLAN, mesh WiFi, cellular, satellite
  • AX.25Packet radio
  • ReticulumResilient mesh networking
  • LoRaLong range, low power
  • Ham radioHF/VHF/UHF links
  • USB stickWhen nothing else gets through

What works today

These parts are implemented and tested against ATAK-CIV, OmniTAK and CloudTAK during development. It is alpha software: expect rough edges and breaking changes between versions.

Enrollment

Its own certificate authority, QR-code invites, password accounts and certificate enrollment as TAK clients expect it. Revoke a lost device or block an identity at any time.

Streaming

Positions, chat and markers over mutually authenticated TLS, including the TAK Protocol (protobuf). New clients get the latest positions immediately.

Missions

The official Mission API: missions, subscriptions, roles, change logs, map layers, mission packages and live updates.

Files

Data packages, photos and other files with DataSync and the file manager API.

Groups

Channels with send and receive directions, as on the official server, switchable from the device.

Device profiles

Push settings and files to devices when they enroll, when they connect, or on demand.

Operations

Backups, Prometheus metrics, connection limits and rate limiting. An admin CLI and an optional admin web interface.

Packaging

Docker images and release binaries for x86_64 and ARM64, plus a Helm chart for Kubernetes.

Roadmap

  1. Next

    Federation

    Small servers that sync with each other and with headquarters in both directions, over IP, AX.25, Reticulum, LoRa and ham radio, built for low bandwidth and intermittent links.

  2. Planned

    Roaming

    Clients move from one server to another and keep their picture.

  3. Planned

    Sneakernet

    Carry the data on a USB stick when no link exists.

  4. Planned

    RF bridges

    Optional modules that bring radios and mesh devices onto the server.

Get started

Run the server with Docker. It creates its own certificate authority on first start and needs no internet connection.

docker run -d --name microtak \
  -p 8446:8446 -p 8443:8443 -p 8089:8089 \
  -v microtak-data:/var/lib/microtak-server/data \
  ghcr.io/microtak/microtak-server:latest

Then enroll the admin with the one-time bootstrap token from the data directory, invite devices with QR codes, and connect ATAK. The README walks through every step, the configuration and running behind a reverse proxy.

Prefer a binary? Download microtakd for x86_64 or ARM64 from the releases, or deploy with the Helm chart.

The MicroTAK family