Use Alluqi Bridge on mobile.
The Alluqi Bridge mobile app is the paired phone surface that securely continues an active desktop session. It gives you your desktop’s work on the move — it does not move the model.
What it is — and what it is not
The mobile app is one access surface. It works the same across cloud-only, private-only, and hybrid model strategies, and it does not choose where inference runs. Your deployment configuration decides that; the phone simply reaches the session.
Pairing and remote authority
A signed-in account is not the same as remote authority:
- Before two-factor enrollment, a mobile account is account-only — it cannot reach sessions or devices.
- Authenticator-app TOTP is required before pairing a PC or viewing sessions, files, responses, or controls.
- Recovery codes are a one-time fallback.
- Pairings, devices, and remote authorization are revocable.
Encryption in transit
Alluqi Bridge traffic is end-to-end encrypted between the mobile app and desktop app. The relay forwards opaque encrypted traffic between approved endpoints — it does not need the plaintext prompt, code, or response to route it, and it cannot read them.
This transport boundary does not hide cloud-model requests from a cloud provider you choose to use. Encryption protects relay transport; it does not make processing private from the provider receiving the request.
Platform and installation
The mobile app's platform and installation details are confirmed during onboarding. No public mobile-store release is promised.
Review the full security model