Thank you to u/Relative_Sherbet for sharing a ZimaBoard that handles client workflows and everyday home services on the same machine. The build combines a separate Ubuntu business environment with a personal ZimaOS app collection, then adds an ESP32 signal intended to trigger a clean shutdown during a power outage.
The original Reddit post and the creator’s follow-up answers explain how that arrangement developed. The interesting part is the operating routine: where business data lives, which jobs run overnight, and how the owner hears about failures.
A Small Server with Two Different Responsibilities
Personal media can usually wait while a container restarts. A database supporting client work has a different relationship with downtime. Putting both on one host makes the physical setup compact, but it also makes maintenance a shared event. That is the central tension in this build.
The creator separates the business stack into an Ubuntu Server virtual machine through ZVM, allocating four cores and 12 GB of memory to that guest. The personal environment remains alongside it. This gives the business applications their own operating environment without turning the machine into two independent physical servers.
| Part of the setup | Reported role |
|---|---|
| ZimaBoard running ZimaOS | Shared host for personal services and the business VM |
| Ubuntu Server through ZVM | Separate environment for business applications |
| PostgreSQL, NocoDB and Metabase | Business data, management and reporting |
| Whatomate and n8n | Client communication and workflow automation |
| Emby, Immich and LightNVR | Media, photos and camera recording |
| UPS, ESP32 and a shutdown script | Power continuity and a reported outage notification mechanism |
| ntfy | Notifications about automated jobs |
The post describes more than fourteen containers across two environments. That is an inventory of this owner’s deployment, rather than a capacity recommendation for every ZimaBoard configuration. A container count alone does not reveal how much work each service performs.

The Business Stack Has a Clear Data Center
PostgreSQL is the main database, with NocoDB helping manage information and Metabase presenting it. Whatomate supports WhatsApp Business API communication, while n8n connects tasks. These applications form a working chain around business information rather than a collection chosen only to fill a dashboard.
That distinction helps explain why the owner groups them together. When several services depend on the same database, maintaining the environment as a unit can make its purpose easier to understand. It also means that a database problem may appear first as a broken report or a failed communication workflow.
For someone designing a similar deployment, a dependency list would be useful alongside the app list: which service stores the original record, which reads it, and which creates a new action. This is a planning lesson from the arrangement, not a configuration file supplied by the creator.

Remote Access Solves an Addressing Problem
The creator reports CGNAT and a dynamic address, and uses a separate Cloudflare account and tunnel for the business environment. Cloudflare Tunnel documentation describes its outbound connection model, which can connect an origin without requiring a publicly routable address on that machine.
A tunnel establishes a way to reach an application. The account permissions, application login and service maintenance still determine what a visitor can do after reaching it. The original discussion does not provide the access policy, so this story does not turn the tunnel into a claim that every exposed application has been audited.
Our small homelab story from u/jc-21 offers another useful view of assigning jobs to compact hardware. In both cases, identifying a service’s responsibility explains the build more clearly than counting machines.
Backup Priorities Follow the Importance of the Data
The business VM is backed up daily to an internal and an external drive, with selected important information also copied to Google Drive. For personal services, the creator concentrates on photos and videos. These are different priorities for different collections, rather than a claim that every application has the same recovery coverage.
A useful next question for any similar owner is what a restore actually needs. A copy of a VM and a copy of selected files may answer different recovery problems. The source does not describe a timed restore exercise, database consistency testing or how long each version is retained.
Immich illustrates why that detail matters. Its official backup guide separates database recovery from the photo and video files themselves. Someone reviewing this design should check both, rather than assume that preserving one automatically preserves the other.
The ESP32 Gives Power Loss an Explicit Signal
A UPS provides time after mains power disappears. The ESP32 adds a way for the owner’s setup to notice the event and invoke a shutdown script. The creator reports that the arrangement has been reliable so far, but does not publish the circuit, signaling protocol, battery runtime or shutdown test results.
Those missing implementation details matter if another builder wants to reproduce it. The useful idea is to connect an outage event with an orderly response; the post is not a wiring guide. A working copy would need its own verified detection behavior and enough battery time for the actual workload to stop.
The owner also shows a Google Home power control. Remote switching has a separate role from asking an operating system to shut down cleanly. Keeping those actions distinct is especially useful when a database and family photo services share the host.
Nightly Automation Makes the Routine Visible
Most automation is scheduled overnight, with ntfy reporting success or failure. The ntfy documentation explains how scripts can send notifications through HTTP requests. Here, the practical value is that a scheduled task can leave a result the owner will actually notice.
A failed job and a job that never started are different operational questions. Readers adapting the approach could record a last-success time as well as a failure message. That would be an extension of the idea; the creator does not document such a heartbeat system.

For related reading, the Pi-hole-to-family-server story follows another machine as its household responsibilities grow. Readers comparing present-day hardware can consult the ZimaBoard 2 product page; the Reddit text itself does not specify the creator’s exact hardware SKU.
FAQ
What makes the ZimaBoard part of a business workflow?
The Ubuntu VM hosts database, reporting, communication and automation services. Personal media and photo applications share the physical host through the surrounding ZimaOS setup.
Does the post provide a reproducible ESP32 shutdown guide?
No. It describes the purpose and the owner’s experience, but does not supply wiring, firmware, script contents or measured battery runtime.
Are all personal applications backed up equally?
The creator says personal backups focus on photos and videos. The business VM has a separate daily backup routine, with selected important data also copied off the machine.
Does the dashboard prove a particular performance level?
No. It shows one running setup. App counts and instantaneous readings do not establish simultaneous workload capacity or a general hardware benchmark.
Conclusion
Relative_Sherbet’s build shows what changes when a home server also carries business responsibilities. Separating the business environment, choosing backup priorities, reporting overnight results and planning an orderly power-loss response all become part of the machine’s everyday job. The original photos and follow-up answers make those decisions concrete without presenting an unfinished description as a universal deployment recipe.
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.



