A new open-source project promises phased array radar at a fraction of commercial costs. The hardware design is real. The software ecosystem to make it useful? That's another story.
Commercial phased array radar systems start at around $250,000. The AERIS-10, an open-source project published on GitHub, aims to deliver similar core capabilities at what its creator estimates is 90–95% less. It operates at 10.5 GHz, uses pulse linear frequency modulation, and comes in two configurations: a 3 km version and a 20 km extended-range variant. For IoT developers and remote sensing researchers who've been priced out of radar experimentation, AERIS-10 is the first project to publish complete schematics, PCB layouts, firmware, and host software for a phased array system you can actually build.
But "can build" and "should build" are separated by a canyon of RF engineering expertise, FPGA programming, and integration work that the project's current alpha state doesn't bridge. Here's what the AERIS-10 actually delivers, where it falls short, and what it would take to make open source radar a practical tool for the broader developer community.
What PLFM Radar Is and Why It Matters
Phased array radar uses an array of antenna elements whose signals are combined with precise phase shifts, steering the radar beam electronically rather than mechanically. This enables near-instant beam repositioning, multi-target tracking, and resilience in adverse conditions. It's the technology behind modern air traffic control, missile defense, and advanced weather radar.
The AERIS-10 specifically uses Pulse Linear Frequency Modulation, or PLFM. Where a simple pulse radar sends a short burst and listens for echoes, PLFM sweeps the transmitted pulse across a range of frequencies. This "chirp" signal can be compressed on receive, giving you the range resolution of a very short pulse without needing the enormous peak power that a short pulse demands. The result is better sensitivity and range from modest hardware.
Here's how PLFM compares to the alternatives:
- Continuous-wave (CW) Doppler systems excel at measuring velocity but struggle with range measurement.
- Simple pulse-Doppler designs trade off between range and velocity resolution.
- PLFM delivers both range and Doppler information simultaneously, which is why it's the modulation scheme of choice for serious radar work.
The tradeoff is complexity: you need precise frequency synthesis, careful timing, and substantial signal processing to extract useful data from the returns.
The Hardware: Modular, Ambitious, Not Simple
The AERIS-10's architecture, documented on its GitHub repository, is built around several specialized boards. A frequency synthesizer board uses an AD9523-1 low-jitter clock generator to supply phase-aligned references across the system. A power management board handles voltage regulation and sequencing. The extended-range AERIS-10E version adds 16 power amplifier boards, each featuring a 10-watt QPA2962 GaN amplifier.
The antenna configurations differ between versions. The 3 km AERIS-10N (Nexus) uses an 8×16 patch antenna array. The 20 km AERIS-10E steps up to a 32×16 dielectric-filled slotted waveguide array, as detailed on the project's Hackaday.io page. Both support electronically controlled elevation beam steering, though the current prototype uses a stepper motor for azimuth scanning. The project notes that the design can be modified for full electronic steering in both axes.
On-board FPGA signal processing handles pulse compression and initial data reduction. A Python GUI provides the host interface, outputting range and Doppler data for multiple targets.
Decoding the 20 km Range Claim
Range claims in radar are always conditional. A radar's maximum detection range depends on target radar cross-section, atmospheric conditions, antenna gain, transmit power, and processing gain. The 20 km figure for the AERIS-10E assumes the GaN power amplifier boards are populated and functioning, the slotted waveguide array is properly fabricated, and you're looking at a reasonably reflective target in clear conditions. A small drone at 20 km in rain? Almost certainly not. A cooperative reflector or a large aircraft in clear air? More plausible.
The 3 km Nexus version, with its simpler patch array and lower transmit power, is the more realistic starting point for most builders.
The Real Cost: Money, Time, and Expertise
The project's Hackaday listing positions the AERIS-10 as costing 90–95% below commercial alternatives. Even if the bill of materials lands in the low thousands, the total cost of ownership includes several factors the price tag doesn't capture.
First, the RF components. Parts like the AD9523-1, ADF4382, LTC5552, and ADTR1107 are specialized and sometimes supply-constrained. Zendot's technical breakdown of the AERIS-10 build advises checking sourcing for these RF parts before committing to a build. High-frequency PCB fabrication at 10.5 GHz demands controlled-impedance substrates and tight tolerances that consumer-grade PCB services may not reliably deliver.
Second, the build complexity. This is not a weekend project: Zendot's assessment is blunt, noting that reproducing the system involves high-frequency PCB fabrication plus FPGA and STM32 firmware work. The project doesn't yet include a structured assembly or installation guide. You're reading schematics, commit history, and issue trackers to figure out how things fit together.
Third, the expertise barrier. You need working knowledge of RF design, FPGA development, embedded systems programming, and radar signal processing. That's a rare combination even in professional engineering teams.
Use Cases: Where This Actually Helps
For the people who can clear those hurdles, the AERIS-10 opens up several practical applications.
University research. Labs studying beamforming algorithms, pulse compression techniques, or Doppler processing can now iterate on real hardware without six-figure equipment budgets. The modular design means students can modify individual subsystems without rebuilding the entire radar.
Drone detection and tracking. Small drone detection is a growing need for airports, critical infrastructure, and event security. Commercial counter-UAS radar is expensive and inflexible. An open platform lets developers tune detection parameters, integrate with existing sensor networks, and build custom alert pipelines.
Remote sensing and environmental monitoring. At 10.5 GHz, the AERIS-10 sits in X-band, useful for weather observation, soil moisture measurement, and vegetation mapping. Researchers who need ground-truth radar data for calibrating satellite observations could use this as a low-cost field instrument.
IoT integration. The Python GUI and open APIs mean developers can pipe radar data into existing IoT stacks. Imagine combining radar returns with camera feeds, lidar point clouds, or ADS-B transponder data for a fused situational awareness system. As we explored in our coverage of open-source AI voice tools, the pattern of open-source projects redistributing capabilities once locked behind expensive platforms is accelerating across multiple domains. Radar may be next, but it faces steeper integration challenges than software-only tools.
The Gap: What's Missing for Non-RF Experts
This is where the AERIS-10's promise collides with its current reality—the gap between a capable hardware design and the ecosystem needed to use it. The project is in alpha. The hardware design is detailed and thoughtful, with proper licensing under CERN Open Hardware Licence Version 2 for hardware and MIT for software. But the surrounding ecosystem barely exists.
No assembly guide. The documentation lives in a /docs folder and GitHub Pages, but there's no step-by-step build manual. For a system with dozens of high-frequency interconnects and precise mechanical tolerances, this is a significant gap.
Limited firmware tooling. The STM32 and FPGA firmware exists but isn't packaged for easy modification. Developers who want to change waveform parameters, adjust beam patterns, or add new processing modes need to understand the full signal chain.
No integration middleware. There's no MQTT bridge, no REST API wrapper, no containerized processing pipeline. IoT developers expect to pull data from sensors over standard protocols. Right now, you get a Python GUI and raw data. Everything between the radar and your application is your problem.
Calibration and validation. How do you know your build is working correctly? Commercial radars ship with calibration procedures and test targets. The AERIS-10 community hasn't yet developed equivalent resources.
What Comes Next
The AERIS-10 is the most complete open source hardware phased array radar project to appear publicly. Its hardware architecture is serious, its licensing is thoughtful, and its ambition is clear. But it's a platform for radar engineers, not yet a tool for the broader developer community.
The path from here is familiar from other open-source hardware projects: community-contributed build guides, pre-assembled module options, higher-level software abstractions, and integration examples with common IoT frameworks. The project's GitHub issues and pull requests are where that work will happen. If the community materializes, the AERIS-10 could become for radar what SDR dongles became for radio experimentation: a gateway that turns an expensive specialty into an accessible skill. The hardware design is already there. The software and documentation need to catch up.
