SynapseCommand Integration with TAK Server
TAK Server is the distribution point of a TAK deployment: it moves situational awareness between tactical clients and the systems around them. SynapseCommand connects to that exchange through a published adapter and adds analysis, options and an inspectable decision record above it, without changing how the tactical picture itself is shared.
What TAK Server is
The Team Awareness Kit is a family of situational awareness applications published through the TAK Product Center. TAK Server is the server component of that family. It authenticates clients, distributes situational awareness between them and connects a TAK deployment to the wider information environment.
The exchange currency of the ecosystem is Cursor-on-Target: a compact event that says what, where, when and for how long the report should be believed. The format is deliberately small because the bearers at the tactical edge are constrained, intermittent and frequently contested. A server holding that traffic therefore holds a live, low-latency view of where friendly and reported entities are.
TAK Server deployments are owned and accredited by the organisation running them. Access to a given server, its certificates and the networks it sits on is controlled by that organisation. Nothing on this page describes access that Decent Cybersecurity holds, or a deployment that has been completed on behalf of a government customer.
Your C2 stays. SynapseCommand adds the decision layer.
SynapseCommand does not replace TAK Server and does not attempt to become the tactical picture. TAK Server remains the distribution mechanism and the tactical clients remain the user environment. SynapseCommand attaches as a further consumer and producer of the same event stream.
What SynapseCommand adds sits one level above data exchange. Events arriving from the server are normalised into the canonical data model with their source, timing and reported confidence preserved, then examined by specialist agents. The products of that analysis, where a customer chooses to return them, can be published back as events the same clients already understand.
The relevant SynapseCommand component is the TAK adapter published in the open integration layer under Apache 2.0. The adapter, its data model and its validation harness can be read before any commitment is made, which is the point of publishing them.
- 01TAK ServerExisting deployment, unchanged. Owned and accredited by the operating organisation.
- 02Authorised tactical data exchangeCursor-on-Target events exchanged under the deployment's own certificate and access policy.
- 03SynapseCommand integration layerPublished TAK adapter, covered by the open validation harness.
- 04Canonical data modelSource, timing, classification and reported confidence preserved on every entity.
- 05Operational understandingTactical reporting deconflicted and held over time rather than as isolated events.
- 06Specialist agentsBlue force analysis and ISR fusion working on the same normalised picture.
- 07Decision supportRisks, constraints and options presented with the reasoning attached.
- 08Human decision gateThe commander or authorised operator decides. The platform does not.
- 09Decision record and replayAppend-only record of what was known, what was recommended and what was approved.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Persistence over a transient picture
Cursor-on-Target events expire by design. SynapseCommand keeps the history behind the current picture, so behaviour over hours can be examined rather than only the last position report.
Multi-agent analysis
Blue force and ISR agents work the same normalised picture in parallel, each producing a separately attributable contribution rather than one unexplained answer.
Decision support at reachback
Analysis that is too heavy for an end-user device runs where the compute is, while the tactical clients keep doing what they do well.
Disconnected operation
Models run self-hosted inside the deployment boundary with no external calls at runtime, which matters on a network designed around intermittent bearers.
Human-controlled decision gates
Nothing is published back into a tactical picture as a result of agent analysis unless an authorised human has approved it.
Decision record and replay
The sequence of information, analysis and authorisation is recorded so an action can be reconstructed afterwards for review or assurance.
How the decision cycle runs
Tactical reporting to operational understanding
Events from the server are normalised, deconflicted against other sources and held with their provenance, so analysis starts from a picture whose origin is explicit rather than assumed.
Detection to assessment
Where a reported contact matters, agents assess it against the wider picture, recent history and the stated commander's intent, instead of leaving the judgement to a single symbol on a map.
Assessment to option
Candidate responses are developed and compared on explicit criteria, with the constraints that shaped them visible to the staff reviewing them.
Option to authorised action
An authorised human approves or rejects. Only then is anything returned to the tactical picture, and the approval itself is part of the record.
Action to review
The full sequence is replayable, which supports after-action review and lessons work without reconstructing events from memory.
How this sits in a real environment
Where SynapseCommand sits
SynapseCommand is deployed inside the customer's own boundary, alongside or behind the TAK Server rather than in front of it. It is a further authorised client of the exchange, not a proxy that tactical clients must traverse.
Access and authorisation
Connecting to a TAK Server requires the operating organisation to issue access under its own certificate and policy regime. That is a customer decision and a prerequisite for any integration work.
Bandwidth and degradation
The decision layer is designed to degrade with the bearer rather than fail with it. When reachback is lost, tactical exchange continues and SynapseCommand resumes from the record when connectivity returns.
Classification boundary
SynapseCommand is designed for deployment up to NATO SECRET in accredited environments. The classification of a given TAK deployment determines where the decision layer can be installed and what may cross between them.
Where the data goes, and where it does not
- SynapseCommand runs self-hosted. Models execute inside the accredited boundary and there are no external AI calls at runtime, so tactical reporting drawn from a TAK deployment does not leave the environment in order to be analysed.
- Records of what was known, what was recommended and what was authorised are held append-only and, in assured deployments, ML-DSA-signed, so a decision sequence can be shown to be unaltered after the fact.
- Access to the adapter, the data model and the validation harness is public. Access to any customer TAK deployment is not, and remains entirely with the organisation that owns it.
What is claimed, and what is not
A specific working SynapseCommand adapter exists for the named system.
A TAK adapter is published in the SynapseCommand open integration layer. It reads and produces Cursor-on-Target events, the exchange format TAK Server distributes to its clients, and it is covered by the public validation harness. No end-to-end deployment against a government-operated TAK Server has been completed, so the claim is limited to the adapter itself.
Qualification
Adapter availability describes SynapseCommand software only. It does not imply certification, endorsement or accreditation by the TAK Product Center or any government authority, and deployment requires authorised access to the relevant server environment.
- publication · 2026-08-25 · direct evidence
SynapseCommand integration layer published under Apache 2.0
The canonical data model, JSON Schema, reference adapters, SDK and validation harness are published for independent inspection.
Interfaces and data standards
The data contract behind these interfaces is published for inspection in the open integration layer.
What SynapseCommand implements for each of these standards, with the direction of exchange and the source files behind it:
Interfaces and data standards
The relationship described here rests on Cursor-on-Target, the exchange format used across the TAK ecosystem, and on the TAK adapter published in the SynapseCommand integration layer. Other SynapseCommand interfaces, including ASTERIX and the STANAG track and GMTI formats, are not claimed as TAK Server interfaces. Dedicated interoperability documentation for Cursor-on-Target and the TAK interfaces will be added to the SynapseCommand interoperability catalogue.
The SynapseCommand data contract is published for inspection in the open integration layer.
Open interoperability layer
SynapseCommand connects to external systems through an openly published interoperability layer rather than proprietary point interfaces. The canonical data model, the JSON Schema and the format adapters are inspectable before any integration is committed to. That layer describes what SynapseCommand implements; it is not a statement about TAK Server and implies no interface to it.
Public sources
Factual statements about the named system on this page are drawn from these public sources.
Frequently asked
- Does SynapseCommand replace TAK Server?
- No. TAK Server continues to authenticate clients and distribute situational awareness. SynapseCommand attaches as a further authorised participant in that exchange and adds analysis and decision support above it.
- What would a SynapseCommand and TAK Server integration require?
- Authorised access to the server under the operating organisation's certificate and access policy, agreement on which events may be consumed and whether any analytical product may be returned, and a deployment location for SynapseCommand inside the accredited boundary.
- What is the current status of SynapseCommand alongside TAK Server?
- Adapter available. A TAK adapter is published in the SynapseCommand open integration layer, reads and produces Cursor-on-Target events and is covered by the public validation harness. No end-to-end deployment against a government-operated TAK Server has been completed.
- Can SynapseCommand operate alongside an existing TAK deployment?
- That is the intended pattern. The deployment keeps its own architecture, accreditation and user experience, and the decision layer is added beside it rather than in place of it.
- Is the integration officially certified?
- No. Nothing here is certified, endorsed or accredited by the TAK Product Center or any government authority. The published adapter is SynapseCommand software and is described as such.
- Does SynapseCommand publish anything back into the tactical picture automatically?
- No. Any product returned to a tactical picture passes an authorised human decision gate first, and both the product and the authorisation are recorded.
Where to go next
Relevant use cases
Discuss an integration
Briefings are available under NDA. SynapseCommand® integration work begins from the published data contract, so the interface can be reviewed before any commitment.
Third-party systems and trademarks
Product names, trademarks and registered trademarks referenced on this site are the property of their respective owners. References to third-party systems describe implemented, planned or potential technical interoperability as stated on each page and do not imply sponsorship, certification, endorsement or partnership unless expressly stated.
Category: Tactical edge. Last reviewed 2026-09-06.