Separate by purpose
Media, audiobooks, documents, photos, downloads, 3D assets, and backups each have a clear share and ownership boundary.
Smart-Home-Edge-Systems.us / Storage hub
Make your data stay home.
A calm, dependable storage layer for the files your household actually depends on: films, family photos, documents, audiobooks, 3D assets, downloads, and the backups that keep every service recoverable.
One central gateway gives many services a clearer path from raw disks to the things your home uses every day, with private cloud access and media services built on the same organized foundation.
Independent field testing for the next generation of local-first storage infrastructure.
Hardware and software partners are invited to place real products in a transparent, community-facing evaluation environment.01 / What it does
The household data layer.
Local file sharing, private cloud access, and media streaming share one organized storage foundation. Services get the access they need without turning the home into a collection of disconnected disks.
SMBHousehold file sharing for computers and everyday access.
NFSEfficient mounts for Linux services, containers, and VMs.
CloudNextcloud for private document access and synchronization.
MediaPlex, Jellyfin, and Emby stream the same managed library.
Serve every service
Read-only media mounts protect the library while Nextcloud, Immich, Paperless-NGX, Deluge, and Manyfold use purpose-built paths.
Back up what matters
Hybrid backups collect Home Assistant exports, compose files, database dumps, proxy settings, and service configuration archives.
02 / The documented build
A gateway and a database backbone.
LXC 100 presents the shares. PostgreSQL runs separately on the isolated backend network, keeping application data and file storage understandable, portable, and easier to recover.
LXC 100 / Samba-NAS
- Compute / 2 vCPUs, 1 GB RAM, 16 GB NVMe OS
- Exports / SMB and NFS on the primary LAN
- Shares / media, audiobooks, documents, photos, downloads, 3D assets
- Backups / configs, database dumps, Docker stacks, and cold-sync status
Purpose-built shares
Database architecture: LXC 101 PostgreSQL uses 4 vCPUs, 4 GB RAM, 32 GB NVMe, and a bind mount at /var/lib/postgresql/data on the isolated 10.0.20.10 backend. LXC 109 PostgreSQL-FE provides the 2 vCPU, 512 MB frontend endpoint on the primary LAN.
03 / Installed application map
Every service has a job.
The compact inventory below captures the application layer around the storage gateway, including allocations, storage paths, the reason each service exists, and the benefit it adds to the household system.
PlexLXC 102 / 6 vCPU / 4 GBWhy: provides polished multi-device media playback. Benefit: QuickSync passthrough and read-only /media access deliver efficient streaming without risking the source library.
JellyfinLXC 103 / 6 vCPU / 4 GBWhy: provides an open-source media platform. Benefit: QuickSync passthrough and read-only /media access keep playback local, flexible, and separated from the master files.
EmbyLXC 104 / 4 vCPU / 2 GBWhy: gives the lab a second commercial media experience to compare. Benefit: the shared read-only /media mount makes service testing possible without duplicating the library.
AudiobookshelfLXC 105 / 2 vCPU / 1 GBWhy: manages spoken-word and audiobook collections. Benefit: a dedicated /audiobooks mount keeps metadata and listening access separate from film and television media.
NextcloudLXC 106 / 4 vCPU / 4 GBWhy: supplies private cloud file sharing and synchronization. Benefit: household documents remain accessible across devices while staying on the local storage foundation.
ImmichLXC 107 / 6 vCPU / 6 GBWhy: organizes and searches personal photos. Benefit: /photos provides a durable local library with enough dedicated memory for indexing and a responsive browsing experience.
Paperless-NGXLXC 108 / 2 vCPU / 2 GBWhy: turns scanned paperwork into searchable records. Benefit: separate consume and archive mounts protect the document workflow while keeping records on shared storage.
Deluge VPNLXC 110 / 2 vCPU / 1 GBWhy: manages downloads through a VPN-isolated service. Benefit: /downloads contains transient files and separates network-sensitive activity from the permanent media library.
LinuxGSMLXC 112 / 8 vCPU / 4 GBWhy: hosts and manages game servers. Benefit: dedicated compute and /game_backups preserve server state without competing with media playback workloads.
ManyfoldVM 113 / Docker / port 3232Why: catalogs printable 3D assets. Benefit: the mounted /mnt/shares/3d_assets library makes models searchable and reusable from one managed location.
HomeboxVM 113 / port 7745Why: records household equipment and possessions. Benefit: inventory data makes maintenance, replacement planning, and storage decisions easier to manage locally.
NetboxVM 113 / port 8000Why: documents networks, devices, and IP assignments. Benefit: an authoritative source reduces configuration drift and makes the storage architecture easier to troubleshoot.
GrocyVM 113 / port 9192Why: manages household stock and supplies. Benefit: local inventory tracking helps reduce waste and makes everyday planning independent of a cloud subscription.
MealieVM 113 / port 9925Why: organizes recipes and meal planning. Benefit: shared local data keeps household planning available even when external services are unavailable.
Pi-hole BackupVM 113 / ports 53, 80Why: preserves DNS filtering configuration. Benefit: Teleporter exports provide a recoverable local copy if the primary Pi-hole needs to be rebuilt.
Gravity-SyncVM 113 / DockerWhy: synchronizes DNS state with the compute Pi-hole. Benefit: configuration redundancy reduces recovery time and keeps filtering behavior consistent.
Uptime KumaVM 113 / port 3001Why: monitors service health and availability. Benefit: local alerts expose failures early, while exports stored on backups preserve monitoring configuration.
Watchtower #2VM 113 / DockerWhy: watches the web-stack containers for updates. Benefit: centralized container awareness simplifies maintenance while keeping update decisions visible.
04 / Build it carefully
Start with the storage guides.
Move from architecture to implementation with the documented Proxmox storage server design and installation workflow.