Browser app · host or viewer
Nothing to install. Open the secure production app in a current compatible browser, sign in through verified email, and enroll this browser as its own device.
Open production appOfficial release center
Download only what is ready and verifiable.
This page is the canonical installation entry point for RealLexi Connect. A platform receives a download button only after its package, publisher signature, checksum, software bill of materials, and supported-device checks pass.
Available now
Choose the software for each device role.
The production browser app is ready now. Windows, Android, Chrome/Edge, and VS Code development packages are installable for transparent testing, but remain unsigned or development-signed and are not production/store releases.
Windows companion · unsigned development package
Installable for development testing on a Windows device you administer. The package includes the native host, current-user installer/uninstaller, and unpacked browser extension. Installation requires the explicit -AllowUnsignedDevelopment opt-in and accepts only an Authenticode NotSigned executable.
Android client · debug APK
Installable development APK signed with the standard Android SDK debug certificate. Unit tests, release/debug lint, package identity, permission bounds, and APK signature checks passed; physical MediaProjection and notification acceptance still require a real authorized device.
Chrome/Edge and VS Code extensions
Development packages include incoming-session notifications and trusted handoff to the Sessions screen. Extract and Load unpacked in Chrome/Edge developer mode, or install the VSIX through VS Code's normal extension installer.
Apple clients · macOS / iPhone / iPad
Not offered yet. Apple packages must be signed and notarized on the release Mac with the approved Developer identity.
Linux companion · package
Not offered yet. There is no reviewed native Linux client package or approved Sigstore release identity in this release.
Set up in order
From a clean device to a visible session.
Use the production browser path for normal sessions. Install development packages only on devices you administer, keep every platform warning visible, and follow the included unsigned-development opt-in instructions.
- 01
Open
Use the production link from this page on the host and viewer.
- 02
Sign in
Use the short-lived link sent to your verified email address.
- 03
Enroll
Give each browser a recognizable device name; each keeps its own private key.
- 04
Request
The viewer requests the exact enrolled host and the host reviews the named participant.
- 05
Approve
The host chooses the exact screen and grants only the permissions needed.
- 06
Stop visibly
Capture and any approved control stay visible and can be ended locally.
Safe updates
Every native update follows the same evidence chain.
Native applications will update only through a versioned, signed release. A missing or invalid gate keeps the package unpublished.
- Versioned build
- Publisher signature
- Checksum + SBOM
- Acceptance checks
- Staged release
- Visible update
Verify before installing
Development packages are not production signatures.
Windows is Authenticode NotSigned, Android uses the SDK debug certificate, Chrome/Edge uses developer mode, and the VSIX is not Marketplace signed. Exact checksums and metadata are published, but these packages remain development previews and must not be represented as signed production/store releases.