SpikeCamp crews on your TAK map

Four ways to connect

• Download for TAK Live today

  Any TAK user, no setup

  One tap on the command board downloads a data package. Open it in ATAK, iTAK or WinTAK and the crew appears, refreshing on the incident’s cadence (30 seconds to 10 minutes). Revoke it from the board at any time.

• Send to your TAK Server Live today

  Agencies with a TAK Server

  Command enters your server’s address and the client certificate your TAK admin issues. SpikeCamp streams Cursor-on-Target over TLS every 30 seconds, and everyone on your server sees the crew.

• SpikeCamp TAK Server In development

  Incidents with no TAK Server

  Command turns on SpikeCamp TAK and shows a QR code at briefing. Each ATAK or iTAK device scans it, gets its own certificate, and joins that incident’s group. No server to run.

• Federation In development

  Agency TAK admins

  Your TAK Server and ours federate once, admin to admin. Command shares an incident with your agency from the board, and it appears on your server. You control what you accept, and either side can end it.

What shows on TAK

• Each crew member as a friendly ground unit, with callsign, team color and Team Lead role
• Vehicles as ground vehicles
• The time, accuracy and battery of the last fix
• Markers that go stale on TAK when SpikeCamp marks someone dropped off
• An emergency (911) alert at the person’s position the moment they press SOS, until it is cancelled

How the SpikeCamp TAK Server will work

In development

1. 1
   Turn on SpikeCamp TAK

   On the command board, command turns it on for the incident. SpikeCamp creates a private group for that incident on the SpikeCamp TAK Server.

2. 2
   Scan the QR code

   At briefing, anyone with ATAK or iTAK scans the code. The device enrolls once, gets its own certificate, and joins only that incident’s group.

3. 3
   Crews appear

   SpikeCamp sends every crew position into the group every 30 seconds, with SOS alerts as they happen. TAK users see the crews; other incidents never see each other.

4. 4
   Turn it off or close the incident

   The QR code stops working and the devices’ certificates are revoked. TAK data is deleted after the incident’s retention period, 30 days unless command changes it.

For agency TAK admins

• Federation (in development)

  TAK Server federation v2 on port 9001 with mutual TLS. We exchange CA certificates once. Nothing is shared until command shares an incident with your agency, and only that incident’s group is sent. Your admin maps it to your own groups.

• Direct push (live today)

  Streaming CoT input on your server: TLS on 8089 with a client .p12 you issue, or plain TCP on 8087 for a test server. SpikeCamp checks the certificate when command saves it, sends a test push, and pauses after an hour of failures, showing why on the board.

• What we send

  Field members command can see. Never command members, never anyone demobilized or waiting for approval. Each person keeps the same CoT uid across every path.

• Paperwork

  A one-page federation packet with our security overview, CA, data handling and retention, and a contact. Ask and we will send it.

Security and privacy

• Every TAK connection uses mutual TLS with certificates. Enrollment on the SpikeCamp TAK Server uses a one-time password.
• One private group per incident, so incidents never see each other. Federation shares only the incidents command chooses.
• Certificates are stored encrypted and never shown in the app. Passwords for your .p12 are never stored.
• TAK data follows the incident’s retention, 30 days unless command changes it.

Questions

Connect your incident or agency

Run an incident on SpikeCamp and use Download for TAK today, or write to us to set up a push or federation with your TAK Server.

How crew tracking works: crew tracking.