relay.Open Relay

A LITTLE CLOSER TO YOUR COMPUTER

Your computer.
Wherever
you are.

The work stays there.
The possibilities come with you.

Mac + iPhone · Private beta

Keep your computer.Change your point of view.↓

01 / THE IDEA

A window into
your own world.

Your apps. Your files. That task you left running.
Relay brings your computer within reach, without moving your work somewhere else.

01

See it. Take over.

View your Mac and request control from your iPhone or browser. Keep the work moving when you step away.

02

Bring the useful bits.

Explicit clipboard sharing and file transfers are part of the beta. You choose what crosses between devices.

03

Go beyond your Wi-Fi.

The current headless.host installation supports internet access. Your computer stays where it belongs.

02 / A SIMPLER WAY IN

Leave the desk.
Keep the connection.

The beta starts with your Mac.
The destination is any computer you call home.

  1. 1

    A home for your work.

    The Mac host runs in the background. Screen recording and input permissions keep you in control of access.

  2. 2

    A window in your pocket.

    Open the iPhone app or browser, sign in and pair with your Mac. Approve the connection on the Mac; existing gateway-password access remains available.

  3. 3

    Make yourself at home.

    View your desktop, take control, and move selected files. Reliable capture and smoother mobile controls are our next focus.

03 / ONE IDEA. MORE PLACES.

Headless.
Not out of reach.

Starting with Mac. Built toward a shared experience across computers and the devices you carry.

macOS

Host your workspace

Private beta

iPhone & iPad

Reach your Mac on the go

iOS private beta

Your browser

Open your existing gateway

Connect

Windows, Linux & Android

A broader Relay is on the roadmap

Planned

Private beta access is invitation-only. Public downloads are not available yet.

BUILT WITH BOUNDARIES

Access should feel easy.
Never casual.

The current internet gateway uses HTTPS and secure WebSockets through Cloudflare Tunnel. Remote viewing requires authentication, and input requires a control lease.

Apple and Google sign-in, trusted-device pairing, and personal subdomains are planned—not active features. Security depends on the whole connection, and we won’t promise what we haven’t verified.

A FEW GOOD QUESTIONS

Before you
head out.

Can I download Relay today?

Relay is in a private Mac and iOS beta. Existing testers can connect using their configured gateway. There is no public download or open registration yet.

Does my computer need to stay on?

Yes. The computer must be powered on, online, and running the Relay host. Mac sleep, lock-screen and unattended recovery are still being tested. Relay does not bypass your computer’s lock or security settings.

Will it work with Windows and Linux?

Windows and Linux hosts are planned, alongside Android. The goal is the same mobile and browser experience across platforms. They are not available in the current beta.

Can I choose my own headless.host address?

Personal subdomains are on the roadmap, together with account sign-in and device pairing. Subdomain registration is not currently available. A future address will identify a computer, not replace authentication.

Is this the final mobile experience?

No. The beta validates the connection and core controls. A more immersive viewer, better gestures, adaptive streaming and reliable recovery are active development priorities. The illustrations here show a design direction, not a performance demonstration.

A PROJECT BY LIVI LABS

A little less tied
to your desk.

Open your Relay

PERFORMANCE, WITHOUT THE GUESSWORK

Know what
you’re connecting to.

Mac first. Shared browser and mobile clients. Clear limits, measured results and a visible connection route.

Measured so far

Local synthetic video tests reached 29.5 fps at 1080p in native peers over six seconds and about 30 fps at 720p in Chrome over four seconds. A narrow generated-window capture test also decoded a real frame.

These are short local tests, not sustained desktop, physical iPhone or internet benchmarks. The installed private preview retains JPEG fallback; the new video path is still being verified.

Where frame rate is headed

60 fps is the next engineering target. Up to 120 fps is a later goal for capable devices and networks; 90 fps may be an optional mode.

60, 90 and 120 fps are not delivered guarantees. Capture cadence, encoder, decoder, content and display refresh all matter. A 60 Hz screen cannot present 120 distinct frames each second.

What your connection needs

The host’s upload, your device’s download, latency and packet loss all affect the experience. Hardware encoding and decoding support, screen resolution, battery and thermal limits matter too.

A validated hardware and bandwidth minimum has not been established yet. We’ll publish real-device profiles as they pass testing.

Direct first. Your choice after.

The new video connection will try direct access first. If a network prevents that, choose your own Cloudflare, Twilio, Metered or custom TURN relay and pay that provider yourself.

No automatic paid relay or shared relay bill. These provider integrations are planned, not currently enabled. The existing JPEG preview uses its gateway path.

A useful connection indicator

The video update is adding observed stream Mb/s, decoded frame rate, network round-trip time and the actual connection route. Text labels accompany the green, amber and red indicators; unavailable measurements stay neutral.

Stream Mb/s is the data being used by this session, not a speed test of your internet plan. Network round-trip time is not total screen-to-screen delay. Zero new frames on a static desktop is not automatically a bad connection.

Platform status

Mac hosts come first. iPhone and browser access are in private testing. A native Mac viewer preview exists; Windows and Linux hosts, followed by broader client coverage, remain planned.

The native Mac viewer currently uses password/JPEG access. Fresh-Mac host onboarding and a general installer are not ready. Browser and mobile clients share the protocol, while capture and input still need each host’s native adapter.

Private development preview · Evidence updated November 1, 2026 · No pricing or future-performance guarantee is published here.