Helio is installed on the Windows PC that sends the stream; a technical beta also exists for Apple Silicon Macs. On the receiving side, the PWA needs no install. Apple apps use private TestFlight and Android uses a private Google test, by invitation only.
37 answers
Desktop Chrome is the best-covered path. The beta also includes Safari/PWA, iPhone, iPad, Apple TV, Android and Android TV, with each model validated separately. The compatibility matrix lists tested paths and their exact limits.
After installing Helio, a code links the PC to your account. You then find the machine in Nyx, select a display or create a virtual one, and start the session. No manual inbound port forwarding is required on the router.
Every configuration introduces different hardware and network cases. The 50 invitations are opened gradually so the team can follow feedback, fix regressions and avoid promising more support than a small team can deliver.
Request beta access. Once approved, the team invites you to private TestFlight for iPhone, iPad and Apple TV, or the private Google test for Android. None of these apps is freely listed in the stores yet.
Helio for Windows remains the primary and most complete path. Helio for macOS has a first proven H.264/HEVC path on Apple Silicon, with deliberate gaps compared with Windows. Compatible hardware encoding is recommended.
Yes from an Apple Silicon Mac with the Helio macOS technical beta, after granting screen-capture and accessibility permissions. It does not yet provide virtual displays, Windows launchers or virtual controllers. No Linux Helio is distributed.
They target the same journey — account, PC selection, video, audio, controls and diagnostics — but parity is not complete yet. The PWA is the functional reference; iOS and Android are catching up, tvOS is controller-first, and the Windows Store candidate still needs native input and fallback proof. The matrix lists every gap.
No. Lume is designed for both local and remote use. Away from home, quality depends more heavily on the host upload speed, the client network and whether a direct or relayed path can be established.
The PWA is the fastest way to test from a compatible browser. Native apps provide deeper platform integration — tvOS remote, orientation, audio, controllers and lifecycle — but each build is validated separately during the beta.
Yes on compatible paths, including Xbox-, PlayStation- and Switch-style controllers recognized by the client device. Button indexes vary by OS and some generic compatible controllers are still being validated: report the exact model when a button is missing or reversed.
Yes, a touch interface is planned for playing without a physical controller. Its ergonomics and parity across PWA, iOS and Android are still evolving; a physical controller remains recommended for demanding games during the beta.
Core controls are supported on compatible paths. System shortcuts, right click, wheel input and combinations reserved by the browser or OS may behave differently; full parity remains on the roadmap.
It creates a dedicated streaming workspace with a chosen resolution and refresh rate, without necessarily forcing those settings on the physical display. It is useful for gaming on a TV, working from a tablet or isolating a remote session.
Use Helio’s action to restore the previous desktop or stop the game display. Cleanup is still monitored during the beta: if a display remains, send a diagnostic before rebooting so the team can identify the creation path involved.
Lume is preparing shortcuts for major launchers and a living-room mode. Basic launching works on several paths, but bringing an app to the foreground on a virtual display — especially for some Windows apps — remains a beta validation point.
No inbound port forwarding is required. Helio and the client must still be allowed to establish outbound WebRTC/TURN connections; heavily filtered enterprise networks may block them.
Lume then tries the TURN relay. It helps behind many NAT and CGNAT setups, but cannot bypass a network that also blocks the required outbound protocols or ports. The HUD and diagnostics identify the active path.
Yes. Quality remains manually controlled through profiles and the Lab. H.264 is the baseline, HEVC depends on the encoder–decoder pair, and AV1 is limited to explicitly proven paths. 4K was validated on one Apple TV setup, not guaranteed everywhere.
It depends on the PC, client and network. One 16:04 direct session measured 128.4 fps median, but Lume does not yet publish glass-to-glass latency: internal RTT and decode times do not measure the entire physical chain.
144 fps was validated on one test configuration on August 12, 2026. This proves that path, not every device: the client display, GPU, decoder, codec and network must all keep up. The actually observed rate remains visible in session measurements.
There is no single number: demand varies with resolution, refresh rate, codec and content. A link around 1 Mbps requires very low quality; high definition and high frame rates need much more headroom and, above all, stable throughput. Lume favors cautious settings over a universal promise.
They can be more efficient at a similar bitrate, but only when the sender encodes and the client decodes them correctly, ideally in hardware. A newer codec is not automatically faster: Lume keeps H.264 as a fallback and reserves AV1 for explicitly compatible Lab paths.
End-to-end HDR is still a Lab project. Capability detection and instrumentation are progressing, but Lume does not yet promise a correct HDR chain across every TV, app and graphics card.
Wait a few seconds to see whether the session recovers, then check the HUD for direct or relayed path, bitrate, received frames and decoded frames. Temporarily lower quality and send a diagnostic with the time, device and action performed just before the freeze.
Check Lume’s mute button, the client media volume and the browser’s audio playback permission. Then restart the session. If it persists, send a diagnostic with the exact time: counters can distinguish sound missing on the PC from sound received but not played by the client.
The private beta is currently free both locally and remotely. Commercial relay pricing and any future plans will only be announced after measuring usage, actual cost and willingness to pay.
WebRTC media is encrypted in transit with DTLS-SRTP and APIs use TLS. Lume does not record or store video or audio sessions. Technical diagnostics are sent voluntarily and must never include passwords or live tokens.
Lume does not give the team a screen for freely opening your stream. Media travels in real time between endpoints or is relayed in encrypted form, and it is not recorded. Any support intervention must remain user-initiated and consented.
A diagnostic contains technical logs and counters used for troubleshooting: network, codecs, connection steps and errors. It is submitted voluntarily. It must not include video, audio, your password or a live access token; any exception must be treated as an incident.
Yes, devices and sessions must be revocable from the account. If you lose a phone or suspect unusual access, revoke the device, change your password and contact support.
Yes. Core paths are tested, but a beta spanning many GPUs, networks, TVs and controllers can still encounter regressions. The compatibility page separates validated, experimental and unverified paths.
The protocol, authentication and audio, video or controller fixes evolve together. An older build may still connect while missing an important fix. Always include both Helio and client versions when reporting an issue.
Lume Pro brings clients, physical PCs and VMs into one fleet workspace, then opens support from Nyx. The pilot foundation is deployed for a closed cohort: Pro gate, TOTP, fleet search and pagination. Sensitive capabilities remain separately enabled and fail closed.
That is one of the goals: inventory VMs and physical PCs by client, track availability and open an authorized intervention. Compatibility will still depend on capture support inside the VM, GPU acceleration and guest operating-system licenses.
The goal is fluid visual access and fleet management for smaller organizations, not an immediate claim of parity with every mature RMM feature. The pilot must first prove roles, consent, auditing, revocation and operational reliability.
The closed pilot has been open by invitation since August 20, 2026. No commercial date, price or SLA has been announced yet: reliability, security and field needs must first be proven with the first professionals.