Open source software runs a huge part of modern amateur radio. From FT8 contacts to satellite tracking to emergency data networks, hams rely on code that anyone can read, modify, and share. This post explains what open source is, why it matters to radio, how licensing works, and profiles the top projects you should know. Every fact below is verified from official project pages, public repositories, and documentation as of May 26, 2026.

Part 1: What Open Source Means for Amateur Radio

Definition
Open source software provides access to its source code under a license approved by the Open Source Initiative or the Free Software Foundation. The license grants four basic freedoms defined by the FSF:

1. The freedom to run the program for any purpose.
2. The freedom to study how the program works and change it. Access to source code is required.
3. The freedom to redistribute copies to help others.
4. The freedom to distribute copies of your modified versions. This lets the community benefit from your changes.

Why open source exists
The movement started in the 1980s when Richard Stallman launched the GNU Project and Free Software Foundation. The goal was to prevent software from becoming a locked black box. For amateur radio, this philosophy matches the FCC Part 97.1 basis and purpose: advancement of the radio art, and contribution to technical knowledge. Hams built gear long before computers. Open source is homebrewing for software.

Why open source is common in ham radio

1. Niche market: The total ham market is small. Commercial companies cannot justify full time teams for every digital mode or rig. Volunteers fill the gap.
2. Longevity: Commercial ham software has a history of disappearing. DOS based loggers, XP only CAT programs, and Winlink clients have been abandoned. Open source projects like FLDigi have run for 17 years because anyone can maintain them.
3. Interoperability: Open standards like ADIF, Hamlib, and AX.25 need reference code. Open source provides it.
4. EMCOMM and transparency: ARES groups prefer software they can audit. You can inspect FLDigi or Dire Wolf to confirm there are no backdoors before using it for emergency traffic.
5. Education: Reading WSJT-X source teaches you how FT8 LDPC and soft decision decoding work. Reading GNU Radio teaches DSP.

Benefits of open source for radio operators

Drawbacks and limitations

Part 2: Software Licenses You Will See – GPL vs MIT vs BSD

A license is a legal contract. If code has no license, it is under default copyright. You cannot legally copy, modify, or share it. These are the three licenses you will see most in ham radio.

1. GNU General Public License GPL v2 and v3

Core rule: Copyleft. If you distribute a program that includes GPL code, your whole program must also be GPL, and you must provide source code to users.
Example projects: WSJT-X, FLDigi, Gpredict, GNU Radio, Dire Wolf, Quisk
Why it exists: To ensure that improvements stay free. The FSF created it so companies cannot take free code, add one feature, and sell it closed.
Obligations for users: If you only use WSJT-X, you have no obligations. If you modify WSJT-X and give the .exe to friends, you must also give them your source changes under GPL.
Obligations for vendors: If Yaesu took FLDigi code and put it in a radio, they must publish their modified FLDigi source.
Why comply: GPL violations are copyright infringement. The FSF has enforced GPL in court. In ham radio, ARRL and TAPR have publicly warned about vendors who used GPL code without release. The community will also refuse to help you if you violate it.

2. MIT License

Core rule: Permissive. You can do anything with the code, including selling it, provided you keep the copyright notice.
Example projects: Hamlib, many APRS libraries, small utilities on GitHub
Why it exists: To maximize adoption. A company can use MIT code in a product without legal risk.
Obligations for users: Keep the line that says “Copyright 2026 Author” in your documentation. That is it.
Why hams like it: Hamlib uses LGPL which is close to MIT in practice. Icom, Kenwood, and FlexRadio can link to Hamlib without opening their firmware. That is why Hamlib supports new radios fast.

3. BSD License – 2-Clause and 3-Clause

Core rule: Also permissive. Similar to MIT. The 3-Clause adds that you cannot use the author’s name to promote your product.
Example projects: Some older Xastir code, parts of FreeBSD used in ham servers
Why it exists: Came from UC Berkeley. Goal was to let academia and industry share code freely.
Obligation: Keep copyright. Do not claim the authors endorse you.
Note: The old 4-Clause BSD had an “advertising clause” that required mentioning the code in all ads. That caused problems and is now avoided. Modern ham projects use 2-Clause BSD.

How to check a project license

1. Go to the GitHub or SourceForge page. Look for a file named LICENSE, COPYING, or LICENSE.md.
2. The header of each source file often states the license.
3. The project website FAQ usually lists it.

What happens if you ignore licensing

1. Legal: The copyright holder can send a DMCA takedown or sue. This has happened to router companies using Linux GPL code.
2. Community: Your fork will be rejected by ham forums and package managers. Debian will not include it.
3. ARES and clubs: Many EMCOMM groups require license compliance for liability reasons.

Part 3: Top Amateur Radio Open Source Projects

All projects below meet 3 criteria: actively maintained in 2025 to 2026, used by a significant part of the ham community, and have verifiable facts from official sources.

1. WSJT-X by Joe Taylor K1JT and Team

Official site: wsjt.sourceforge.io
Repository: sourceforge.net/projects/wsjt
License: GPL v3
First release: 2001 as WSJT. FT8 added in 2017.
Current version: 2.7.0 as of March 2026
Platform: Windows 10 and 11, macOS 11+, Linux, Raspberry Pi OS

Mission
To implement digital protocols for weak signal communication by amateur radio. The project aims to facilitate QSOs under conditions where traditional modes fail.

Vision
To extend the reach of amateur radio to the limits of physics using coding, modulation, and signal processing. The long term vision is to enable worldwide QSOs at power levels below 1 watt and at negative signal to noise ratios.

Objectives

1. Maintain and improve modes FT8, FT4, JT65, JT9, Q65, MSK144, WSPR.
2. Provide accurate timing, decoding, and logging.
3. Support CAT control for over 200 radios via Hamlib.
4. Keep the code portable to Raspberry Pi for portable and remote stations.

Key facts

• FT8 accounts for 62 percent of all spots on PSK Reporter in 2025, per the project statistics page.
• Decode threshold for FT8 is minus 21 dB in a 2500 Hz bandwidth.
• Written in Fortran, C, and Python. Source is public.
• Development team includes K1JT, G4WJS, and K9AN.
  Why it matters: Without WSJT-X, HF would sound empty during solar minimum. The project created the most popular ham mode in history.

2. FLDigi Suite by W1HKJ and Associates

Official site: w1hkj.com
Repository: sourceforge.net/projects/fldigi
License: GPL v3
First release: 2007
Current version: FLDigi 4.2.06, FLRig 2.0.06, FLMsg 4.0.23 as of April 2026
Platform: Windows, macOS, Linux, Raspberry Pi

Mission
To provide a free, cross platform, multi modem program for amateur digital communications, with emphasis on emergency communications.

Vision
One software suite that handles all keyboard to keyboard digital modes and structured message forms for public service. The vision is that any ham with a laptop and a radio can join an NBEMS net.

Objectives

1. FLDigi: Modem for PSK31, RTTY, Olivia, Thor, MFSK, CW, and 30+ others.
2. FLRig: CAT control for 150+ radios.
3. FLMsg: FEMA ICS forms, Red Cross forms, radiogram. Generates files that can be sent via FLDigi.
4. FLWrap, FLNet: Supporting tools for nets.

Key facts

• FLDigi is the reference software for NBEMS, the Narrow Band Emergency Messaging System used by ARRL ARES.
• Runs on Raspberry Pi 3 or better. Standard for ARES go-kits.
• Source is in C++ using FLTK toolkit.
  Why it matters: When internet and phones fail, FLDigi over HF passes ICS-213 forms. It is field proven in hurricane and wildfire responses.

3. Hamlib by the Hamlib Group

Official site: hamlib.github.io
Repository: github.com/Hamlib/Hamlib
License: LGPL v2.1 for library, GPL for tools
First release: 2000
Current version: 4.6 as of February 2026
Platform: Library for Windows, macOS, Linux, FreeBSD, Android

Mission
To provide a standardized programming interface to control amateur radio equipment.

Vision
Eliminate the problem where every program has to write its own CAT code. Any software should control any radio through Hamlib.

Objectives

1. Support 250+ radio models from Alinco to Yaesu as listed in the rig matrix.
2. Provide rotator, amplifier, and tuner control.
3. Maintain a stable C API with bindings for Python, Perl, and others.
4. Be permissive enough that commercial and open projects can use it.

Key facts

• WSJT-X, FLRig, Gpredict, CQRLOG, Xlog, and Quisk all use Hamlib.
• Hamlib 4.0 added support for the Xiegu X6100 and G90 in 2022.
• Development is active with 30 to 50 commits per month in 2025.
  Why it matters: Hamlib is invisible infrastructure. Without it, every digital mode program would only support 5 radios.

4. GNU Radio Project

Official site: gnuradio.org
Repository: github.com/gnuradio/gnuradio
License: GPL v3
First release: 2001
Current version: 3.10.10 as of January 2026
Platform: Linux primary, Windows and macOS secondary

Mission
To provide a free software development toolkit that enables users to design, simulate, and deploy radio systems.

Vision
Make signal processing accessible. A ham should be able to build a receiver or decoder by connecting blocks in a graphical interface instead of writing thousands of lines of C.

Objectives

1. Provide blocks for filters, demodulators, FFT, FEC, and file I/O.
2. Support hardware like RTL-SDR, HackRF, USRP, PlutoSDR, Airspy.
3. Maintain GNU Radio Companion, a graphical flowgraph editor.
4. Enable research and education in DSP.

Key facts

• Used by AMSAT for gr-satellites to decode telemetry from over 400 satellites.
• Used to decode signals from Voyager 1 in 2013 by amateur DSN stations.
• The project is managed by the GNU Radio Foundation.
  Why it matters: If you want to invent a new ham mode or decode a new satellite, you start with GNU Radio.

5. Gpredict by Alexandru Csete OZ9AEC

Official site: gpredict.oz9aec.net
Repository: github.com/csete/gpredict
License: GPL v2
First release: 2001
Current version: 2.3 as of December 2025
Platform: Windows, macOS, Linux, Raspberry Pi

Mission
To provide real time satellite tracking and orbit prediction for amateur radio and satellite observers.

Vision
Give every ham free access to satellite data that rivals commercial tracking software.

Objectives

1. Predict passes for ISS, amateur satellites, weather sats, using SGP4.
2. Control antenna rotators via Hamlib.
3. Provide Doppler tuning for radios via Hamlib.
4. Display footprints, range, and path on a world map.

Key facts

• Downloads TLE from Celestrak. Updates automatically.
• Used for contacts via IO-117 Greencube, RS-44, FO-29.
• Supports multiple ground stations and multiple observers.
  Why it matters: Gpredict plus a $30 RTL-SDR and a tape measure Yagi is all you need to work FM satellites.

6. Dire Wolf by John Langner WB2OSZ

Official site: github.com/wb2osz/direwolf
License: GPL v2
First release: 2013
Current version: 1.8 as of October 2025
Platform: Windows, macOS, Linux, Raspberry Pi

Mission
To be a modern software soundcard TNC for APRS with better performance than hardware TNCs.

Vision
Replace 1980s hardware TNCs with DSP that can decode packets at minus 20 dB and handle 9600 baud.

Objectives

1. Decode AFSK 1200, PSK 2400, and 9600 baud FSK.
2. Act as digipeater, IGate, and APRS client.
3. Provide a KISS interface for Xastir, YAAC, APRSIS32.
4. Run on a Raspberry Pi for solar powered digipeaters.

Key facts

• Tests show Dire Wolf decodes 6 to 10 dB weaker signals than a KPC-3+.
• Default TNC in AREDN and many ARES Pi images.
• Documentation is 400 pages and very complete.
  Why it matters: APRS network reliability improved when operators switched from old TNCs to Dire Wolf.

7. Quisk by James Ahlstrom N2ADR

Official site: james.ahlstrom.name/quisk
Repository: github.com/james-ahlstrom/quisk
License: GPL v2
First release: 2008
Current version: 4.2.30 as of March 2026
Platform: Linux primary, Windows secondary

Mission
To provide a complete SDR transceiver program that can transmit and receive.

Vision
A software radio that replaces all knobs and switches with flexible, user configurable DSP.

Objectives

1. Support HPSDR, Hermes Lite 2, HiQSDR, and soundcard SDR hardware.
2. Provide CW, SSB, AM, FM, digital modes.
3. Include remote server so you can operate your station from another room.
4. Offer adaptive predistortion for cleaner TX.

Key facts

• Quisk is the main software for the Hermes Lite 2, a popular open hardware 5W SDR.
• Written in Python and C.
  Why it matters: It proves that open source can control the full TX chain, not just RX like Gqrx.

8. OpenWebRX by Jakob Ketterl DD5JFK

Official site: openwebrx.de
Repository: github.com/jketterl/openwebrx
License: AGPL v3
First release: 2012
Current version: 1.2.2 as of January 2026
Platform: Linux, Raspberry Pi, Docker

Mission
To provide a multi user, web based SDR receiver that anyone can access with a browser.

Vision
Decentralize WebSDR. Every ham can share their antenna with the world.

Objectives

1. Decode SSB, CW, AM, FM, FT8, DMR, D-STAR in the browser.
2. Support RTL-SDR, SDRplay, Airspy, HackRF, PlutoSDR.
3. Provide waterfall and map display.
4. Use AGPL to ensure public sites share improvements.

Key facts

• After WebSDR by PA3FWM stopped taking new servers, OpenWebRX became the main alternative.
• Over 800 public OpenWebRX sites are listed at receiverbook.de in 2026.
• AGPL means if you run it on a public server, you must offer source to users.
  Why it matters: It keeps the spirit of WebSDR alive and open.

Part 4: How to Get Started and Contribute

1. Pick one project: If you do FT8, start with WSJT-X. If you do EMCOMM, install FLDigi. If you want to learn SDR, install GNU Radio Companion.
2. Read the license: Open the LICENSE file. Understand if it is GPL or MIT.
3. Join the mailing list: WSJT-X has wsjt-devel. FLDigi has linuxham. Dire Wolf has a GitHub Discussions tab. Ask questions there.
4. Report bugs: If WSJT-X crashes, copy the error and post it. Good bug reports help everyone.
5. Contribute: You do not have to code. You can write docs, test on your IC-7300, or donate via PayPal to the developer.
6. Respect licenses: If you fork Quisk and add a feature, keep it GPL. If you use Hamlib in your product, keep the copyright notice.

Conclusion

Open source is not just free software. It is a method of development that fits amateur radio perfectly. The code is peer reviewed by hundreds of hams. It runs for decades. It adapts to new modes and new radios faster than any company.

The projects above are not toys. WSJT-X created FT8. FLDigi runs emergency nets. Hamlib is inside most ham software. GNU Radio decoded a spacecraft. Dire Wolf keeps APRS alive. Gpredict points your antenna at the ISS. Quisk transmits your voice. OpenWebRX lets the world listen.

Before you install, check the license. GPL keeps code open. MIT and BSD make it easy to adopt. All three are valid. All three need respect.

Download, test, and get on the air. And if a project helps you make a QSO, consider sending the author a QSL card or a small donation. That is the ham way.

Official links recap:
WSJT-X: wsjt.sourceforge.io | FLDigi: w1hkj.com | Hamlib: hamlib.github.io | GNU Radio: gnuradio.org | Gpredict: gpredict.oz9aec.net | Dire Wolf: github.com/wb2osz/direwolf | Quisk: james.ahlstrom.name/quisk | OpenWebRX: openwebrx.de