Hardware Compatibility:

You can mix and match hardware as needed in Ruby. You don't have to use a single SBC across the board. That is, you can use different SBC for vehicles and controllers and use different radio modules on the same link (assuming they do support the frequency you will be using).
For example you can pair a Raspberry controller to an OpenIPC AIO unit. Or you can pair a Radxa controller to a Raspberry vehicle. All functionalities still work the same across the board, in whatever way you mix and match your hardware components.
Due to the large diverse hardware ecosystem, there are some limitations on how you can mix and match hardware in Ruby.
Below are compatibility issues to be aware of:

SBC Compatibility:

• OpenIPC hardware can't be used as a controller/VRx. Only as air units (or relay air units);
• Radxa boards can be used as air units (as relay nodes or vehicles with telemetry only), but with no video stream, no cameras are supported on Radxa boards.

Radio Compatibility:

• Atheros, Sik Radios and ELRS radios can be used only on Raspbery platform. Support for Radxa, OpenIPC hardware will come in a future update;

Audio Compatibility:

• Audio works only on Raspbery SBC boards. Support for audio on OpenIPC air units will come in a future update;

Known limitations:

These limitations are either due to technical issues or complexity in software, and are as follows:

• Driver for radio cards that use the Atheros chipset is not included on OpenIPC Goke boards;
• Adaptive video and over the air update (OTA) is not enabled on OpenIPC Goke boards;