Camera to cloud storage mounts: Shade, Suite, LucidLink, and the local Relay pattern
How camera uploads reach Shade, Suite, LucidLink, JuiceMount, Mountain Duck, ExpanDrive, a NAS, or an external SSD through a safe desktop relay.
The short answer
The most portable integration is a one-way desktop Relay that writes verified camera assets into a user-selected folder. That folder can be an external SSD, NAS share, LucidLink filespace, ShadeFS drive, Suite volume, JuiceMount, Mountain Duck, or ExpanDrive mount. Add direct APIs selectively when they improve remote operation and delivery proof.1,5,6,7,8
A mounted folder reaches more creative storage than a wall of OAuth logos.
Creative filesystems already own caching, namespace, reconnect behavior, and collaboration. A desktop Relay can subscribe to one account-scoped delivery stream, write to a temporary local name, verify bytes, finalize atomically, and report a receipt.
This makes ordinary folders, SSDs, SMB/NAS shares, and many mounted cloud products immediately useful without teaching the camera or cloud service a new protocol.
| Destination | Initial path | Direct path later | Important constraint |
|---|---|---|---|
| Shade / ShadeFS | Relay to mount | Shade multipart uploader | BYO S3 uses Shade’s blob/chunk layout |
| Suite Studios | Relay to mount | Enterprise S3 Native surface | Confirm account eligibility and storage contract |
| LucidLink | Relay to filespace | Enterprise Connect through customer S3 | Connect links are currently read-only |
| JuiceMount | Relay to mount | Founder-related open-source deep integration | Beta, macOS-first, self-hosted |
| Mountain Duck / ExpanDrive | Relay to mount | Usually unnecessary | Remote durability differs from local write acceptance |
| MASV | API/Portal output | Direct connector | Package-oriented and each egress can be billable |
“Bring your own S3” does not always mean ordinary objects.
Shade and JuiceFS document their own block or chunk layouts in object storage, so a random object written into a backing bucket may not appear as a file in the mounted namespace. LucidLink Connect instead documents a separate, read-only way for eligible customers to link existing external object stores.2,9,5
Suite’s S3 Native product is materially different because its current product and pricing pages say standard objects remain readable and writable by other S3 tools and identify the feature with its Enterprise offering. Confirm account eligibility and the technical storage contract before implementation.3,4
Local acceptance and remote durability need separate receipts.
A desktop mount may acknowledge a write before its cache has reached the remote provider. The UI should show those states separately.
Received
The camera upload is complete and verified in the routing staging area.
Relay accepted
The desktop helper downloaded and verified the object locally.
Folder finalized
The helper closed and renamed the file into the selected destination.
Remote confirmed
The mount/provider reports remote durability when that evidence is available.
Frequently asked questions
Can a camera upload directly to LucidLink?+
A generic FTP camera does not natively speak the LucidLink filesystem. A local Relay can write to the mounted filespace. Enterprise customers can also evaluate an S3-plus-Connect pattern, with current read-only link constraints.5
Should Camera to Anywhere build a separate API for every mounted storage product?+
No. Certify the Relay against mounted folders first. Add a direct integration when it removes the always-on desktop, improves large-file behavior, or provides stronger remote delivery evidence.
Sources
Sources were last reviewed on . Vendor interfaces and documentation can change; follow the linked source and re-test the exact production workflow.
- 01
- 02
- 03Suite StudiosS3 Native File Streaming ↗
- 04Suite StudiosPricing ↗
- 05LucidLinkLucidLink Connect FAQ ↗
- 06CyberduckMountain Duck ↗
- 07ExpanDriveIntegrations ↗
- 08Leland DutcherJuiceMount open-source repository ↗
- 09JuiceFSArchitecture ↗