Self-Hosted Photo Backup Without Docker: Sync Photos Directly to Your NAS (2026)

Docker is a packaging method for server software. It does not make photos safer, and it is not required to own your library. A dockerless photo backup moves the work to the device: the phone reads its camera roll and uploads files directly to storage. There is no application server in the middle to host, patch, or back up, so the moving parts shrink to the two things you already maintain — your phone and your NAS.

That difference matters most on iOS, where the operating system decides when background work runs. A self-hosted platform that depends on a server still needs its app to stay alive long enough to finish uploading. Pho instead uses BGProcessingTask, the Apple API designed for long-running background work, and resumes the queue whenever the system grants time — so a large camera roll does not depend on you staring at the app.

No Server, No Database in the Photo Path

A Docker-based photo platform is really three systems stacked together: the application, a database that indexes every asset, and a container runtime that keeps them isolated. Each one needs updates, backups, and monitoring. Pho has none of them. The upload path is the app writing a file to storage, and the storage filesystem itself is the index — folders by date, thumbnails under .thumbnail/, and no metadata service to keep in sync.

First-Party Evidence: What Sits Between Phone and Disk

This page is published by the team that builds Pho, so here is the engineering detail instead of a marketing claim. Pho's control plane is a gRPC service and file transfers use HTTP — both implemented by an embedded Go engine that ships inside the app, compiled per platform. No server process exists at runtime. Photos and videos are written as YYYY/MM/DD/filename, Live Photos into a sibling folder whose name starts with live_, and thumbnails into a mirrored .thumbnail/ tree. Supported targets are SMB/CIFS, WebDAV, NFS, and Baidu Netdisk. Pho Pro adds client-side AES-256-GCM encryption: data is encrypted on the device before upload, the key never leaves the device, and it is off by default. Encrypted files carry an .aes suffix.

The Real Cost Is Maintenance After Year One

Docker makes the first install repeatable; it does not make year two free. Someone still applies image updates, reads release notes for schema migrations, watches disk space, and restores the database when a volume fails. A dockerless setup trades that ongoing work for a one-time connection: point the app at storage, and the only shared dependency is the storage itself. That is why removing Docker matters most to people whose hobby is photography, not server administration.

What You Give Up When You Skip the Stack

The server layer is not wasted complexity for everyone. Immich and PhotoPrism provide browser galleries, multi-user accounts, and server-side machine learning such as face recognition and automatic tagging; Nextcloud adds calendars, contacts, and documents. If those features are the point, run the stack. Pho is a backup-first mobile app: it puts photos on your storage reliably and shows them in a unified gallery, but it does not try to be a web content system or a shared family portal.

Encryption Without Trusting a Server

Server-side encryption protects the disk, not the operator — whoever runs the server can usually read the library. Pho Pro offers client-side AES-256-GCM: the app encrypts each file before upload and keeps the key on the device, so the storage target only ever sees ciphertext. Because the format supports random access, encrypted videos still stream with HTTP Range requests instead of forcing a full download. Traffic is protected in transit as well, over HTTPS, SMB3, or WebDAV-SSL depending on the protocol you choose.