Thank you to u/supremeoctopus for sharing a ZimaCube 2 that grew from a NAS into a personal application platform. Files, websites, a database and media services now sit behind a custom dashboard, giving one owner a place to manage both everyday applications and the machine beneath them.
The original Reddit post and the creator’s replies explain the important distinction: this is a minimal Debian installation with a locally accessible interface called cubeOS. The screenshot shows the creator’s own software, rather than an official ZimaOS release.
A NAS Became a Place to Run Personal Projects
A storage server becomes more useful when the files it holds connect to something people actually do. A media library needs playback software. A website needs a deployment process. An application may need a database as well as somewhere to keep uploaded files. Bringing those tasks onto one machine changes what its owner has to maintain.
Here, the interesting step is the management layer. The creator brought service controls and host administration into a shared workspace. That arrangement makes a personal server easier to understand at a glance: a stopped application, a storage warning and a pending maintenance task can be considered together.

The hardware is a ZimaCube 2 personal cloud NAS. This story follows the owner’s software choices; the screenshot does not establish which hardware edition they bought or provide a performance comparison between editions.
What the Dashboard Brings Together
The interface is useful to read as a map of responsibilities. Its panels group work that otherwise tends to become scattered across browser tabs, terminal sessions and separate applications.
| Area | Role in the creator’s setup | Question it helps the owner answer |
|---|---|---|
| Files | Sharing stored content | Where is the information I need? |
| Applications | Container management | Which services are running? |
| Web projects | Deployment through a CLI tool and GitHub app | Which project version is on the server? |
| Database | A self-hosted real-time database | Where does application state live? |
| Machine maintenance | Package and OS updates, reboot and shutdown | What will a host-level change interrupt? |
For another builder, the transferable idea is to organize administration around recurring decisions. A page that links to twenty applications can be convenient, but maintaining the host also means knowing which services depend on the same disk, network route or operating system.
Our small homelab story from u/jc-21 approaches that question through separate machines. This build puts more functions together. Both arrangements become clearer when each service has a defined job.
Debian Provides the Base for a Personal Interface
In a follow-up reply, the creator explains that they replaced the original installation with Debian and built a front end for desktop and mobile use on the local network. That choice puts responsibility for the interface and its assumptions with the person operating the server.
For a custom tool, this can be a productive constraint. It only has to present the workflows its author uses. There is less need to expose every storage option or support every possible machine. In return, a future change to the underlying system may require a corresponding change to the dashboard.
A practical distinction follows: an interface can make an operation easy to reach without making the operation independent of the host. Restarting a container affects an application. Restarting the machine affects all of its applications. A useful control surface should make that difference apparent before the owner clicks.
Pooling Files and Protecting Them Are Different Jobs
The creator also identifies mergerfs and SnapRAID as their storage tools. Understanding those names explains more than assuming that the illustrated disk bays represent a conventional RAID array.
The mergerfs documentation describes a filesystem pooling layer: multiple existing filesystems or directories can appear through one directory tree. It does not itself add parity, snapshots or RAID-style performance. A common path can simplify applications without changing the protection offered by the underlying disks.
The SnapRAID FAQ explains protection based on a synchronized state. Changes made after that state need separate consideration. Consequently, grouping disks and maintaining parity should be treated as distinct operations when planning recovery.
That distinction matters especially when a server combines a media collection with an active database. A library of relatively stable files and frequently changing application state have different recovery needs. The post does not provide a complete backup procedure, so it would be premature to treat the dashboard as evidence of one.
Deployment Convenience Still Needs Persistent Application Data
Automatic deployment makes it easier to move new code onto a server. Recovering an application involves another question: what has changed since that code started running? Uploaded content, database records and settings may all need to survive a replacement container.
The Docker volumes documentation explains how persistent storage can outlive the container using it. For readers building a similar workflow, a useful record pairs each application definition with the location of its persistent data. A running container list alone cannot provide that inventory.
This is a planning lesson drawn from the arrangement, rather than a claim that the creator lost data. Before automating more deployments, another owner could record:
- The application definition and configuration needed to recreate the service.
- The storage location of its database, uploads and other persistent state.
- A recovery method that can be used without the custom dashboard.
Our Proxbox backup-server story offers a different example of assigning recovery its own role as a homelab grows.
A Personal Tool Has a Different Finish Line
Asked about sharing the software, the creator said it was closely tied to their own installation. Supporting other storage arrangements would require more work. That reply is valuable context for anyone attracted by the screenshot: a polished interface can still be a personal project.
The story therefore offers a design example rather than a ready-to-install replacement operating system. Its strongest idea is making one person’s recurring tasks visible together. Other builders can borrow that approach while choosing tools that fit their own time, skills and recovery requirements.
FAQ
Is cubeOS the same product as ZimaOS?
No. Here, cubeOS is the creator’s custom interface. Their replies identify Debian as the underlying installation. Readers looking for the official platform can explore ZimaOS separately.
Can I download this dashboard and reproduce the build?
The discussion does not establish a generally available installer. The creator described the software as specific to their personal setup and said broader support would take additional work.
Does the screenshot prove storage performance or backup reliability?
No. It illustrates the interface. It is not a benchmark or a documented recovery test, and it should not be used to infer either.
Where can I read the creator’s explanations?
Use the original Reddit discussion linked above, including the replies about Debian, storage tools and the project’s availability.
Conclusion
This ZimaCube 2 project shows how a personal NAS can become a place to develop and operate applications. The creator’s contribution is the connection between those tasks: one interface presents the storage, running services and maintenance controls that matter to their daily use.
For another self-hoster, the useful starting point is to list the decisions made repeatedly, then decide which tools make them easier to understand. A custom dashboard can follow those needs as they grow, provided the application definitions and recovery information remain accessible outside it.
Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.
Zima Campaign Hub
More to Read

A ZimaBoard 2 Prototype with Two 22 TB Drives on the Test Bench
Explore sabitech2k’s early ZimaBoard 2 drive test, the reported power conditions, and the existing ZimaBoard used for Proxmox backups.

A Quiet ZimaCube and ZimaBoard Homelab with Debian and Docker
A ZimaCube and ZimaBoard split everyday applications from smart-home services, with Debian, Docker, Pi-hole and a Homepage dashboard.

A LEGO Rack for a First ZimaBoard 2 Home Server
See how a first-time builder organized a ZimaBoard 2 and two SSDs in a LEGO rack, with Home Assistant and home-office storage planned next.



