The self-managing mesh
for field
TAK operations.

Four things
netTAK does well.

OUTCOME 01

Flash, boot, mesh — a node joins on its own

netTAK knows how to join the cluster without you. Flash the SD card, power on the appliance, watch it converge in under a minute. No central master to configure, no keys to type, no console cable. Add a node mid-operation and it just shows up.

• Self-managing — no central server, no provisioning steps, no admin login required to add a node.
• Self-healing — when a node drops, traffic re-routes within seconds. Operators don't notice the failure.
• Standalone or mesh — run a single node for a remote outpost, or mesh dozens for a multi-site deployment.
• Layer-2 transparent — standard TAK traffic crosses the mesh without translation. Multicast, broadcast, ARP all just work.

OUTCOME 02

Admin from any browser, anywhere on the mesh

Every netTAK node serves a full admin web UI over HTTPS. Open it from any browser on the network — phone, tablet, laptop — and you're in. No SSH, no console cable, no specialized tooling.

• Live dashboard — DHCP leases, connected Wi-Fi clients, mesh neighbors, battery state, GPS — all auto-refreshing in place.
• Per-page admin scope — dashboard, access point, mesh, node, services, logs, and admin pages keep concerns separate.
• Cluster-wide changes from any node — edit DNS records, DHCP reservations, or the upstream resolver list from any node and they propagate to every node.
• Service control in the browser — restart, stop, view logs for any of netTAK's managed services without opening a terminal.
• Reboot, shutdown, halt — system-level actions exposed in the UI with confirmation gates.

OUTCOME 03

Install in the field, no internet required

The whole netTAK install bundle is a single 75 MB tarball with every dependency vendored inside. The install script never touches the network. Drop the bundle on a USB stick, flash a fresh appliance, run the installer — done.

• Offline by default — every apt package, every driver, every config template is included in the bundle.
• Re-install preserves state — admin password, TLS material, cluster state, operator-set DNS records, DHCP reservations, and GPS settings all survive a re-install on top of an existing node.
• Soft and clean uninstall — default uninstall preserves state and credentials so a follow-up re-install picks up where you left off; reset mode wipes for a true clean slate.
• Build your own bundle from the running cluster — the web UI exposes a one-click bundle rebuild for stamping out new nodes from your verified, in-the-field configuration.
• Optional online updates — when you do have WAN reachability, pull security updates with one click and stay on your pinned kernel.

OUTCOME 04

Built for the field, on hardware you can carry

netTAK runs on small Linux appliances you can hold in your hand. Battery-viable, solar-viable, and quiet enough that you can leave one in a Pelican case at a forward site for the duration of an operation.

• Multi-platform support — Linux appliance (palm-sized to mini-server). Pick the hardware that fits the role.
• Wi-Fi HaLow backhaul — sub-1 GHz long-range Wi-Fi gives you miles between sites. Pair with a Yagi or panel antenna for ridge-to-ridge bridges.
• Standard 2.4 GHz Wi-Fi for clients — operators connect with the phones, tablets, and laptops they already have. No special radios required on the client side.
• USB-PD UPS hat UPS integration — live battery state in the dashboard. Plug in a USB-PD UPS hat 2, 3, or 3-Plus and you have a battery-operated node with charge visibility.
• GPS time discipline — clocks stay synchronized across the cluster without internet. Plug in a USB or UART GPS receiver; trust it from the dashboard.

What's in the box.

netTAK is a self-managing wireless mesh for field-deployable TAK operations. The list below is what ships today — every capability is in the current Beta build and used by Early Adopters in active operations.

• Self-managing mesh — drop a node, it joins. No central master, no provisioning.
• Self-healing routing — when a node drops, traffic re-routes within seconds.
• Wi-Fi HaLow backhaul — sub-1 GHz long-range Wi-Fi, miles between sites with directional antennas.
• Standard 2.4 GHz Wi-Fi for clients — operators connect with phones, tablets, and laptops they already have.
• Flat LAN across the cluster — TAK multicast, broadcast, and unknown-unicast cross the mesh transparently.
• Web admin UI on every node — HTTPS, mobile-friendly, no SSH required.
• Live dashboard — DHCP leases, AP clients, mesh neighbors, battery, GPS — all auto-refreshing.
• Cluster-wide DNS records — add an entry on any node, every node serves it.
• Cluster-wide DHCP reservations — pin a MAC to an IP across the cluster.
• Operator-configurable upstream DNS — empty by default (true offline-first); add resolvers when you have WAN.
• Secure cluster sync — encrypted handshake, rotatable cluster-wide pre-shared key.
• Hot-reload TLS — regenerate the certificate without dropping the listener.
• Wildcard certificate — accept once per browser, every current and future node is trusted.
• GPS time discipline — clocks stay in sync across the cluster without internet.
• Manual time setter — when GPS isn't available, set the clock from the web UI.
• RTC sync — manual time survives a reboot on hardware with an RTC.
• Offline install bundle — 75 MB, every dependency vendored, no network required.
• Idempotent re-install — admin password, TLS, cluster state preserved across upgrades.
• Service control in the browser — restart, stop, view logs from the admin UI.
• Reboot, shutdown, halt — system actions in the UI with confirmation gates.
• USB-PD UPS hat UPS integration — live battery state on the dashboard for battery-operated deployments.
• Runs on any small Linux appliance — auto-detected, no per-platform configuration.

What netTAK needs.