TAK Server
TAK Server
Section titled “TAK Server”The IrregularChat community runs a TAK (Team Awareness Kit) server for shared situational awareness. Members connect with ATAK (Android) or iTAK (iOS) and see each other, saved markers and TeamCO check-ins on shared maps.
There are two hostnames, and it matters which one you use where:
| Hostname | What it is | Used by |
|---|---|---|
tak.irregulars.io | The web app: login, enrollment page, web maps | Your browser |
tak-direct.irregulars.io | The TAK server itself | ATAK / iTAK on your phone |
The web app cannot carry TAK’s streaming port, so a phone pointed at tak.irregulars.io will never connect. Phones always talk to tak-direct.irregulars.io.
What is TAK?
Section titled “What is TAK?”TAK is a geospatial situational awareness platform originally developed for military use and now widely adopted by emergency services, search and rescue, event coordination, and community groups. Teams use it to:
- Share real-time positions on a map
- Drop markers and points of interest
- Coordinate movements and resources
- Sync shared data (missions) between devices
TAK clients communicate using Cursor-on-Target (CoT), an XML-based protocol for geospatial data. For a general introduction to the ecosystem see the TAK primer.
Connect your phone
Section titled “Connect your phone”The whole process takes about five minutes. You need an IrregularChat SSO account and either ATAK-CIV (Android) or iTAK (iOS) installed.
| Platform | App | Where to get it |
|---|---|---|
| Android | ATAK-CIV | Google Play, or TAK.gov |
| iOS | iTAK | App Store |
| Windows | WinTAK-CIV | TAK.gov |
| Web | tak.irregulars.io/map | Any browser, after SSO login |
Step 1: Create an Authentik App Password
Section titled “Step 1: Create an Authentik App Password”- Open sso.irregularchat.com/if/user/ and sign in.
- Go to Settings → Tokens and App passwords.
- Click Create App Password. Any name works (for example
TAK). - Copy the generated value straight away. It is shown once; if you lose it, delete it and create another.
You can revoke this App Password at any time from the same page without affecting your main account.
Step 2: Enroll the app
Section titled “Step 2: Enroll the app”Open tak.irregulars.io/enroll in a browser (SSO login required). The page shows QR codes for ATAK and iTAK.
ATAK (Android)
- Either scan the QR code with the phone’s camera (this opens ATAK), or in ATAK go to Settings → Network Connections and scan or import it there.
- When prompted, enter your SSO username and the App Password from Step 1.
- Wait a few seconds. The server issues a client certificate and the app shows Connected.
To add the server by hand instead of scanning:
| Setting | Value |
|---|---|
| Server address | tak-direct.irregulars.io |
| Port | 8089 |
| Protocol | SSL |
| Authentication | Turn on Use Authentication and Enroll for Client Certificate |
| Username / password | SSO username / App Password |
iTAK (iOS)
- In iTAK go to Settings → Network → QR Code and scan the iTAK QR code from the enrollment page.
- When prompted, enter your SSO username and the App Password.
- After a few seconds the server shows as connected.
Step 3: Turn on the channel
Section titled “Step 3: Turn on the channel”The server currently exposes one channel, ots_irregularchat. Admins add every enrolled user to it through two Authentik groups (ots_irregularchat_read and ots_irregularchat_write).
- In the app, open the channels screen for the server (ATAK: Settings → Network Connections → tap the server → Channels, or the Channels tool in the toolbar; iTAK: Settings → Servers → tap the server) and make sure
ots_irregularchatis switched on. - If the channel is not listed, ask an admin in Signal to add you to the groups. New memberships take a few minutes to appear.
- If the channel is listed but cannot be toggled on, delete the server in the app and enroll once more. The server snapshots your group membership at enrollment, so a phone enrolled before you were added has to enroll again.
Step 4: Set your callsign, team and role
Section titled “Step 4: Set your callsign, team and role”- ATAK: Settings → My Preferences (Callsign, Team, Role).
- iTAK: Settings.
Team colours are a convention agreed in the Signal group, not something the server enforces.
Step 5: Subscribe to a workspace (optional but recommended)
Section titled “Step 5: Subscribe to a workspace (optional but recommended)”Workspaces are the team maps on the web app (see Workspaces below). Every workspace is also published as a Data Sync mission on the server, named after the workspace. Subscribing gives your phone the workspace’s saved markers, its TeamCO check-in locations as waypoints, and its announcements as the mission log, refreshed every 15 minutes.
- ATAK: open the Data Sync tool → select the server → pick the workspace → Subscribe.
- iTAK: Data Sync / Missions → select the server → pick the workspace.
What to expect once connected
Section titled “What to expect once connected”- Your position appears on the web maps of the workspaces you belong to. Until your phone is linked to your account (this happens the next time you log in to
tak.irregulars.io), it appears on every map. - Markers dropped on any workspace web map are sent to every connected phone.
- A phone that has been offline first drains up to 24 hours of missed messages from its server-side queue when it reconnects. A burst of old traffic on reconnect is expected, not a fault.
- Chat on the web map is disabled. The community uses Signal for messaging.
On the web
Section titled “On the web”Two web maps, different jobs:
| Site | What it is | Sign in with |
|---|---|---|
| https://tak.irregulars.io | the workspace map: your team’s saved markers, TeamCO check-ins and announcements, phones on your workspaces (MIL-STD-2525 symbols with team colour, shapes drawn on phones, 911 alerts, read-only TAK chat, five basemaps, MGRS readout) | IrregularChat SSO |
| https://map.irregularchat.com | CloudTAK, a full TAK client in the browser: drawing, range & bearing, range rings, routes, GeoChat, Data Sync missions, iconsets, KML/GPX import | the Sign in with IrregularChat SSO button (same account as everything else), or your SSO username and an Authentik App Password |
CloudTAK talks to the same server as the phones, so what you draw there reaches ATAK/iTAK and
the workspace missions. The SSO button is answered by our own small service (tak-sso), because
no CloudTAK release implements it; your first SSO sign-in also enrols the certificate CloudTAK
uses to speak to the server for you. If it says your account is not in the TAK directory yet,
ask an admin to add you to a channel group. Known gaps against our server: video streams and file/data-package
upload.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Fix |
|---|---|---|
| Enrollment succeeded but nothing shows / app says not connected | The app is streaming to the wrong port (an older QR code pointed it at 8446, the enrollment port) | Delete the server in the app and re-scan the current QR code |
| “0 available channels” | You are not in the channel groups yet, or your phone enrolled before you were added | Ask an admin to add you; then delete the server in the app and re-enroll |
| “peer did not return a certificate”, or connects and immediately drops | The app has no client certificate for this server | Re-enroll with Enroll for Client Certificate turned on |
| “identity could not be verified” during enrollment | Wrong hostname (must be tak-direct.irregulars.io), or an old app version without ISRG Root X1 in its trust bundle | Check the hostname; update the app |
| Position not shown on the web map | iOS Location permission for iTAK is off or not precise; or the map was opened before the phone reported | Set Location to While Using with Precise on; positions load when the map opens and update every minute |
| Data Sync shows no missions | Not subscribed, or no server selected in the Data Sync tool | Select the server in Data Sync and subscribe to a workspace |
| Your phone shows on other workspace maps but not on your own | The phone is not yet linked to your account | Log in to tak.irregulars.io once; the link is made at login |
Workspaces and web maps
Section titled “Workspaces and web maps”Web maps live at tak.irregulars.io/map (login required). The full list is at /map?manage=1, and opening a /map/<slug> link joins you to that workspace automatically. !teamco create <name> in a Signal group creates a TeamCO workspace with a linked TAK map and replies with the link.
A workspace holds a team’s saved markers, TeamCO check-in locations and announcements. Every workspace is also a Data Sync mission on the server (see Step 5 above). Chat on the web map is disabled; use Signal.
For how the service fits together with TeamCO and the Signal bot, see the TAK Service page.
Architecture (operators)
Section titled “Architecture (operators)”Browser ──▶ tak.irregulars.io (Cloudflare Worker) │ Web maps, enrollment page, OIDC auth (Authentik SSO) │ Markers, workspaces, missions, geofences (D1) │ Live map updates per workspace (Durable Objects WebSocket) │ NWS weather ETL + Data Sync mission sync (cron, every 15 min) │ TeamCO bridge (Queue → TeamCO Bot API) │ └──▶ VPC Service Binding ──▶ bridge ──▶ OpenTAKServer (Proxmox, Docker)
Phones ─────▶ tak-direct.irregulars.io (DNS-only A record, no Cloudflare proxy) :8089 CoT stream (TLS, client certificate required) :8446 Certificate enrollment (nginx, Let's Encrypt certificate) :8443 Marti APIPhones reach OpenTAKServer directly. There is no Cloudflare Tunnel, Spectrum or step-ca in the phone path: tak-direct.irregulars.io is a grey-cloud DNS record pointing at the host, and the three ports above are open to the internet. Cloudflare’s HTTP proxy cannot carry 8089 or 8446, which is why the phone-facing hostname is separate from the web app. The Worker reaches the server through a private VPC Service Binding to a bridge, not over the public ports.
Enrollment on 8446 checks the SSO username and App Password against Authentik through its LDAP outpost (tak-ldap-outpost) and issues a client certificate signed by the server’s CA; that certificate is what the phone then presents on 8089. The Let’s Encrypt certificate on 8446 is why an app needs ISRG Root X1 in its trust store.
Cloudflare services used
Section titled “Cloudflare services used”| Service | Purpose |
|---|---|
| Workers | Web app, API, auth |
| D1 | Users, workspaces, markers, devices, missions, geofences |
| KV | Sessions, position cache, rate limiting |
| R2 | Data package bucket (the download path is disabled) |
| Durable Objects | Per-workspace WebSocket map rooms |
| Queues | tak-events, async delivery to TeamCO |
| VPC Services | Worker-to-server bridge |
| Cron triggers | NWS ETL and mission sync (15 min), stale-device sweep (hourly), daily maintenance |
The Worker exposes a REST API to logged-in users (session cookie tak_session). Every write takes a workspace slug and requires membership in that workspace.
# List markers in a workspacecurl "https://tak.irregulars.io/api/markers?workspace=alpha" \ -H "Cookie: tak_session=YOUR_SESSION"
# Create a saved markercurl -X POST https://tak.irregulars.io/api/markers \ -H "Content-Type: application/json" \ -H "Cookie: tak_session=YOUR_SESSION" \ -d '{"workspace":"alpha","title":"Rally Point","cot_type":"a-f-G-U-C","lat":43.615,"lon":-116.202}'
# Publish a CoT event (forwarded to every connected phone)curl -X POST https://tak.irregulars.io/api/publish \ -H "Content-Type: application/json" \ -H "Cookie: tak_session=YOUR_SESSION" \ -d '{"workspace":"alpha","title":"Checkpoint","cot_type":"a-f-G","lat":34.0,"lon":-118.0}'Publishing is rate limited to 60 requests per minute per user.
CoT type codes
Section titled “CoT type codes”CoT types follow the format a-{affiliation}-{dimension}-{function}:
| Affiliation | Code | Colour |
|---|---|---|
| Friendly | f | Blue |
| Hostile | h | Red |
| Unknown | u | Yellow |
| Neutral | n | Green |
| Dimension | Code |
|---|---|
| Ground | G |
| Air | A |
| Sea/Surface | S |
Common types: a-f-G (friendly ground), a-f-G-U-C (friendly ground unit, combat), a-h-G (hostile ground), a-u-G (unknown ground).
WebSocket stream
Section titled “WebSocket stream”Each workspace has a live room at wss://tak.irregulars.io/ws/<workspace-slug>. The web map uses it; you can subscribe to it directly with a valid session.
const ws = new WebSocket('wss://tak.irregulars.io/ws/alpha');ws.onmessage = (event) => { const data = JSON.parse(event.data); console.log('event:', data.type, data.payload);};Message types: markerCreated, markerUpdated, markerDeleted, positionUpdate, deviceOnline, deviceOffline, userJoined, userLeft, missionChange, geofenceAlert, weatherAlert, medevacRequest.
Missions
Section titled “Missions”Every workspace is mirrored to OpenTAKServer as a Data Sync mission of the same name. A cron job every 15 minutes pushes the workspace’s saved markers and TeamCO check-in locations into the mission and mirrors new TeamCO announcements into the mission log (announcements prefixed [TAK] are the web map’s own echo of markers and are skipped).
- List and inspect via
/api/missions(workspace-scoped; membership required) - Change log at
/api/missions/:name/changes?since=<ISO8601>(defaults to the last 24 hours, up to 500 entries)
curl "https://tak.irregulars.io/api/missions/Alpha/changes?since=2026-04-17T00:00:00Z" \ -H "Cookie: tak_session=YOUR_SESSION"Geofences
Section titled “Geofences”Geofences are polygons on the map. When a tracked device crosses one, an alert fires in real time over the workspace’s WebSocket room (geofenceAlert) and is forwarded to the linked TeamCO workspace as an announcement (alert for critical severity, warning otherwise).
- CRUD at
/api/geofences; body{ workspace, name, geojson, alert_type?, severity? }wheregeojsonis a GeoJSONPolygon - Up to 50 geofences per workspace
- Every incoming position is evaluated against the workspace’s active geofences
curl -X POST https://tak.irregulars.io/api/geofences \ -H "Content-Type: application/json" \ -H "Cookie: tak_session=YOUR_SESSION" \ -d '{ "workspace": "alpha", "name": "Exclusion Zone Alpha", "geojson": {"type":"Polygon","coordinates":[[[-116.20,43.61],[-116.19,43.61],[-116.19,43.62],[-116.20,43.62],[-116.20,43.61]]]}, "alert_type": "entry", "severity": "high" }'Weather alerts (NWS)
Section titled “Weather alerts (NWS)”Every 15 minutes the Worker ingests active alerts from the National Weather Service API. Each alert becomes a neutral ground marker (a-n-G) at the centroid of the alert polygon, with the headline and severity in the description. Markers are removed when the alert expires, and new alerts broadcast a weatherAlert message to connected map viewers.
MEDEVAC / 9-Line requests
Section titled “MEDEVAC / 9-Line requests”ATAK’s built-in MEDEVAC tool sends a CoT event with a <medevac> detail block. The Worker parses it into the standard 9-line structure, stores it, broadcasts a medevacRequest message, and relays it to the linked TeamCO workspace as an alert announcement. Use the app’s own 9-Line form; it handles the CoT formatting.
Integration with TeamCO
Section titled “Integration with TeamCO”TAK and TeamCO share the same Authentik SSO and are linked per workspace: each TAK workspace maps to one TeamCO workspace, so announcements and alerts land in the right team rather than one shared channel.
TAK → TeamCO. Publishing a marker from the web map stores it in D1, broadcasts it to the workspace room, forwards the CoT to OpenTAKServer for phones, and queues an event on tak-events. The queue consumer posts an announcement to TeamCO’s Bot API (/api/bot/announce) as the tak-bridge system user: friendly markers become info announcements, hostile markers become alert. Geofence and MEDEVAC events follow the same path. Plain position updates from phones do not create announcements.
TeamCO → TAK. TeamCO check-in locations (!teamco checkin, !teamco setloc) appear on the linked workspace’s web map, and the 15-minute mission sync pushes them to subscribed phones as waypoints. TeamCO can also post raw CoT through the ingest API:
curl -X POST https://tak.irregulars.io/api/ingest \ -H "Authorization: Bearer <TAK_API_KEY>" \ -H "Content-Type: application/xml" \ -d '<event version="2.0" uid="..." type="a-f-G" ...>...</event>'Backend: OpenTAKServer
Section titled “Backend: OpenTAKServer”The server is OpenTAKServer running in Docker on the IrregularChat Proxmox host, with a bridge alongside it that the Worker reaches over the VPC Service Binding. The bridge also exposes the device-to-user mapping the Worker uses to route a phone’s positions to its owner’s workspaces.
| Port | Purpose |
|---|---|
8089 | TLS CoT stream for phones; client certificate required |
8446 | Certificate enrollment (nginx in front, Let’s Encrypt certificate) |
8443 | Marti API |
User accounts and the ots_irregularchat channel come from Authentik: the two groups ots_irregularchat_read and ots_irregularchat_write control read and write access, and the server snapshots a user’s groups when their phone enrolls.
Use cases
Section titled “Use cases”- Event coordination. Stand up a workspace for a meetup or field exercise to track attendees, mark locations and coordinate movement.
- Emergency response. Mutual-aid coordination: track responders, mark hazards, run logistics.
- Training exercises. Blue/red team markers, movement tracking, after-action review from the change log.
- Mesh networking. Pair TAK with Meshtastic LoRa radios for off-grid awareness; Meshtastic nodes can relay positions into TAK through the ingest API.
Security
Section titled “Security”- Web traffic is TLS via Cloudflare; phone traffic on 8089 is mutual TLS with per-device client certificates issued at enrollment
- Login is IrregularChat SSO (Authentik OIDC); phones authenticate with a revocable Authentik App Password, never the account password
- Position data is cached for 5 minutes; devices unseen for an hour are marked stale; saved markers persist in D1
- Publishing is rate limited (60 requests per minute); certificate operations to 5 per hour
- Location data is sensitive and is shared only with authenticated community members in the same workspace or channel
Related resources
Section titled “Related resources”- TAK primer — What TAK is and how the ecosystem fits together
- TAK Service — How the web app, TeamCO and the Signal bot work together
- TeamCO — Team coordination platform
- Tactical Technology — Broader tactical tech overview
- Authentik — SSO setup guide
- TAK.gov — Official TAK downloads and documentation