Questions, answered.
What RigPlane is, how the open-core and Pro pieces relate, which radios and platforms it supports today, how it handles digital modes and audio, and what is and is not open source. If the answer you need is not here, email [email protected] or check the technical docs at rigplane.dev.
About RigPlane
What is RigPlane?
RigPlane is software for operating IP- or USB-connected ham transceivers from a desktop computer. It speaks directly to the radio — no vendor app, no hamlib bridge, no third-party daemon in the loop — and presents one consistent operator console (dual-VFO, panadapter, waterfall, audio) for every supported backend. RigPlane is split into an open-core Python package and a paid native desktop app called RigPlane Pro.
What is the difference between RigPlane Core and RigPlane Pro?
RigPlane Core is the MIT-licensed Python library and browser-based Web UI, published on PyPI as the rigplane package. You install it with pip, manage Python, audio routing, and config files yourself, and run the Web UI in a browser. RigPlane Pro is the same radio-control engine packaged as a native desktop app for operators who would rather just install and operate, with audio bridged automatically, RC-28 controller integration, and a native CW console.
Which platforms does RigPlane support?
RigPlane Core runs anywhere Python runs — macOS, Windows, Linux, and Raspberry Pi — with the same Web UI on every platform. RigPlane Pro, the native desktop app, ships on macOS today; Windows and Linux are planned and tracked on the public roadmap. Pro beta is targeting Q3 2026.
Licensing & pricing
How much does RigPlane Pro cost?
RigPlane Pro is $79 USD at launch as a one-time desktop license purchase that includes one year of updates. After the update year ends, the desktop features you bought keep working — Pro is not a subscription. An optional update pass renews another year of updates for $49 USD. Full breakdown is on the pricing page at /pricing/.
Is RigPlane a subscription?
No. RigPlane Pro is a one-time desktop license purchase. The $79 launch price includes one year of updates, and after that year your purchased desktop features keep working without any further payment. The optional $49 update pass extends the update year — it is opt-in and not a subscription. See renewal details.
Do I need to pay if I only use the open-core PyPI package?
No. The rigplane PyPI package is MIT-licensed and free for any use — personal, club, or commercial. You can install it with pip install rigplane, read the source on GitHub, and run the browser-based Web UI on any platform where Python runs. RigPlane Pro is only required if you want the packaged desktop app, the bundled audio bridge, or hardware features like RC-28 controller integration.
Is RigPlane open source?
Partly. The core engine — radio control, transports, and the browser-based Web UI — is MIT-licensed and lives at github.com/rigplane/rigplane-core. The native desktop app (RigPlane Pro), the brand and icon set, and the paid distribution are not open source. This is a deliberate open-core split: the protocol and radio support are open, the packaged operator product is paid.
Radio compatibility
Which radios does RigPlane support today?
Production-grade backends with full CI coverage and real-hardware testing today: Icom IC-7610, Icom IC-7300, and Yaesu FTX-1. Community-validated: Icom IC-705. Profile-based backends with declarative capability profiles: Icom IC-9700, Xiegu X6100, and Lab599 TX-500. The authoritative per-radio status — including known limitations — lives in the rigplane.dev documentation. New radios land in rigplane-core as PRs.
Does RigPlane work with the Icom IC-7610 and IC-7300?
Yes. Both are production-grade backends — the daily-driver radios for development — with full feature coverage, CI tests, and real-hardware validation. The IC-7610 uses LAN (built-in Ethernet) and the IC-7300 uses USB CI-V; both are direct CAT, no RS-BA1 in the loop. Per-radio setup details are in the rigplane.dev documentation.
Does RigPlane support the Yaesu FTX-1?
Yes. The Yaesu FTX-1 is a production-grade backend over USB CAT, with 17 mode coverage, VHF/UHF, C4FM, and an audio FFT scope. It is one of the daily-driver radios used to develop RigPlane. Setup details are in the rigplane.dev documentation.
Setup & networking
Does RigPlane need cloud or an internet connection?
No. RigPlane talks to your radio directly over your local network or USB — there is no RigPlane cloud relay in the path, and no account login is required to control the radio. License validation for RigPlane Pro happens online, but the operating path is local. If your radio and computer are on the same LAN, no internet connection is needed to operate.
Do I need to configure port forwarding on my router?
No, not for normal local operation. RigPlane runs on the same LAN as the radio, so the rig and the computer just need to see each other on the local network. Port forwarding only becomes relevant if you want to reach your station from outside your home network, and that is a separate remote-operating setup rather than a default requirement.
Digital modes
Does RigPlane work with WSJT-X, JS8Call, fldigi, and other digital-mode software?
Yes. RigPlane speaks the rigctld wire protocol natively, so in WSJT-X, JS8Call, or fldigi you point the radio at "Hamlib NET rigctl" on localhost:4532 and it just works — no hamlib dependency on either side. Audio appears as a normal soundcard to your digital-mode software. The rigplane.dev documentation has per-mode setup guides.
Does RigPlane handle FT8 and FT4?
Yes, indirectly. RigPlane provides the CAT control and audio routing; FT8 and FT4 decoding happens in WSJT-X as usual. The setup is the same as for any WSJT-X integration: point WSJT-X at RigPlane over rigctld and route audio through RigPlane. Detailed FT8 setup notes for each supported radio are on rigplane.dev.
CW & audio
How does RigPlane handle audio routing on macOS and Linux?
On macOS, RigPlane Pro bundles BlackHole in the installer, so virtual audio is provisioned without a separate installer. On Linux, a PipeWire or PulseAudio sink is auto-provisioned. The audio path uses the Opus codec over UDP with tight buffers, tuned for headphone monitoring and CW. Windows audio packaging is on the roadmap; if you are on Windows today you can use RigPlane Core with manual audio routing.
Does RigPlane support CW with a paddle or external keyer?
RigPlane Pro ships a native CW console with a decoder. CW keying uses the radio's native CW interface; external paddle and keyer support depend on the specific radio and operator workflow rather than on RigPlane providing a USB keyer of its own. Per-radio CW notes are in the rigplane.dev documentation.
Trial, refunds, and support
Is there a trial or refund policy?
Yes to both. You can request a free trial of RigPlane Pro at /trial/ — the desktop app can create trial access directly with your RigPlane account email, and the public trial form records interest for support follow-up. Paid purchases of RigPlane Pro are processed by Paddle as merchant of record, and refunds follow Paddle's official refund policy; details are at /refund/.
Last reviewed 2026-05-19.