On your computer
UHFiX Server
Selects, captures and encodes your chosen source. Nothing begins silently.
Computer-to-TV screen sharing
Choose the source, approve the television, and see exactly where it goes. You don’t need luck when you have a plan. UHFiX is designed to keep the picture on your own connection while RUEZALS handles pairing and route approval.
The signal path
UHFiX separates control from media. The hosted Broker confirms identity, pairing, package capacity and route authorization. By design, your computer sends picture and sound directly to the television you approved. Phones join as Clients only: they bridge to the UHFiX Server over your local network and never act as the Server.
On your computer
Selects, captures and encodes your chosen source. Nothing begins silently.
RUEZALS control plane
Handles identity, entitlement, signaling and renewable session approval. It never carries the media.
On each television
Receives only the source assigned to that named TV and makes stopping obvious.
Pairing
Every UHFiX pairing starts with the RUEZALS circular code shown on the receiving screen — our house standard, and the only code type UHFiX uses. Scan the circle, compare the matching confirmation number on both screens, and approve on both ends. A code is an introduction, never permission by itself; it expires quickly and works once.
Phones are client-only. A phone pairs as a UHFiX Client and bridges to the UHFiX Server on your computer over the local network. It does not capture or host your screen.
Illustration only; not a scannable code.
Interactive routing board
This illustrative demo shows the core UHFiX decision: select a source, then choose the named television that should receive it.
1 · Choose a source
2 · Choose a television
Product demonstration only. It does not start screen capture or connect to a real television.
Built for deliberate sharing
Screen sharing should never feel mysterious. UHFiX keeps the important decisions visible and gives both ends a clean way out.
The computer still approves the exact Client and names it before any route begins.
Share a screen, window, presentation or supported source. No automatic microphone request.
UHFiX will not send an invitation or start another route when the package has no open capacity.
The Server or an authorized Client can end its route immediately.
Working beta packages
These package names, prices and capacities are launch hypotheses for a closed beta. Final store pricing will follow measured compatibility and support results.
One television. Automatic quality. A useful product without another monthly bill.
Send one source to several approved televisions and unlock higher quality where supported.
Route multiple named sources independently for busy homes, creators and presentations.
Up to ten Clients, multiple sources, display groups, volunteer roles and diagnostics.
$199 / year pilotAdministrators, display groups, multi-source routing, audit history and business support.
$299 / year pilotMultiple locations, larger Client fleets, organization policies and negotiated support.
CustomCompatibility without theater
The first release is a private Fire OS / Android prototype. Its build, signature and alignment checks are recorded. Physical Fire Stick picture, sound, remote behavior and off-site direct connections are still being verified.
APK build · signature · alignment
Physical Fire TV picture · sound · remote
Hosted circular-code pairing · routing board · packages
Direct encrypted media (to be verified before it is claimed)
Presenter: phone as mic and clicker · echo cancelled by timing
Protected services may block screen capture. UHFiX will not claim to bypass DRM or supply a movie catalog.
Straight answers
The planned Broker handles pairing, entitlement and route authorization. The design sends media directly from your computer to the television you approved, with no RUEZALS media relay. Transport encryption is part of the plan and will be stated as built only after it is verified.
That is part of the UHFiX plan. Higher packages support several named sources and Clients, while your computer's processor and upload capacity determine the practical limit.
Remote direct viewing is planned. Some networks block direct routes, so UHFiX will run a compatibility check and explain when NAT, a firewall, VPN or carrier network prevents the connection.
Planned, not built. The presenter plan lets a paired phone act as a microphone and slide clicker, with echo cancelled by timing alignment. Until it is tested, treat it as a roadmap item.
With the RUEZALS circular code only. The TV or phone shows the circle, you scan it, both screens show a matching number, and both sides approve. Phones stay Clients and connect to your computer over the local network.
No. Protected video services may intentionally block screen capture. UHFiX will explain likely protected-content limits and will not promise to defeat them.
Not yet. The receiver remains a private prototype. No Amazon app record, APK upload or certification submission has occurred.
Private beta
Big results start with one honest test. Help shape UHFiX through real Fire TV setup, direct-connection and repeat-use testing.
Request beta access