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 for you, RC-28 controller support (tested on macOS), and a native CW console.
Which platforms does RigPlane support?
RigPlane Core is Python and runs on macOS, Windows, and Linux with the same Web UI. RigPlane Pro is in open beta: macOS on Apple Silicon (M-series) only (macOS 26 or later), Windows x64 and ARM64, and Linux as a Flatpak for AMD64 and ARM64. The downloads page lists the current release. Beta signup is at /beta/.
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 needs no subscription. An optional $49 USD yearly pass pays for additional services and updates beyond the first year. Full breakdown is on the pricing page at /pricing/.
Is RigPlane a subscription?
No subscription is needed to use the app. 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. You do not need a subscription to use the app. 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?
Supported: Icom IC-7610, IC-7300, IC-705 and Yaesu FTX-1. The Icom IC-9700 has a rig profile and CI-V backend, and its satellite mode is not implemented. The Xiegu X6100 and Lab599 TX-500 have rig profiles only, with no control backend. See rigplane.dev for per-radio status and known limitations.
Does RigPlane work with the Icom IC-7610 and IC-7300?
Yes. 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 has a native backend over USB CAT, with 17 modes, VHF/UHF, C4FM, and an audio-derived spectrum scope. Sending free text CW from the Pro app is not supported on the FTX-1 yet. 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. RigPlane Pro does need a one-time sign-in with a Google account to activate its licence (every open-beta account gets access); the app will not start without it. After activation it works without an internet connection, and if your radio and computer are on the same LAN, no internet 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, with limits. 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 — no hamlib dependency on either side. Audio appears as a normal soundcard to your digital-mode software. WSJT-X is the tested path. In WSJT-X, "Fake It" split works everywhere; "Split: Rig" works on the IC-7300, IC-7300MK2, IC-705, IC-7610, IC-9700 and FTX-1. The rigplane.dev documentation has 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, Linux, and Windows?
On macOS, RigPlane Pro installs its own signed virtual audio driver, so virtual audio is provisioned without any separate download. On Linux, a PipeWire or PulseAudio sink is auto-provisioned. The radio delivers PCM (or μ-law, or USB audio on USB radios); over the network RigPlane sends audio as Opus with small buffers. If the app cannot find a radio's audio device, the connection center lets you choose the receive and transmit devices by hand. On Windows 11 version 22H2 or later, Pro installs, repairs, and removes the RigPlane virtual audio cable from inside the app.
Does RigPlane support CW with a paddle or external keyer?
RigPlane Pro has a CW console that sends text and decodes. Free text sending is not supported on the FTX-1 yet. RigPlane has no paddle input or USB keyer of its own; external paddle and keyer support depend on the specific radio. Per-radio CW notes are in the rigplane.dev documentation.
Trial, refunds, and support
Is there an open beta or refund policy?
Yes to both. Join the open beta at /beta/ or download the app at /downloads/ first; the app will ask you to sign in or join with your RigPlane account email. Paid purchases of RigPlane Pro, when checkout is available, are processed by Paddle as merchant of record. Refunds follow Paddle's official refund policy; details are at /refund/.
Last reviewed 2026-10-22.