Back to RTG Spectrum

Platform Overview

Collectors, shared events, Pattern-of-Life, and operator decisions.

RTG Spectrum turns RF and wireless observations into a source-aware event plane: collect, normalize, correlate, establish baseline, detect change or anomaly, and support operator decisions.

60-second architecture

Specialized modules feed Trace Analyzer as the shared event plane.

Each module keeps its purpose and evidence type, but the output is made reviewable in a common timeline. That is the difference between a set of demos and a platform.

Collection and application modules

SDR-Shark

Spectrum collection, IQ replay, FFT, waterfall, scanner workflows, signal activity, and RF/ML hooks.

RF Sentinel

Multi-protocol RF detections, entity tracking, WiFi topology, Bluetooth Classic, BLE, Zigbee, FM, and sub-GHz events.

AirScope

HaLow and WiFi observations, AP/station topology, survey state, Pattern-of-Life indicators, and report exports.

PASSIVE-SHIELD

Defense prototype cues, passive DJI/OcuSync-family RF evidence, acoustic corroboration, station state, and operator map context.

Module outputs become timestamped, source-aware events

Trace Analyzer

Unified timeline and Pattern-of-Life layer for BLE, GPS, WiFi, RF, spectrum, and mission events. Cellular 4G/5G event-family support is planned.

Correlate events, establish baseline, detect change, support decisions

What moves between modules

Events, not screenshots, are the platform interface.

The important boundary is the event model: source, timestamp, protocol, identity, signal, location or context where available, and raw detail for review. This lets a reviewer compare a WiFi AP, BLE observation, spectrum event, passive drone-signal cue, and operator status without flattening away where the evidence came from.

Trace Analyzer unified timeline showing source-aware RF wireless GPS and mission events

Buyer outcomes

What the platform helps teams do.

Reduce manual RF triage

Put detections, entities, health, topology, and raw detail into interfaces a reviewer can inspect quickly.

Establish baselines

Track recurring infrastructure, normal timing, known devices, channel use, and survey-to-survey behavior.

Detect change

Surface new, missing, recurring, anomalous, or mission-relevant activity with source context attached.

Correlate sensors

Review WiFi, BLE, RF, GPS, spectrum, and prototype mission cues together instead of in isolated dashboards.

Produce evidence

Create screenshots, exports, reports, and claim-boundary notes that support engineering, partner, or SBIR-style reviews.

Transition faster

Use Dockerized demos, replay data, health/status views, and repeatable workflows to move prototypes toward field testing.