Anti-jam mesh data links
Encrypted resilient tactical networking
Overview
Encrypted, anti-jam mesh data links that keep units, vehicles and unmanned systems connected in contested spectrum. Self-healing network topology with no single point of failure: the link layer that the rest of the battlefield architecture depends on.
The link layer the whole battlefield architecture depends on: encrypted, anti-jam and self-healing, with no single point of failure.
Capabilities
- Encrypted, anti-jam waveforms for contested spectrum
- Self-healing mesh topology across units, vehicles and unmanned systems
- Distinct from the software-defined-radio line: purpose-built tactical data links
- Scales from a patrol to a formation without re-architecture
- Keeps units connected through jamming and node loss: the resilient link layer that lets sensor fusion, unmanned systems and command all stay coordinated
- Removes the single point of failure a conventional network presents, so degrading one node never collapses the force's ability to fight connected
Specifications
| Type | Tactical mesh data link |
| Security | Encrypted / anti-jam |
| Topology | Self-healing mesh |
| Origin | Independent / non-aligned |
In depth
The tactical link layer
The product is a purpose-built tactical mesh data link, distinct from the software-defined-radio line. Its documented users are units, vehicles and unmanned systems, and its security characteristics are encryption and anti-jam waveforms for contested spectrum. The network layer is intended to carry the connections on which sensor fusion, unmanned control and command-and-control depend. The catalogue does not publish a radio frequency, throughput, range or node count. Those values therefore cannot be inferred from the word tactical or from the anti-jam description. What is stated is the network behaviour: the link is designed to keep the connected force coordinated when spectrum is contested, rather than relying on a fixed link that stops as soon as it is jammed. The specific waveform and interfaces must be matched to the buyer's units, vehicles, unmanned platforms and existing command architecture.
Self-healing topology
The defining topology is self-healing mesh. The detailed record describes it as a network across units, vehicles and unmanned systems with no single point of failure. It also states that the architecture scales from a patrol to a formation without re-architecture. In practical terms, the link layer is specified to continue serving a changing force structure rather than requiring a new network design for every increase in connected elements. That claim remains about topology, not an assurance that every node survives every form of attack. Configuration still has to establish the operating environment, security requirements, platform interfaces and command relationships. The source is independent and non-aligned, with one accountable team for integration, training and in-region sustainment. The exact network design remains tied to the units, vehicles and unmanned systems that the buyer intends to connect.
A link layer, not a radio substitute
The distinction from the software-defined-radio line matters. These are purpose-built tactical data links, not a general statement that any radio can provide the same network behaviour. Their documented job is to connect units, vehicles and unmanned systems through encrypted, anti-jam waveforms and a self-healing topology. Sensor fusion and unmanned control depend on those connections, but the link does not replace the sensors or the command application above it. The architecture is stated to scale from a patrol to a formation without re-architecture. It is also stated to have no single point of failure. Those are topology and growth claims, not published throughput, frequency or range values. The buyer still has to define the connected platforms, security requirements, spectrum environment and command interfaces. The independent, non-aligned source provides one accountable team for integration, training and in-region sustainment. That is the available support model for a network whose exact configuration is determined by the force using it.
Resilience has a defined boundary
Encryption, anti-jam waveforms and self-healing topology describe different parts of the link. Encryption addresses the protected tactical connection. Anti-jam operation addresses contested spectrum. Mesh routing addresses the loss of a node by avoiding a single point of failure. The catalogue presents these together as one tactical data-link layer for units, vehicles and unmanned systems. The same record is careful about what is not published. There is no universal frequency, throughput, range or node count in the product specification. A patrol and a formation are both named architectural scales, but the equipment, interfaces and network plan still have to be configured for the force. The independent, non-aligned source supplies one accountable team for integration, training and in-region sustainment. That gives the buyer a delivery and support path without turning the topology description into an unsupported performance figure.
Why Unstrat: the difference
Unstrat is the authorised global representative and distributor for this capability. It is already in service with a track record behind it, so you are buying something that has done the job elsewhere, not funding a first attempt. You are not the test bed.
Independent, non-aligned origin, with no political exposure to any major-power ecosystem.
One accountable team from first briefing through delivery and in-region sustainment.
Self-healing mesh topology: losing a node never means losing the network.
How it reaches you
Related capability
View all →
Procurement & sustainment
Classification and the end-user-certificate chain are confirmed before this capability is represented to your market.
Sourced from an independent manufacturer: no major-power disclosure rules or political conditions.
A single team responsible from first briefing through delivery: not a chain of foreign primes to integrate yourself.
Lifecycle support and operator training delivered in-region, building capability that outlasts the initial deployment.
Questions buyers ask
What is a tactical mesh data link?
It is the radio layer that keeps units, vehicles and unmanned systems on one network without a base station or a master node. Every radio relays for the others, so the topology heals itself and there is no single point whose loss takes the network down. Ours are encrypted and anti-jam by design, built for contested spectrum, and they are fielded as the link layer under sensor fusion, unmanned systems and command traffic rather than tested on a range.
Best MANET radio for a buyer outside US export arrangements
Silvus, Persistent Systems and DTC publish detailed and impressive numbers, and they deserve the respect. They also publish the conditions: US export restrictions on release to non-US persons, FCC authorisation limited to government use, AES-256 sold as a separate licence. Ours carry no US or European release approvals in the chain and are sustained in region. We do not yet publish node counts, throughput or latency, so insist on a side-by-side trial rather than taking either party's word.
Is encryption included or sold separately?
Ours are described as encrypted as delivered, with no separate licence to buy. For comparison, DTC orders AES-128 and AES-256 as separate part numbers and the standard Silvus build is DES-56 with AES-256 as an option. What we do not publish is the algorithm or a certification level, so if your requirement names FIPS or a national standard, settle it before contract rather than after.
Do mesh radios work when the spectrum is being jammed?
That is what they are built for. Ours use encrypted, anti-jam waveforms for contested spectrum, and the self-healing topology means jamming or losing a node degrades throughput instead of collapsing the network. Silvus goes further in public than we do by naming specific techniques such as interference cancellation and avoidance under its Spectrum Dominance suite. Our approach is not described technique by technique in public, which is deliberate and best discussed under a briefing agreement.
Mesh data links for unmanned ground vehicles and drone control
The link layer is where unmanned programmes usually break, because control traffic, video and command all compete on the same contested spectrum. Ours carries units, vehicles and unmanned systems on one self-healing mesh, and it is supplied by the same team behind our unmanned ground platforms and sensor-fusion suite. That means fewer integration interfaces and one supplier to hold responsible when a feed drops.
See: The link layer under unmanned and sensor systemsThe fused picture the mesh feeds
How many nodes can the mesh carry?
We scale from a patrol to a formation without re-architecture, but we do not publish a node count and will not borrow someone else's. Silvus documents 550-plus nodes and Persistent states no limit on hops or nodes with node entry under one second. Those are real published figures and a fair thing to test us against. Ask for ours under a trial agreement and put both networks under the same load.
See: Scale, throughput and latency rows, marked where unpublished
Alternative to Silvus StreamCaster for a non-aligned buyer
Ours is built for exactly that position: non-aligned origin, no third-country release approval in the chain, and in-region sustainment for spares and repairs. Be clear-eyed about the trade. Silvus publishes 550-node scaling, 7 ms average latency at 20 MHz bandwidth and a documented anti-jam suite; we do not yet publish comparable figures. The Silvus datasheet also notes the device is not FCC-authorised for non-government sale, and that exported units are subject to the laws of the destination country.
See: Country of manufacture and export conditions, row by row
What happens to the network when a node is destroyed?
Traffic reroutes and the network keeps running. Self-healing topology means losing a node costs you throughput rather than the force's ability to fight connected, which is the same principle Persistent describes for Wave Relay. A conventional network with a master node offers an adversary one target worth finding. A mesh does not.
Is a mesh data link the same thing as a software-defined radio?
No, and buying one when you need the other is a common and expensive mistake. Our mesh links are purpose-built tactical data links for networked units, vehicles and unmanned systems in contested spectrum. Our HF software-defined radios are a separate line for long-haul voice and digital traffic with no infrastructure at all. Most forces need both layers, and they answer different failure modes.
See: The tactical data-link lineThe HF software-defined radio line
Our MANET radios are American and every spare needs a re-export approval. What do we replace them with?
The hardware cost was never the real cost in that arrangement. Persistent notes that radios transmitting at 6 W or above are for military or international sales only and that release to non-US persons may be export-restricted, which puts every spare, firmware release and repair inside a foreign licensing process. Ours are non-aligned in origin, and the team that installs the network keeps it running from inside your region, so a replacement radio is a logistics question rather than a diplomatic one. Do the swap on evidence: run both networks side by side under jamming before you commit.
We are buying sensor fusion, unmanned ground vehicles and counter-drone at the same time. Should the data link come from the same supplier?
It usually should, because the mesh is not a subsystem you can quietly swap later. Sensor fusion, unmanned platforms and command traffic all sit on top of it, so a freeze on the radios freezes the force. Our mesh links, fusion suite and unmanned platforms come from one accountable team, which cuts the number of integration interfaces and removes the argument about whose fault a lost track was. Where you do need a third-party sensor in the picture, raise it early rather than assuming it will drop in.
See: How the mesh, fusion and unmanned layers fit togetherThe command-post picture the link layer supports
What should a border force buy to keep patrols, vehicles and drones on one network in an area with no cellular coverage?
A mesh, because it needs no infrastructure to exist between the nodes and creates its own coverage as the patrol moves. Ours carries dismounted units, vehicles and unmanned systems on the same self-healing network and scales as more patrols join, without redesigning it. Where the distances break line of sight entirely, an HF layer underneath is the sensible fallback rather than a heroic mesh hop. We supply both layers through one channel.
See: Mesh coverage without fixed infrastructureThe HF fallback layer for long distances
You do not publish throughput, latency or bands. How can we evaluate you fairly against Persistent Systems and Silvus?
By trial rather than by datasheet. Persistent publishes 100-plus Mbps and a 391 g chassis, Silvus publishes 7 ms average latency, and a buyer comparing pages line by line will notice we do not match that disclosure. We list those gaps for our own product team instead of filling them with numbers we cannot stand behind. Put our radios and theirs in the same jamming environment, on your terrain, and judge the result.
Can one mesh network grow from a company trial to a brigade without being redesigned?
That is the design intent: it scales from a patrol to a formation without re-architecture, so the pilot you run this year is the architecture you field later. We do not publish a maximum node count, so agree the growth path and test it during evaluation rather than assuming it. The practical constraint on most programmes is not the radios but the plan for spares, training and network management as the network grows.
Who keeps the network running in our country, and how fast can a damaged radio be replaced?
The same team that installs the network sustains it in region, which is the whole point of buying the link layer from a supplier with no alliance obligations. There is no re-export approval standing between a damaged radio and its replacement, and no foreign capital reviewing your firmware release. We do not publish a spares turnaround figure, so make it a contractual commitment rather than an assumption. Capability you cannot operate during a political disagreement is not capability.
See: Why a link layer is the wrong place for political riskThe wider secure-communications programme
Anti-jam mesh data links: questions
What are Anti-jam mesh data links?
Anti-jam mesh data links are Unstrat's Land (Land Domain) capability: Encrypted, anti-jam mesh data links that keep units, vehicles and unmanned systems connected in contested spectrum. Self-healing network topology with no single point of failure: the link layer that the rest of the battlefield architecture depends on.
How do Anti-jam mesh data links work?
Anti-jam mesh data links deliver their effect through Encrypted, anti-jam waveforms for contested spectrum, Self-healing mesh topology across units, vehicles and unmanned systems and Distinct from the software-defined-radio line: purpose-built tactical data links, capabilities matched to the requirement and confirmed under briefing rather than published.
Who makes Anti-jam mesh data links?
Anti-jam mesh data links are built by The Unmanned Systems Developer, whose focus is counter-uas, loitering munitions & unmanned aircraft. Unstrat represents The Unmanned Systems Developer to government and enterprise buyers worldwide as an independent, non-aligned prime vendor.
Who uses Anti-jam mesh data links?
Government and enterprise buyers acquire Anti-jam mesh data links to address communications failure after disasters across the land domain, matched to the mission and accountable to them, not to a foreign vendor's government.
Why choose Anti-jam mesh data links over a major-power alternative?
Anti-jam mesh data links are sourced from an independent, non-aligned manufacturer, so they carry no major-power disclosure rules, upgrade-locks or political ramifications. Concretely: Self-healing mesh topology: losing a node never means losing the network. The capability is accountable to you, not to a foreign vendor's government and its release schedule.
How are Anti-jam mesh data links procured, and where can it be exported?
The link layer the whole battlefield architecture depends on: encrypted, anti-jam and self-healing, with no single point of failure. Every engagement begins with a briefing, and export eligibility is confirmed per market under briefing rather than published. Where controlled capabilities are involved, the classification and end-user-certificate chain is confirmed first. Anti-jam mesh data links are then sustained in-region by one accountable team from briefing through long-term operation.