Respond faster
Turn RF observations into cues fast enough to point other sensors or assets.
- Designed for tip-and-cue workflows
- Designed for event-driven cueing and track updates
SkyMesa Locus // receive-only RF backend
Turn RF observations into location cues your team can test.
SkyMesa Locus sits downstream of Guardian radar and partner RF sensors, turning observations into location cues, tracks, uncertainty, scan recommendations, and AAR logs.
Software only. Receive-only by design. Operator-in-the-loop by default.
Impact
Faster cueing, smaller search areas, and outputs that stay honest when conditions degrade.
Reduce search area
Stop searching 360 degrees and focus the hunt where it matters.
- Shrink scan sectors for confirmation and response
- Fewer false pursuits and wasted sorties
Avoid false confidence
When conditions degrade, confidence backs off instead of getting confidently wrong.
- Fails safe by inflating uncertainty or withholding cues
- Clear reasons recorded when quality drops
Reviewable results
Repeatable outputs that teams can understand, replay, and review after the mission.
- Built for evaluation-first pilots and AAR logs
- Designed to integrate into existing operator workflows
Use cases
Designed for defense and commercial operators that need spectrum-derived awareness.
Counter-UAS cueing
Turn RF activity into location cues that support confirmation and response workflows.
Persistent monitoring and anomaly detection
Understand activity, change, and anomalies over time with reviewable outputs.
Finding interference sources
Support incident response and mitigation by shrinking the search area.
RF-derived ISR cueing
Provide RF cues to support tip-and-cue workflows inside broader sensing systems.
How it fits into your stack
A simple pipeline: RF observations in, operational cues out.
Inputs
- RF observations, measurement products, or cue records
- Timing references, platform metadata, and scan context where available
SkyMesa Locus
- Receive-only geolocation, cueing, tracking, and uncertainty
- Scan recommendations configured around your mission objectives
Outputs
- Location cues, tracks, confidence, uncertainty bounds, and scan recommendations
- AAR logs and messages that plug into your existing tools (TAK/CoT as needed)
What you provide
- Representative RF observations, recorded data, or a live feed in your environment
- A target integration endpoint (C2, UI, or analytics pipeline)
- A short test plan that defines what success means
Outputs include uncertainty, confidence, and reason codes. When quality thresholds aren’t met, the system fails safe by withholding cues.
How we engage
Start small, prove value, then scale.
01
Quick evaluation
Fast Locus evaluation using recorded RF observations or a live feed.
- Time-to-first-cue integration support
- Unclassified evaluation report, cue examples, and uncertainty summary
- Integration notes and scan recommendation behavior (scope as agreed)
02
Paid pilot
Fixed-scope pilot (typical 8–12 weeks) with defined objectives and success criteria.
- Measured outcomes: time-to-cue, search-area reduction, track continuity, wrong-basin events
- Pilot results and recommended next-phase scope
- Acceptance artifacts: replayable logs, AAR logs, and evaluation report
03
Operational integration
Hardening, packaging, and system-level integration.
- Integration package and documentation
- Program-facing artifacts for review and sustainment
- Production licensing structured to match deployment needs
FAQ
Do you sell hardware?
SkyMesa is software-first. Guardian is the radar product, and SkyMesa Locus is the receive-only backend. Production deployments integrate behind your receiver, Guardian radar, partner RF sensors, or an integrator baseline.
Do you control the platform or payload?
No. Locus produces cues, tracks, uncertainty, confidence, scan recommendations, and reason codes. Your operator workflow or C2 decides actions.
Is this autonomous?
Operator-in-the-loop by default. Interfaces are designed to cue autonomy stacks when authorized, not replace them.
Is this a single platform solution or multi-sensor?
We support both. The right approach depends on mission constraints, geometry, and what sensors you already have.
Do outputs include uncertainty and traceability?
Yes. Outputs are designed for decision support with uncertainty, confidence, and audit-friendly metadata (including reason codes where applicable).
What happens when signal conditions degrade?
Outputs fail safe. If quality thresholds aren’t met, Locus inflates uncertainty or withholds cues and records why via reason codes.
What does an evaluation look like?
Evaluations start with representative RF data or a live feed, a short integration plan, and a time-boxed objective with clear success criteria.
What environments do you support?
We start with unclassified evaluation workflows and scale integration as requirements mature.
How do you integrate with C2?
We focus on clean interfaces and predictable outputs so your team can route cues into existing operator workflows.
Can you work with primes and integrators?
Yes. SkyMesa is designed to slot into larger systems and partner architectures.
About
SkyMesa Systems builds Guardian radar and SkyMesa Locus for defense and dual-use teams that need a fast path from RF observations to testable operational value.
Locus is our receive-only backend for RF geolocation, cueing, tracking, scan recommendations, uncertainty, and AAR logging.
SkyMesa software can be deployed at the edge for low-latency sensing workflows or integrated into larger enterprise, command, and analytics environments.
Our current work spans three connected areas:
SkyMesa Locus
Receive-only RF geolocation backend software for cues, tracks, uncertainty, scan recommendations, and AAR logs.
Guardian radar
Radar product work focused on adaptive detection performance under strict time and resource constraints.
Cross-domain sensing research
Translating aerospace-grade reliability into other signal-processing domains where calibrated confidence matters.
The common thread across our work is reliable detection, calibrated confidence, and fail-safe behavior when average-case assumptions break down.
Contact
For Locus evaluations, Guardian radar discussions, and unclassified integration questions, email us and we will propose a low-friction plan.