A "common operating picture" — one shared, real-time view of everything happening around you — has been standard in military and emergency operations for decades. The problem with most modern versions is simple: they assume the internet is up. When the network drops, the cell tower congests, or you're operating somewhere with no coverage at all, the picture goes dark exactly when you need it most. BlackAtlas is built around the opposite assumption. Here's how the products fit together to produce one picture that doesn't depend on a connection to anywhere.
The Problem With Cloud-Dependent Awareness
Most sensors, trackers, and mapping tools route their data through a vendor's servers. Your drone detector phones home; your team tracker syncs through an app backend; your map tiles stream from the cloud. In a connected office, that's invisible. In the field — a disaster zone, a remote search area, a site with jammed or saturated spectrum, a grid-down emergency — it's a single point of failure that takes the whole system with it.
There's also a quieter cost. When every device speaks its own proprietary format and reports to its own separate dashboard, you don't have a picture — you have five of them, none of which agree, each requiring its own screen and its own login. Correlating them is manual, slow, and error-prone, which defeats the purpose of situational awareness in the first place.
One Common Language: Cursor-on-Target
The thing that makes a single picture possible is a shared format. BlackAtlas products speak Cursor-on-Target (CoT) — the same lightweight messaging standard that underpins TAK (the Team Awareness Kit used widely across military, law enforcement, and search-and-rescue). CoT describes what something is, where it is, and when it was seen, in a compact form any CoT-aware client can plot.
Because every device emits the same kind of message, a drone detection, a vessel track, a teammate's position, and a sensor alert all land on the map as the same kind of object — no custom integration between each pair of devices, no translation layer you have to build and maintain. CoT is the lingua franca; everything else is a dialect of it.
One Hub: GridDown
If CoT is the language, GridDown is where the conversation happens. GridDown is the offline operating picture — a mapping and coordination client designed to run with no internet connection, holding its own map data locally and accepting CoT feeds from everything around it. Sensors, drones, and radios all converge here, so a single operator sees air, ground, sea, personal, and team data in one view rather than juggling separate apps.
The key word is offline. GridDown doesn't degrade gracefully when the network drops — it was built assuming the network isn't there. That's what makes it suitable as the center of a stack meant for grid-down and no-coverage conditions.
How Each Product Feeds the Picture
With the language and the hub in place, each product becomes a contributor to one shared view. Here's the role each plays:
| Product | Role in the picture | What it contributes |
|---|---|---|
| AtlasRF | Sense — full spectrum | Passive RF, airspace, vessel, and vehicle tracks, published as CoT |
| Sensor Hub | Sense — lighter, built for GridDown | A lighter AtlasRF-class detector feeding ADS-B, Remote ID, and emergency-beacon data to the map |
| AtlasGuard | Sense — personal | Pocket tracker / jammer / unknown-transmitter detection, plotted to GridDown over Bluetooth |
| AtlasBridge | Translate | Turns third-party sensor feeds into CoT/TAK so non-BlackAtlas gear shows up in the same picture |
| OpenGCS | Fly | Drone command-and-control with native TAK output, so vehicle telemetry appears on the map |
| Secure Messenger | Communicate | Encrypted LoRa mesh messaging that bridges team positions and messages onto the map |
| GridDown | The hub | The offline operating picture everything else converges on |
Sensing — From Full Spectrum to Pocket-Sized
AtlasRF is the heavy sensing layer: passive, multi-spectrum monitoring that detects and classifies what's in the air, on the water, and on the ground, then streams those tracks to the map as CoT. The Sensor Hub is a lighter, GridDown-oriented detector for users who want core airspace and emergency-beacon awareness without a full AtlasRF deployment. And AtlasGuard brings sensing down to the individual scale — a pocket device that flags hidden Bluetooth trackers, GPS jamming, and unknown transmitters, then connects over Bluetooth to plot what it finds on the same GridDown picture.
Translating — Bringing In Everything Else
No one runs an all-single-vendor operation, and BlackAtlas doesn't pretend otherwise. AtlasBridge is the universal translator: it ingests third-party sensor feeds and republishes them as CoT/TAK (and other C2 formats), so gear you already own can contribute to the same picture without custom engineering. It's the piece that keeps the ecosystem open rather than walled.
Flying — Drones as Part of the Picture
For programs that operate drones, OpenGCS is the ground control station, with native TAK support so a vehicle's position and telemetry flow into the same operating picture as everything else. Paired with the UAS Build Configurator and component database for building NDAA-aligned platforms, it closes the loop from "build the aircraft" to "see it on the map."
Communicating — Coordination Without Coverage
Secure Messenger handles the comms layer using encrypted LoRa mesh — radios that talk directly to each other with no cellular or internet. It also bridges to the map, so a teammate's position and messages live alongside the sensor and drone data rather than in a separate chat app. Combined with support for established off-grid standards like Meshtastic and APRS, it keeps a team coordinated when there's no infrastructure to lean on.
One Network You Control: AtlasGate
All of this rides on a network. AtlasGate is the routing layer — built from allied-nation components with no Chinese-origin parts in the signal chain, with cellular failover and intruder alerting — that puts every device on one private network, with no cloud in the loop. It's the floor the rest of the stack stands on: the thing that lets a sensor, a drone, and a radio reach the same GridDown instance without routing through anyone else's servers.
Why This Matters for the Way You Actually Operate
The practical payoff of a connected, no-cloud stack shows up in the field, not the spec sheet:
- It keeps working when infrastructure doesn't. Grid-down, no-coverage, or congested-spectrum conditions are when situational awareness matters most — and when cloud-dependent tools fail.
- One picture instead of five dashboards. Air, ground, sea, personal, drone, and team data converge on a single map, so an operator correlates at a glance instead of by hand.
- It grows with you. Start with one product; add others as needs expand. Because they share a language and a hub, each addition slots into the picture you already have rather than becoming another silo.
- You own the data path. Nothing has to leave your network for the system to function — which matters for privacy, for security, and for operating in places where "the cloud" simply isn't reachable.
Where to Start
You don't have to adopt everything at once, and most people don't. The natural entry point is GridDown itself — the hub that everything else plugs into — paired with whichever sensing or comms layer matches your mission. From there, the stack expands as your needs do, each piece speaking the same language and landing on the same picture. The point isn't to sell you seven products; it's that when you do add the next one, it makes the picture you already have better.
See How the Stack Fits Together
GridDown is the offline operating picture at the center of the BlackAtlas system. Explore the hub, then add the sensing, flying, and comms layers that match how you operate.
Explore GridDown