There is also a version which can run on distribution variants for Linux ARM devices, including Nvidia's Jetson Nano[21] and the Raspberry Pi.
[22] An app is available which allows users to connect from smartphones and tablets running Android or Apple's iOS/iPadOS operating system.
For the user connecting to the remote desktop, it is possible to view and stream audio and video content, including in the browser.
Simplest setup:[29] nxproxy alone achieves 1:10 to 1:1000 compression ratios,[30] reducing bandwidth, but does not eliminate most of X's synchronous round trips, responsible for most of X's perceived latency.
nxagent, derived from Xnest (similar to Xephyr), is typically started on the remote (client) machine, thus avoiding most X11 protocol round trips.
Typical setup:[29] On systems with a functional X11 implementation, nxproxy and nxagent are all that is needed to establish a connection with low-bandwidth requirements between a set of remote X clients and the local X server.
FreeNX and the various NX Clients are used for setup, handling suspend and resume, secure tunnelling over SSH, and printing and sound.
Prior to version 4.0, NoMachine released core NX technology under the GNU General Public License, and offered non-free commercial NX solutions,[31] free client and server products for Linux and Solaris, and free client software for Microsoft Windows, macOS and embedded systems.
In late 2005, Fabian Franz and George Wright began modifying kNX to use the nxc library, but abandoned the project.
[citation needed] It also drops dependency on Qt, which prevented nxclientlib from becoming widely used as a cross-platform basis for NX client programs.
Another obsolete (last updated Jan 2013) OSS NX client is OpenNX, described as a "drop-in replacement for NoMachine's [proprietary] nxclient" with full suspend and resume.
Remmina, another recent GTK+ remote desktop client project, announced the ability to use the NX protocol in its release 0.8.