Thank you to u/Usual_Lock7115 for sharing a ZimaOS server built from a laptop motherboard and used every day to demonstrate applications and websites to clients. The project gives reused hardware a specific working role: keep prototypes running so another person can see and use them.
The original Reddit contribution includes a hardware photograph and screenshots of the system. Together, they connect the creator’s account of a useful NAS with a visible, rebuilt computer and a dashboard containing storage, database and web-access tools.
A Laptop Motherboard Gets a Different Working Life
The hardware is no longer arranged as a conventional laptop. In the photograph, the board and storage sit between clear panels, with the cooling fan and heat pipe still visible. Two compact hard drives occupy the other side of the assembly. This makes the reuse tangible: the computer’s core parts remain, while the screen-and-keyboard form has been replaced by a server-oriented layout.
The device-information screenshot identifies an Intel Core i5-6200U, two cores and four threads, and 8 GB of DDR4 memory. It also lists Intel HD Graphics 520. These are details visible in the creator’s image, rather than specifications inferred from the appearance of the motherboard.
| Part of the build | Evidence in the source |
|---|---|
| Reused laptop motherboard | Described by the creator and shown in the hardware photograph |
| Intel Core i5-6200U | Identified in the ZimaOS device-information screenshot |
| 8 GB DDR4 memory | Reported by the device-information panel |
| Clear-panel assembly | Visible mounting arrangement for the board and drives |
| ZimaOS | NAS and application environment used for the project |
| Client prototypes | Applications and websites the creator says are demonstrated daily |

The Server’s Main Job Is Showing Working Prototypes
The creator’s central use case is more specific than file storage. Clients can see application and website prototypes functioning in real time. That gives the machine a practical reason to stay available: it supports a conversation about something that can be opened and tried, rather than only described.
There is an important boundary to that account. The post establishes a demonstration workflow, but does not name the projects, their frameworks, the number of simultaneous visitors or a production availability commitment. It should be read as a personal deployment story, without turning it into an undocumented hosting-service benchmark.
The workflow also explains why a modest server can be useful without a very large app collection. A small number of tools that support repeated client demonstrations may matter more to the owner than adding unrelated services. The value comes from the recurring job the computer performs.
The Dashboard Shows Several Layers of the Setup
The app screenshot includes Nginx Proxy Manager, Cloudflared, MariaDB, Nextcloud and FileFlows, alongside ZimaOS features such as Files, Backup and ZVM. These icons show what the creator chose to place on the dashboard at that moment. They do not expose the configuration or reveal which application supports a particular client project.
In a follow-up, the creator explains that the screenshot was taken after changing drives, so it does not show everything previously configured. That makes the image a useful snapshot of the system’s state, rather than a definitive inventory of every service ever used on the machine.

For a related operating pattern, our ZimaBoard business-and-home server story follows an owner who also combines work applications with personal services. The comparison concerns the responsibilities assigned to the machine; the hardware and application arrangement are different.
Web Access and Application State Need Separate Attention
Cloudflared and Nginx Proxy Manager are visible in the screenshot, but the thread does not supply the public hostname, proxy rules or access policy. Their presence should not be turned into a claim that the creator uses a particular tunnel route for every prototype.
For readers exploring that part of the design, Cloudflare’s official Tunnel documentation explains the outbound connector model. It provides context for one visible tool, while leaving this owner’s actual routing and client permissions unspecified.
Application state is another concern when drives change. Docker’s volume documentation distinguishes persistent data from a container’s writable layer. In a comparable prototype server, the useful inventory would identify the project files, database data and configuration that must survive rebuilding an application. That is reader guidance, not a backup procedure documented by this contributor.
The Screenshots Describe a Moment, Not a Capacity Limit
The owner says the system feels responsive and uses few resources. The images show light CPU activity at the time they were captured, but they do not include a repeatable load test. A dashboard reading can describe a moment without establishing how many client sessions or background jobs the machine can support.

The screenshot also shows storage usage for the configured system. That value should not be treated as a verified total of every physical drive visible in the photograph: the thread does not map each device to a filesystem, pool or application location.
For someone considering a similar reuse project, the most relevant check would be the real demonstration task: open the prototype, exercise its main interaction and observe the host while that happens. This follows from the creator’s stated purpose and avoids using an idle-looking dashboard as a substitute for the actual workload.
A Clear Purpose Keeps Reuse Focused
The unusual enclosure is memorable, but the stronger part of the story is the connection between reused hardware and daily work. The contributor identifies a recurring need and shows the machine that serves it. A complete hardware shopping list or a claim of enterprise reliability is not required to understand why the project is useful.
Our first ZimaOS homelab on an HP ProDesk offers another example of assigning existing PC hardware a defined role. Readers comparing a reused assembly with an integrated storage system can consult the ZimaCube 2 product page as a separate reference; the contributor’s server here is the rebuilt laptop motherboard.
FAQ
What does the creator use this ZimaOS server for?
The creator says it is used daily to demonstrate working application and website prototypes to clients, in addition to its NAS role.
Which processor and memory are shown?
The device-information screenshot identifies an Intel Core i5-6200U and 8 GB of DDR4 memory. The motherboard is reused from a laptop.
Does the app screenshot show the complete deployment?
No. The creator says it was captured after changing drives and does not show everything previously configured.
Does the post provide a complete hosting tutorial?
No. It shares the working purpose, hardware and screenshots, without the project source, routing configuration, client-access policy or reproducible performance tests.
Conclusion
Usual_Lock7115’s project gives an older laptop motherboard a specific new purpose through ZimaOS: run prototypes that clients can experience directly. The original images show both the rebuilt hardware and its application environment. That combination makes this a useful reuse story grounded in an everyday workflow, with the deployment details left at the level the creator actually shared.
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.



