Back to Wave Wiki

Wave Harbor

From Wave Wiki — the open reference for the Wave OS ecosystem.

1. About

Harbor is the desktop companion agent for Wave OS. It runs as a native desktop application on Windows, macOS, and Linux, providing a bridge between your local machine and the Wave OS cloud. Harbor enables file synchronization, local compute offloading, E2E encrypted transfers, and 2FA-protected device pairing. It also serves as a local file server for the WaveBeam file transfer system. Built with Tauri v2 for minimal resource footprint.

2. Tech Stack

Framework: Tauri v2 (Rust + WebView). Desktop mode runs as a system tray application with a background service. Server mode runs as a Docker container on port 8443.

Security: end-to-end encryption plus 2FA authentication for device pairing. File Transfer: integrates with WaveBeam using RaptorQ fountain codes. Sync: bidirectional file sync between the local filesystem and Wave OS.

3. Install

Download the Harbor installer from the Wave OS desktop (Settings → Devices → Connect Harbor). Available for Windows (.msi), macOS (.dmg), and Linux (.AppImage). Server mode requires Docker and can be deployed via docker run -p 8443:8443 xbuildy/harbor-agent.

4. Pricing & Credits

The Harbor desktop application is free to use. Server mode is self-hosted at no additional cost. Remote file transfers via the Theta Edge relay use Wave OS credits, while local (LAN-only) transfers cost zero credits since they never touch the cloud relay.

5. Known Limitations

Desktop mode does not support headless/server deployment — use Server mode for that. 2FA is mandatory for device pairing, with no option to disable it. E2E encryption means Wave OS cannot recover files if encryption keys are lost. Sync conflicts require manual resolution — there is no automatic merge. Docker mode requires a minimum of 512MB RAM allocation.

6. Privacy & Data

File contents are E2E encrypted before upload — Wave OS servers cannot read file contents. Encryption keys are stored locally on the Harbor device and never transmitted. Device pairing uses a one-time pairing code with a 15-minute expiration. The HarborDevice entity stores device name, platform, and connection mode only — no file contents. Local file inventory is synced to the FileEntry entity as metadata only (name, size, path).

7. Published

Published: Yes, by xBuildy.