Rescue responder with comms headset maintaining situational awareness during helicopter operation
Search & Rescue Communications

Everyone Is Supposed to
Go Home at the End of the Op.

That isn't a slogan. It's the operational requirement that AT Labs was built around — because the gap between a team that's connected, visible, and coordinated and one that isn't isn't measured in inconvenience. It's measured in outcomes.

Why This Exists

The Gap Between Chaos and Accountability

When communications fail during a search and rescue operation, the mission doesn't pause. Teams keep moving. Sectors keep expanding. And somewhere out there, someone is waiting on a decision that can only be made if command knows where everyone is.

Early in AT Labs' founder's exposure to emergency services, a responder was lost during an incident. It took days before he was found. By the time he was located, the outcome was already decided.

In a different world — one with persistent visibility and accountability even when conditions collapse — that outcome might have looked different. Not guaranteed. But different.

That is what AT Labs builds toward. Not a world where loss is impossible, but one where preventable loss becomes harder to accept — because the tools exist to close the gap, and using them is a form of responsibility.

If you see danger and refuse to act, that is failure. AT Labs builds to prevent that failure.

The Operational Cost of Lost Comms
01

Coordination Delay

Degraded comms slow resource routing, slow task assignment, and slow the decisions that compress rescue timelines. Every minute of delay is a minute the victim doesn't have.

02

Loss of Team Visibility

When command loses track of where responders are, safety and accountability break down simultaneously. Decisions get made on guesses. Teams move into areas no one knows about.

03

Fragmented Accountability

Manual accountability methods — boards, radio check-ins, paper logs — collapse at operational tempo. The picture gets stale. The margin for error grows.

04

Duplicated or Missed Coverage

Without a shared operational picture, teams search the same ground twice or leave sectors uncovered. In a survival scenario, that gap is the difference.

The Problem with Standard Solutions

Why Existing Systems Break When You Need Them Most

SAR operations don't fail in controlled conditions. They push into exactly the environments that conventional communications were never designed for — and the gear fails accordingly.

Cell Networks

Coverage follows population, not terrain. Canyon walls, mountain ridges, dense vegetation, and hollow country all create dead zones in areas where SAR operations are most likely to occur.

In mass-casualty events and major disasters, cell infrastructure is simultaneously the most overloaded and most likely to be physically damaged — the moment the mission gets big enough to matter, the network gives out.

Infrastructure-dependent · Fails under load · Terrain-limited

Satellite Communications

Subscription costs run whether systems are used or not. Most configurations require clear sky view — functionally useless in canyon, canopy, or urban canyon environments.

Satellite comms also still depend on third-party infrastructure your team does not own or control. When the provider has an outage or prioritizes other traffic, you have no recourse.

Expensive · Sky-view dependent · Third-party reliant

DIY Mesh Nodes

Hobbyist LoRa boards and 3D-printed enclosures have moved mesh networking into the field, and they've proven the concept. But they are prototypes — fragile, inconsistent, and largely unsupported when something breaks mid-operation.

There is a significant difference between a proof-of-concept that works in good conditions and a tool you can trust when someone's life depends on the network staying up.

Fragile · Unsupported · Prototype-grade

AT Labs builds the gap-filler — rugged, subscription-free, out-of-box ready mesh communications designed for the environments where all three of the above break down.

The AT Labs Approach

A Capability Stack, Not a Device Sale

AT Labs doesn't build radios and call it a communications solution. The system is designed as a complete capability stack — each layer supports the ones above and below it, and the whole thing operates without any dependence on external infrastructure. What you bring to the scene is what you have. It's enough.

Layer 01

Field Devices

Ruggedized, man-portable mesh radios carried by individual responders and field teams. Each device maintains connectivity and location tracking through dynamic terrain — and every unit acts as a repeater, so the mesh extends as teams push forward.

Layer 02

Mesh / RF Network

The LoRa mesh backbone connecting field devices to each other and to command. Ad-hoc by design — no access points, no repeater infrastructure required. Messages, position data, and sensor traffic continue moving even as teams travel through terrain that kills conventional radio. Infrastructure nodes can be staged on ridgelines, vehicles, or forward positions to extend range as needed.

Layer 03

Local Incident Infrastructure

The TOC layer — a self-powered, vehicle-deployable platform running the TAK server, operational software, and the full software suite locally. No cloud. No internet required. The Response Crate brings up a complete command infrastructure the moment it's powered on, with fifteen radios charging simultaneously and the TAK server available within minutes of arrival on scene.

Layer 04

Team Tracking & Accountability

Real-time position and status visibility for every responder across the operational area. Command sees where teams are, where they've been, and whether they've checked in — continuously, not just when someone remembers to call. This is the layer that turns the mesh from a communications tool into an accountability tool.

Layer 05

Mapping & TAK Integration

A shared operational picture across ATAK, WinTAK, and iTAK — running locally without internet, kept current by the mesh below it. Command sees the search grid, team positions, and incident data in real time. SignalReach models repeater placement before the operation begins so optimal node positions are identified before boots hit the ground.

Layer 06

Training & Ongoing Support

A system is only as effective as the team that operates it. AT Labs and Constellation Response provide direct technical support, training for agency personnel, and ongoing operational guidance to ensure systems are configured for your mission profile and your team is ready to use them when it matters. No support ticket queue. Direct access to the people who built it.

Typical Deployment

From Staged to Operational in Minutes

AT Labs systems are designed for the gap between "wheels stop" and "radios out." The operational requirement is simple: the network should be up before your first team clears the staging area. The deployment sequence is designed to make that happen.

01

System staged at base, mobile command, or forward position

The Response Crate fits in a truck bed, trailer, or vehicle interior. It deploys from wherever the mission puts you — no permanent installation, no infrastructure prerequisites. Power on and the server stack comes up automatically.

02

Radios charge in their cradles as teams brief and gear up

Every RM-2 in the system charges while stored. By the time briefing ends and teams are ready to move, radios are at full charge — pulled from the crate and clipped to kit, not scrambled from a table full of loose cables.

03

Infrastructure nodes staged on terrain, vehicles, or forward positions

RM-1 and RM-2 infrastructure variants extend the mesh into terrain that field-portable units can't reach alone. Pre-sited during sector planning, they turn ridgelines and high ground into coverage assets — running on solar, requiring no maintenance during the op.

04

Teams move — the mesh moves with them

Every radio is a repeater. As teams push into the search area, they carry the network forward with them. Team positions update on the TAK picture in real time. Command has accountability without requiring field teams to stop and check in.

05

Operations scale without reconfiguration

Additional teams slot into the existing mesh. More Crate Minis expand radio capacity. The system scales to the incident without requiring technical reconfiguration in the field — because in the field, no one has time for that.

Hardware for the Mission

AT Labs Systems for SAR Teams

Every AT Labs product is designed around a single operational requirement: the network stays up, and command always knows where the team is. These are the tools that make that possible.

The Foundation

This Work Is Not Incidental

AT Labs was built on the conviction that every human life carries real value — and that if the tools exist to protect people in extreme situations, deploying them is a form of responsibility. This is not a hardware business dressed up in mission language. The accountability is genuine, the stewardship is deliberate, and the hardware reflects both.

Disasters do not care who you are or where you come from. When people need help, we show up — and we make sure the people going in to help them can be seen, heard, and brought home.

Talk to AT Labs Read the Founder's Letter