BoatKit can find a UniFi OS console running Protect without credentials, add an enabled but incomplete integration, and tell the administrator that a local API key is still needed. After the key is entered, BoatKit inventories the cameras and existing streams without changing their configuration.
The administrator chooses which cameras join BoatKit. For each selection, BoatKit reuses existing low-, medium-, and high-quality RTSPS streams and asks Protect to create only the missing qualities. All available tiers feed BoatKit’s adaptive camera transport. BoatKit records stream ownership so removing the camera deletes only streams it created; a stream enabled by another Protect client is left alone.
Local security boundary
The API key remains a write-only secret on the BoatKit host. BoatKit records the console’s certificate before first sending the key, then requires that exact certificate for both the Protect API and encrypted RTSPS video. Stream URLs and their access tokens are not exposed through ordinary Viewer state.
Local discovery and viewing stay on the vessel LAN and can continue without internet access. Authorized remote camera access uses BoatKit’s separate BoatKit Cloud streaming path and depends on the vessel’s access policy and available bandwidth.
BoatKit does not yet publish a fixed Protect camera or firmware compatibility list. Initial validation includes a UniFi UNVR Instant with UVC G5 Turret Ultra and UVC G6 Pro 360 cameras; those examples are not a promise that every Protect combination is supported. BoatKit accepts H.264 and H.265/HEVC streams without transcoding. A 360-degree source opens as an interactive dewarped view, and every camera item remembers its own angle so one camera can cover several docking or watch views.
For discovery, API-key setup, stream consent, verification, backups, and troubleshooting, see the UniFi Protect setup guide.
UniFi and Ubiquiti are trademarks of Ubiquiti Inc. BoatKit and this integration are not affiliated with, certified by, or endorsed by Ubiquiti.