How Just Jean Builds a Private Photo Cloud With ZimaBoard 2

Thanks to Just Jean for creating the original video. This article reorganizes the demonstration around one practical decision: what does it take to turn ZimaBoard 2 into a usable private photo cloud, and what responsibilities remain with the person operating it?

The practical verdict: ZimaBoard 2, ZimaOS, and Immich can form a compact self-hosted photo platform for uploading, browsing, organizing, and controlling a personal media library. The setup reduces dependence on a commercial photo service, but users remain responsible for storage health, backups, updates, security, and remote-access configuration.

Why Build a Private Alternative to Google Photos or iCloud?

Google Photos and iCloud simplify mobile uploads, search, synchronization, and sharing. The tradeoff is that storage limits, subscription changes, platform policies, and account availability remain outside the user’s direct control. A self-hosted photo system changes that relationship by storing the primary library on hardware the user manages.

This does not mean every cloud service should be abandoned immediately. The strongest reason to self-host is not simply avoiding a monthly payment. It is gaining greater control over where original files are stored, how much capacity can be added, which applications can access the library, and how long the archive remains available.

Immich is designed around a familiar photo-management experience, including mobile uploads, timeline browsing, albums, search, and other organizational functions. Its interface makes the transition easier for people who want local ownership without managing photos entirely through folders and filenames.

Assembling ZimaBoard 2 and Its Storage

At 03:58, Just Jean shows the ZimaBoard 2 hardware assembly and the board’s open PCIe expansion slot. The exposed design makes the system easier to adapt than a sealed consumer appliance because storage, networking, and compatible expansion hardware can be selected around the intended workload.

For a photo library, storage planning matters more than simply getting the operating system to boot. Phone images, RAW photography, edited exports, screenshots, and videos can expand the library quickly. Dedicated SATA storage allows the photo archive to grow beyond the board’s system storage and makes future drive replacement or capacity expansion more practical.

The open PCIe slot also leaves room for compatible expansion when the project changes. A user might prioritize additional storage connectivity, faster networking, or another specialized function. The exact card must still be checked for operating-system support, physical clearance, power requirements, and compatibility with the selected configuration.

Users preparing a similar build can review the available memory and hardware options on the ZimaBoard 2 Mini Home Server .

Starting ZimaOS and Configuring the Hard Drive

At 05:15, the video moves from hardware assembly to the first ZimaOS startup and storage configuration interface. This stage connects the physical drive to the applications that will use it. Before Immich can become a dependable photo library, the system needs to recognize the drive and make the selected storage location available.

A clean interface reduces setup friction, but the choices made here still have long-term consequences. Users should identify which drive holds application data, which location stores the photo library, and whether any existing files will be affected by formatting or initialization.

It is also useful to separate system responsibilities conceptually. The operating system runs ZimaOS and its applications, while the photo storage holds original uploads and generated media data. Keeping those roles clear makes troubleshooting, migration, backup, and future storage expansion easier.

Running Immich as a Self-Hosted Photo Library

At 06:35, Just Jean shows the Immich photo library running on the system. This is the point where the project moves beyond basic network storage. Instead of browsing a collection through folders alone, Immich presents photos through a visual timeline and application-style interface.

The interface is important because a photo archive must remain usable after the files have been uploaded. A large collection becomes difficult to navigate when the only organization method is a deep folder structure. A timeline, albums, thumbnails, search tools, and mobile access make the local library behave more like a complete photo service.

Immich should still be treated as a self-hosted application rather than an invisible appliance. Application updates, database data, thumbnails, user accounts, storage paths, and mobile synchronization settings all need to be maintained. Before a major update, users should verify that both the original media files and the application data can be recovered.

What Immich Can Replace—and What It Cannot

Immich can replace many everyday interactions associated with commercial photo platforms. Users can maintain a visual photo timeline, organize albums, upload media from personal devices, and access a centrally managed library without placing the primary collection entirely under a third-party storage account.

That does not create automatic feature parity with every Google Photos or iCloud function. Sharing behavior, mobile background restrictions, editing tools, account recovery, ecosystem integration, remote access, and search quality can differ. The practical comparison depends on which features a household actually uses.

A Private Photo Cloud Is Not Automatically a Backup

Moving photos from a phone to ZimaBoard 2 protects against losing only the phone, but it does not protect against every failure. If the server contains the only remaining copy, a damaged drive, accidental deletion, application error, theft, electrical event, or filesystem problem can still remove the entire library.

A dependable plan keeps more than one copy. The ZimaBoard 2 system can hold the working library, while another drive, NAS, computer, or encrypted off-site destination holds a separate backup. That second copy should not remain permanently exposed to the same failures or accidental changes as the primary library.

Drive redundancy can improve availability, but it is not the same as backup. Mirrored drives may keep the service online after one disk fails, yet deletions, corruption, or unwanted changes can still be reproduced across the mirror. Recovery requires an independent copy or versioned backup.

Planning Secure Remote Photo Access

Local network access is the simplest starting point. Phones and computers connected to the same home network can reach the server without exposing the application directly to the public internet. This allows the photo library and upload workflow to be tested before remote access is added.

Accessing Immich away from home requires another layer of planning. Users should avoid exposing an unmaintained application through an open router port without understanding authentication, encryption, updates, and network security. A private VPN or similarly controlled access method can reduce unnecessary public exposure.

Strong account credentials, current application versions, controlled user permissions, and a recovery plan remain necessary even when the server is located at home. Self-hosting increases control, but it also transfers security decisions from the cloud provider to the server owner.

Who Should Build This ZimaBoard 2 Photo Server?

This project is a strong fit for photographers, families, content creators, and home-lab users who want direct control over a growing photo and video library. It is especially useful when storage demand continues to increase or when several household members need one shared location for personal media.

It is less suitable for someone who wants a service that never requires updates, storage checks, backup verification, or troubleshooting. A commercial cloud platform may remain the easier choice when operational convenience matters more than hardware ownership and local control.

A hybrid approach can also be practical. Immich can serve as the main local library while a selected group of important photos remains in another backup destination. The decision does not have to be an immediate all-or-nothing migration.

Can ZimaBoard 2 Replace a Commercial Photo Cloud?

Just Jean’s demonstration shows the complete foundation: assemble the ZimaBoard 2 hardware, connect storage, start ZimaOS, configure the drive, and launch an Immich photo library. Together, those components create a compact platform for storing and browsing photos under the user’s control.

Whether it fully replaces Google Photos or iCloud depends on expectations. Users willing to manage storage, updates, backups, and secure access can gain more control and expandable local capacity. Users who prioritize completely managed operation may prefer to retain a commercial service or combine both approaches.

The greatest advantage is flexibility. The same ZimaBoard 2 can host Immich while also supporting selected storage, backup, media, or self-hosted applications, provided the workload and data-protection plan remain appropriate for the hardware.

Have another private-cloud or photo-management idea? Join the ZimaSpace Discord community to share your setup and follow more ZimaBoard 2 and Immich projects.