> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alpha-relay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectivity

> Local relay vs internet sync and queued uploads.

AlphaRelay uses **three separate paths**. Losing one does not always stop the mission.

```text theme={null}
Pilot app
  |-- LAN relay (Relay mission) → Mission Overwatch on same Wi‑Fi
  |-- Live stream (WebRTC) → Remote Overwatch over internet
  `-- Cloud sync → Events, footage, reports, evidence
```

## Without internet

* **Field-device mission** or **Relay mission** local work (relay needs Wi‑Fi, not internet)
* Event logging and LAN screenshots
* Queued footage and deferred sync
* Pilot license within the 10-day offline grace window

## Needs internet

* Sign-in and mission sync
* Footage and photo upload
* Playback links
* **Live stream (WebRTC)** setup and viewing
* Report generation and supervisor workflow
* Offline package and evidence JSON export downloads

## Relay mission connection

1. Pilot app running **Relay mission** on Wi‑Fi.
2. Open mission from Mission Dashboard.
3. **Live Overwatch Screen** → **Connect** (scan or enter pilot device IP).
4. Trust self-signed certificate on HTTPS if needed.

Mission Overwatch auto-fills the pilot IP from synced mission metadata when available.

## Queued states

**Queued for cloud sync**, **Loading playback link**, or upload banners mean local data still needs to reach the cloud. Stay signed in, keep the app open, move to internet, and use **Upload now** when offered.

<Warning>
  Internet ≠ local relay. Relay mission viewing needs same-network reachability, not cloud access.
</Warning>

## PWA / offline shell

Mission Overwatch caches its shell after an online visit. Cloud sign-in, sync, uploads, and playback still require network access.