OpenShack / Questions answered
Questions about OpenShack? Start here.
OpenShack brings together a complete remote-station system, serious CW training and dedicated CW hardware. This FAQ explains what each product does, how they work together and what your station actually needs.
Three products. Clear roles.
Choose a complete remote station, build CW skill, add dedicated keying hardware—or combine them.
What does OpenShack include?
OpenShack Remote connects you to your station through a Windows client or WebRemote in a supported browser, with operating and RX-only access paths. OpenShack CW develops receiving and sending from the first character through pileups, analysis and competition. The OpenShack Box is a standalone CW keyer and the dedicated hardware interface for paddle, keying and PTT in local and remote use.
What is OpenShack Remote?
OpenShack Remote is a complete remote-station platform. The Windows client combines receive and transmit audio, radio control, CW/PTT, logger interfaces, digital-mode connections, waterfall, cluster and supported station devices. WebRemote provides access from a supported desktop, smartphone or tablet browser. Hosts can keep the station private, share operating access or publish an RX-only path. Native Android and iOS apps are on the way.
What must my radio or existing station interface provide?
OpenShack Remote needs receive audio from the radio and transmit audio back to it. That bidirectional audio path can come directly from a radio with native USB audio or through your existing station interface. Radio control uses Hamlib with our custom extensions. If your radio provides two CAT COM ports, you can also use a second 1:1 CAT path. The host-side OpenShack Box connects CW and PTT at the station and makes those functions remotely accessible.
Do I need an OpenShack Box?
The OpenShack CW license works without a Box for keyboard-based training and the software tools. Paddle integration requires an OpenShack Box. Many OpenShack Remote functions also work without a Box. For properly integrated remote CW, we recommend a Box at the host: it connects the radio’s CW and PTT inputs to OpenShack and recreates the transmitted timing at the station. A second Box at the client is optional and provides the ultimate paddle experience.
What exactly does the Box do at the host?
It connects to the radio’s CW key and PTT inputs, receives the remote CW/PTT stream and recreates the intended keying timing locally at the station. The same Box also works as a standalone WinKey-compatible keyer when you operate locally.
What does a Box at the client add?
It puts the physical operating experience beside you: paddle input, immediate local sidetone and footswitch PTT. WinKey-compatible logger keying can work without a client Box, but a client Box is the preferred choice when the paddle and the feel of the keying matter.
One station. Two places.
The host stays with the radio hardware. The client puts the controls and local interfaces in front of you.
How are the host and client divided?
The Windows host stays at the station. It receives and sends radio audio through the radio’s native USB connection or an existing station interface, controls the radio through a supported path, and connects the host Box and supported station devices. The Windows client stays with the operator and provides the controls and local interfaces you need for operating.
Is this screen sharing or a remote Windows desktop?
No. OpenShack brings the station functions to the client PC. Your logger, digital-mode software, paddle, microphone and footswitch stay with you and connect locally.
What parts of the station can OpenShack control?
Depending on the station, OpenShack can combine audio, CAT/rigctld radio control, CW/PTT, virtual COM and audio paths, waterfall, DX cluster, rotators, amplifiers, tuners, antenna controllers and URL-controlled station switches.
Can an unattended station be completely powered down between sessions?
Yes. A networked smart plug can apply power to a host PC configured to start when mains power returns. After Windows signs in and OpenShack starts automatically, URL Switcher actions can switch on the rest of the station, a startup delay allows the equipment to boot, and rigctld can power on a supported radio. At the end, OpenShack can run the Off actions and shut Windows down safely. Only the independent smart-plug and network path needed to wake the station must remain available.
Which radios and station devices are currently supported?
We have several remote stations running OpenShack with the Icom IC-7760, Elecraft K3, Kenwood TS-890S and Icom IC-7300.
OpenShack uses Hamlib for radio control across a broad range of modern transceivers. Available control functions depend on the model. Other station integrations include:
- Amplifiers and tuners: SPE Expert 1K-FA, 1.3K-FA and 2K-FA; Elecraft KPA500, KAT500 and KPA1500; DU4000AL automatic antenna tuner; RF2K-S; Juma PA600 and PA1000; OM Power OM2000A+, OM1700A+, OM2501A, OM3501A, OM4001A and OM4001C.
- Antenna controllers: UltraBeam RCU-06 and SteppIR SDA 100 / SDA 2000.
- Rotators: up to four rotators through PSTROTATORAZ, covering the rotator models supported by that software.
- Waterfall sources: separate integrations for selected Icom, Kenwood and FlexRadio models.
- Other station equipment: generic URL-controlled relays, antenna switches, smart plugs and similar network devices.
Questions about your specific setup? Email support@openshack.com. If your equipment is not listed, include the exact model and the functions you need so we can check the available support.
What can an RX-only client do?
A host can publish the station for receive-only access. An RX-only client can hear the receiver and select frequency, mode, VFO and filter. The host ignores PTT, CW keying, level changes and station-device control from that session. The station owner retains control over access.
Can I share my station with other operators?
Yes. Keep your station private, give selected operators access, or publish it for RX-only clients. Receive-only clients can listen and tune without being granted transmit access. The host enforces the restriction: it ignores PTT and CW keying from these sessions.
Protected in transit. Safe at the radio.
Modern encrypted connections, private station access and local fail-safes protect both ends of the link and the equipment at the host.
How does OpenShack protect the connection between host and client?
Security is layered. OpenShack uses the modern, standards-based security built into WebRTC rather than a proprietary cipher. Connection setup is protected in transit with TLS. Live audio uses SRTP, while the real-time WebRTC data channels use DTLS encryption.
That protection remains in place on direct and relay paths: a relay forwards encrypted WebRTC packets rather than receiving plain audio or WebRTC data. The host accepts control messages only from the active session and rejects stale or mismatched session traffic. We maintain the host and client software, browser client, Box firmware and connection infrastructure as one system.
Why do the Station-ID and shared secret matter?
Both are required. The Station-ID—normally the host station’s callsign—identifies the station but is not a password. The shared secret is processed locally, is never sent in clear text and helps derive the station’s private connection channel.
Use the generated long, unique secret, give it only to trusted operators and replace it when access should change. Knowing a public callsign alone does not open the station.
Why is not needing port forwarding safer?
A traditional forwarded port leaves a fixed service reachable from the public Internet, where it can be found and probed by automated scans. OpenShack usually needs no such permanent router opening: host and client initiate outbound connections, a direct Peer-to-Peer path is established only after protected coordination, and a relay path is used when direct connectivity is unavailable. This reduces the host’s exposed attack surface.
It does not replace normal security hygiene: keep Windows, OpenShack and the router updated, leave the firewall enabled and protect the station secret.
What protects the transmitter and antennas if something goes wrong?
OpenShack uses several independent fail-safes:
- PTT watchdogs: the host application has a configurable PTT safety timeout—120 seconds by default. The OpenShack Box adds its own hardware PTT watchdog.
- CW watchdogs: the Box stops a continuously active paddle or an abnormally long remote key-down, releases the key and forces PTT off. Disconnect and session-teardown paths also request key-up and PTT-off.
- Host shutdown: if enabled, the unattended-host watchdog can shut the PC down after a chosen period without a client, running configured Off actions first.
- Rotor parking: rotators with a configured park bearing can be parked when shutdown begins or, if enabled, after their own no-client interval.
Shutdown and idle parking are opt-in. These safeguards substantially reduce risk, but no software can protect against every independent hardware fault.
Plug in. Connect. Get on the air.
OpenShack is a plug-and-play solution for virtually any Internet environment, not just an ideal home network. It finds the best available path over IPv4 or IPv6—even with CGNAT or DS-Lite—and keeps your CW timing intact once you are connected.
Do I have to configure my Internet router?
In most cases, no. Start the Host, sign in to OpenShack and let it establish the connection. OpenShack first tries to create a direct Peer-to-Peer path. That works surprisingly often without port forwarding or any special setting in the station router.
What if the Host is behind CGNAT, DS-Lite or an IPv6 connection?
Those are normal network environments for OpenShack. If a direct path is not available, OpenShack automatically uses our connection servers. It adapts again when the network changes, so you do not need one setup for your second home and another for a hotel, mobile connection or public Wi-Fi.
Why does OpenShack try Peer-to-Peer first?
A direct connection usually gives you the shortest path and the lowest latency. When it cannot be established, the server path keeps the station reachable. OpenShack chooses automatically—you do not need to work out which route the current network requires.
Why is remote CW difficult?
Network packets do not arrive at perfectly even intervals. Sending those arrival times directly to the transmitter makes CW sound uneven. OpenShack transports the intended key-down and key-up durations and recreates them at the station instead.
What happens when the network has jitter?
The station-side adaptive jitter buffer waits long enough to absorb normal variation, then replays the original timing. Jitter inside that buffer changes latency, not the length of your dits, dahs or element spaces.
What happens during an occasional large delay spike?
A late CW element can be accepted up to a total playout delay of about two seconds. The remaining reserve is approximately 2000 ms minus the active jitter buffer—about 1.5 seconds with a 500 ms buffer. The result is a short pause before CW continues, while the delayed element itself remains complete.
Can I send with both a paddle and a logger?
Yes. A paddle can use an operator-side Box with immediate sidetone, while a WinKey-compatible logger can send through the supported logger path. Both approaches preserve the original CW timing at the host.
What is Box-to-Box?
Put one OpenShack Box beside the operator and another beside the radio. After configuration, the two Boxes exchange CW timing and PTT on their own. No Windows PC remains in the keying path; your existing remote system can continue to carry audio and CAT.
What is Flex Keyer?
Flex Keyer lets you use a real paddle and footswitch through an OpenShack Box beside you while keying a reachable FlexRadio over the network. You keep immediate local sidetone and physical controls without requiring a second Box at the radio.
Why is local sidetone important?
A paddle operator must hear each element immediately. Waiting for audio to travel to the station and back makes natural sending difficult. The client-side Box generates sidetone locally while OpenShack transports the corresponding timing to the host.
More than a remote accessory.
The same hardware has a useful place locally, at the station and beside the remote operator.
What is the OpenShack Box?
It is dedicated CW hardware: a standalone keyer and WinKey-compatible logger interface that can also connect a paddle, CW keying and PTT to OpenShack. It can be used on the station side, beside the remote operator, in a two-Box link, or locally for training and everyday keying.
Does the Box replace my radio’s audio interface?
No. For OpenShack Remote, receive and transmit audio still travel through the radio’s native USB audio connection or an existing station interface. The host Box handles the OpenShack CW/PTT path: it makes those station functions remotely accessible and recreates CW timing at the radio.
Can the Box replace a WinKey?
Yes. The OpenShack Box works as a standalone CW keyer and WinKey-compatible replacement. Remote integration is an additional role, not the only reason to use it.
Does Box-to-Box require a computer while I operate?
No.* Chrome on Windows, Linux or macOS is used to configure both Boxes through USB serial. You set up Wi-Fi, select Box-to-Box mode and enter the shared session password in each Box. After setup, the Boxes can carry the CW/PTT path independently. Audio and radio control remain the responsibility of your chosen remote system.
* Standalone Box-to-Box requires a good Wi-Fi connection, with an access point close to each OpenShack Box. If a Windows PC is available at either end, connecting that Box to the PC by USB and using CW Link is preferable: the wired connection is generally more reliable and provides lower latency and jitter than Wi-Fi. Mixed arrangements are possible—for example, a Box through your phone's hotspot while travelling and a Windows PC connected to the radio at home.
Can the Box connect by USB and Wi-Fi?
Yes. USB/serial is the straightforward local starting point, and supported network roles can use the Box over Wi-Fi. The appropriate connection depends on whether the Box is acting as a local keyer, a host interface, a client interface or part of a Box-to-Box path.
Can I connect the Box to an Android phone or tablet by USB?
Yes. The native OpenShack Remote Android app supports the Box over USB on compatible smartphones and tablets, with a suitable USB data cable or adapter. That brings real paddle input and immediate Box sidetone to mobile remote operation. USB support is implemented; public native-app availability will be announced separately.
Does CW Link replace radio audio and CAT control?
No. CW Link is deliberately focused on CW timing, PTT and the control information needed for that path. Use it alongside an existing remote system, or choose the complete OpenShack Remote product when audio, CAT, logger interfaces and station devices should come together.
Learn, master and compete.
Remote operation is one part of OpenShack; serious CW development is another.
What is OpenShack CW?
OpenShack CW is the training side of the product family. It combines learning, listening, real sending, timing analysis, callsign and pileup practice, CW conversation and measurable challenges in one path for developing operators.
Is OpenShack CW only for beginners?
No. The learning path introduces characters and proper rhythm, while the full suite extends into callsigns, pileups, receiving quality, sending analysis, high-speed work, chat and measured competition disciplines.
What do Learn, Master and Compete mean?
Learn starts with full-speed characters introduced step by step using the Koch method. Master develops practical operating skill with words, callsigns, pileups, conversation, speed and clean keying. Compete shows your progress through personal bests and structured RX and TX challenges.
What is Quality RX?
Quality RX is a transcription exercise. OpenShack sends a random CW text at the selected speed; you copy it, then receive a similarity score and elapsed time. Newcomer mode supports practice, while Competition mode provides a defined measured challenge.
Does training include real sending?
Yes. OpenShack treats receiving and sending as parts of the same skill. Paddle input, timing analysis and transmit-oriented exercises help operators develop clean, repeatable CW instead of only recognizing characters.
Do I need a Box for OpenShack CW?
No. Many exercises use PC audio and keyboard input. A Box adds real paddle or straight-key input, hardware sidetone and direct keying data for sending exercises and analysis, so practice can include the physical technique you use on the air.
Can I practise actual CW conversation?
Yes. Morse Chat exchanges real CW timing with other operators in online rooms, and AI Morse Chat provides a practice partner when another operator is not available.
Can I start without buying the full suite?
Yes. The Web Morse Trainer provides a free entry point. The Windows suite adds the deeper training, analysis, competitions, chat and operating tools.
Practical questions.
What you should know before setting up OpenShack Remote.
Are native Android and iOS apps available yet?
The native Android and Apple iOS apps are on the way. WebRemote is already available in supported mobile browsers. USB Box support is implemented in the Android app for compatible smartphones and tablets; public native-app availability will be announced separately.
Which operating system does OpenShack Remote use?
The station host runs on Windows 11. The Windows client offers the full desktop workspace, including logger and digital-mode interfaces. WebRemote works in supported desktop, Android and iPhone/iPad browsers. Native Android and iOS apps are on the way. USB Box support already works in the Android app on compatible smartphones and tablets; USB Box access uses the native Android app.
How good must the internet connection be?
Stable latency and low packet loss matter more than headline bandwidth. Audio quality can be selected for the available path, and the CW jitter buffer protects timing from normal delay variation. No remote system can hide a sustained outage, so station connectivity still deserves care.
What is Remote Host Connect?
Remote Host Connect is the managed connectivity service for an OpenShack Remote host. The first year of Remote Host Connect is included with your Remote license; afterward the host station can renew for 12 months (€49) or one month (€4.90). The renewal fee helps cover the cost of running multiple servers in first-class data centers. Operators connecting as clients do not each need a separate Remote Host Connect subscription.
What about global server options?
As the user base grows, we will continuously expand our server footprint worldwide so OpenShack can use the closest available server. Our datacenter provider operates locations in Europe, the western and eastern United States, and Singapore — coverage designed to serve users around the world.
What about downtimes and uptime guarantees?
We do not currently offer a contractual uptime guarantee, but we will do our best to keep downtime to an absolute minimum. Occasionally, important security updates or infrastructure maintenance will be necessary. As more users come on board, we will add servers to provide redundancy.
Where do customers get setup instructions?
Detailed installation, configuration and troubleshooting documentation accompanies the product and its customer resources. This public FAQ deliberately explains capabilities and choices without publishing every station-specific setup screen.
Who develops OpenShack?
OpenShack is developed by Frank Grossmann, DL2CC—four-time WRTC competitor, WRTC bronze medallist, DXCC Honor Roll DXer and high-speed CW enthusiast. Work on the remote-CW solution began in the early 2000s and later included an Arduino-based remote system.
Still choosing your OpenShack path?
Tell us whether you want to build a remote station, improve your CW, add a Box—or combine all three. For a station setup, include your radio, audio interface and preferred CW workflow.