ApuSync and ApuClient
ApuClient is the Flutter client for sending content to an ApuOS NAS through ApuSync. The cloud service helps devices discover and pair; the file body travels through the verified client-to-NAS connection.
ApuSync, ApuConnect and browser transfer
| Service | Use case | Data path |
|---|---|---|
| ApuSync direct transfer | Send a file from a client to a NAS | Direct encrypted client-to-NAS transfer |
| ApuConnect remote access | Reach NAS pages from an outside network | Cloud TLS relay |
| Browser file transfer | Move a file between browsers on a LAN | NAS broker, separate from ApuClient |
The discovery service does not receive file names, file hashes, file contents or NAS passwords. STUN supplies network candidates but cannot guarantee direct connectivity through every router, firewall or NAT combination. ApuSync does not silently switch to ApuConnect or a cloud file relay when direct transfer fails.
Pairing flow
1. The NAS owner creates a short-lived pairing code and selects a writable destination. 2. The client verifies the NAS identity and sends its device identity. 3. The owner approves the client ID and public key on the NAS. 4. The client signs in with the NAS account over the verified connection. 5. The client uploads a file and verifies the complete size and SHA-256.
Pairing does not replace NAS accounts, ACLs or destination authorization. Do not enter an NAS password on an unfamiliar web page. ApuConnect uses a separate pairing flow and must not be mixed with ApuSync.