Skip to content

TAK Service

URL: tak.irregulars.io | Source: selfhost/tak-service/

The TAK Service is the web side of IrregularChat’s TAK setup. It connects the community’s team tools (Signal, TeamCO) with the TAK server that phones running ATAK and iTAK talk to, so positions, markers and check-ins flow between them without anyone copying things by hand.

To connect a phone, follow the step-by-step guide on the TAK Server page. This page explains what the service does and how the pieces fit together.

Many members use ATAK or iTAK for training, exercises and field work. Without the service, positions and team status would have to be repeated between Signal chats, TeamCO workspaces and TAK maps. With it, a !teamco checkin from Signal shows up on the map and on subscribed phones, a marker dropped on the web map reaches every connected phone, and severe weather alerts appear as markers automatically.

PieceAddressWhat it does
Web app (this service)tak.irregulars.ioSSO login, enrollment page with QR codes, web maps per workspace, TeamCO bridge
TAK servertak-direct.irregulars.ioWhat ATAK / iTAK connect to (port 8089); certificate enrollment (8446)
TeamCOteam.irregulars.ioTeam coordination; each TAK workspace is linked to one TeamCO workspace
Signal botSignal groups!teamco commands that create workspaces and record check-ins

The web app runs as a Cloudflare Worker and reaches the TAK server over a private VPC binding to a bridge. Phones talk to the server directly; they never go through the web app.

A workspace is a team’s map. Web maps are at tak.irregulars.io/map; the list of all workspaces is at /map?manage=1, and opening a /map/<slug> link joins you to that workspace. !teamco create <name> in a Signal group creates a TeamCO workspace with a linked TAK map and replies with the link.

A workspace holds:

  • Saved markers placed on the web map
  • TeamCO check-in locations from !teamco checkin and !teamco setloc
  • Announcements from the linked TeamCO workspace

Chat on the web map is disabled. Members use Signal for messaging.

Workspaces on the phone: Data Sync missions

Section titled “Workspaces on the phone: Data Sync missions”

Every workspace is also published as a Data Sync mission on the TAK server, named after the workspace.

  1. ATAK: open the Data Sync tool → select the server → choose the workspace → Subscribe.
  2. iTAK: Data Sync / Missions → select the server → choose the workspace.

Subscribers receive the workspace’s saved markers, its check-in locations as waypoints, and its announcements as the mission log, refreshed every 15 minutes. The web map at https://tak.irregulars.io/map/<slug> also works in the phone’s browser.

A phone is enrolled once and is not tied to a single workspace:

  • Markers dropped on any workspace web map are sent to every connected phone.
  • A phone’s position appears on the web maps of the workspaces its owner belongs to. The phone is linked to its owner the next time that person logs in at tak.irregulars.io; until then it appears on every map.
  • Web maps load positions when opened and update them every minute.
  • A phone that reconnects after being offline first drains up to 24 hours of missed messages from its server-side queue. That burst is expected.

The service works with the Signal bot through TeamCO:

CommandWhat happens
!teamco create <name>Creates a TeamCO workspace with a linked TAK map and replies with the map link
!teamco checkin / !teamco checkoutRecords your check-in; the location appears on the workspace map and, via Data Sync, on subscribed phones
!teamco setlocSets a location for the workspace; shown on the map the same way
!location <coords or map link>Converts coordinates between MGRS, decimal degrees and DMS; handy for reading positions off a TAK map

Location data flows: Signal bot → TeamCO → TAK Service → web map and subscribed phones.

  • Geofences. Polygons on the map, up to 50 per workspace. When a tracked device enters or leaves one, the map gets a live alert and the linked TeamCO workspace gets an announcement.
  • Weather alerts. National Weather Service alerts are ingested every 15 minutes and shown as neutral markers at the centre of each alert area; they disappear when the alert expires.
  • MEDEVAC / 9-Line. A MEDEVAC request sent from ATAK’s built-in tool is parsed into the 9-line format, shown on the map and relayed to TeamCO as an alert.
  • TeamCO overlay. Announcements, blockers and check-in/check-out actions for the linked TeamCO workspace are available from marker popups on the web map.

There is nothing to download. A member creates an Authentik App Password, opens tak.irregulars.io/enroll, scans the QR code with ATAK or iTAK, and signs in with their SSO username and that App Password. The server issues the phone a client certificate and it connects within a few seconds. The older data package / .p12 download is disabled. Full steps, the channel setup and a troubleshooting table are on the TAK Server page.

Signal bot → TeamCO → TAK Service → web maps + Data Sync missions (locations)
TAK Service → TeamCO (markers, geofence and MEDEVAC alerts as announcements)
TAK Service → TAK server (VPC bridge) (CoT, missions)
TAK Service → NWS (weather alerts)
TAK Service → Authentik (SSO login)
Phones → TAK server (tak-direct.irregulars.io) (CoT stream, enrollment)
  • TeamCO is the primary integration and is bidirectional: markers, geofence alerts and MEDEVAC requests from TAK become TeamCO announcements (friendly markers info, hostile markers alert); TeamCO check-ins and announcements appear on the map and in the workspace’s mission. Position updates from phones do not create announcements.
  • TAK server (OpenTAKServer) receives CoT and hosts the Data Sync missions the service publishes.
  • NWS supplies the weather alerts.
  • Authentik provides SSO for both web maps (tak.irregulars.io and map.irregularchat.com), and the App Passwords phones enroll with.
  • QR enrollment with SSO username + Authentik App Password replaced the data package download.
  • Every workspace is published as a Data Sync mission, synced every 15 minutes.
  • A phone’s positions are routed to its owner’s workspace maps once the owner has logged in to the web app.
  • One channel, ots_irregularchat, managed through Authentik groups.
  • Web map chat is disabled in favour of Signal.
  • TAK Server — Connect your phone, troubleshooting, architecture and API
  • TAK primer — General TAK introduction
  • TeamCO — Team coordination platform (primary integration)
ComponentTechnology
RuntimeCloudflare Workers (Hono)
DatabaseD1 (users, workspaces, markers, devices, geofences, missions)
Real-timeWebSockets via Durable Objects, one room per workspace
Sessions and cachesKV
StorageR2 (data package bucket; download path disabled)
AsyncCloudflare Queue tak-events → TeamCO Bot API
Server linkVPC Service Binding to the OpenTAKServer bridge
Scheduled workCron: NWS ETL and mission sync every 15 min, stale-device sweep hourly
AuthAuthentik OIDC via @irregularchat/shared-utils

Recent changes

  1. feat(tak-server): CloudTAK signs in with IrregularChat SSO Sac
  2. docs(wiki): TAK guide rewritten for how the service actually works Sac
  3. fix(tak-service): no TeamCO announcements for position shares; skip [TAK] echoes in mission logs Sac
  4. docs(tak): say plainly that phones appear on every workspace map Sac
  5. docs(wiki): enrich service pages with integrations, Signal commands, and dev history gitayam