Four layers. One pipeline.
The system
Each layer is useful on its own. Run together, they close the gap between receiving capability and being able to use it.
What each layer hands to the next
01SEIDR Ravens
A characterized payload: center frequency, channel plan, modulation, and a vulnerability profile. The nodes are configured from what SEIDR measured rather than from a datasheet nobody has.
02Ravens Raven Net
Placement. Nodes deployed by hand, vehicle, or drone form the mesh themselves, so coverage is a consequence of where they were left, not of infrastructure that had to be erected.
03Raven Net Raven Eye
Every node’s sensing and status over an out-of-band link, so the operating picture holds when the primary path is unavailable, monitored, or jammed.
04Raven Eye the unit
A correlated picture on one screen, and Cursor on Target into the TAK ecosystem the unit already runs. No manual re-entry, no reach-back.
Which one you need
| System | What it is | Reach for it when | Instead of | Measure |
|---|---|---|---|---|
| SEIDR | A portable RF characterization and vulnerability assessment lab. | You have a payload and no trustworthy documentation for it. | Shipping hardware to a CONUS lab and waiting weeks | Under 60 minutes per payload |
| Ravens | Two deployable nodes for persistent RF sensing and effect. | You need continuous coverage somewhere you cannot stay. | Holding a position with a person, or accepting a coverage gap | 72+ hours per node on duty cycle |
| Raven Net | A self-forming mesh network that needs no infrastructure. | Your primary C2 is unavailable, monitored, or jammed. | Standing up infrastructure you cannot conceal | Forms itself in minutes from placement |
| Raven Eye | An offline-first command and sensor fusion console. | You are fusing several feeds and cannot assume connectivity. | Correlating feeds by hand and re-entering them into TAK | Full capability with no network at all |