application release
Proxmox VE 9.x
>=9.0.0 <10.0.0
version record →candidate stack · combined allocation model
Home Automation and Media Starter Stack
A modeled Proxmox, Home Assistant OS, and Jellyfin starter stack with combined allocation, storage, passthrough, backup, and evidence conditions.
- record type
- stack
record at a glance
- default modeled snapshot
- Unknown
- combined checks
- 12
- deployment pattern
- primary pilot pattern
- best attached evidence
- grade B
- accepted grade A runs
- 0
stack topology and scope
Proxmox VE on bare metal, Home Assistant OS in a KVM VM, and Jellyfin in Docker inside a small Debian VM.
Combined prerequisite and allocation fit. It does not claim measured transcoding, VM latency, thermals, power, uptime, or backup integrity.
application release
Home Assistant Core 2026.7.4
>=2026.7.4 <2026.8.0
version record →application release
Jellyfin Server 10.11.x
>=10.11.0 <10.12.0
version record →- Proxmox VE on bare metal
- Home Assistant OS in a KVM virtual machine
- Jellyfin Docker container in a Debian KVM virtual machine
primary deployment architecture
Proxmox host with isolated appliance and application guests. The pilot's maintained topology for one exact mini PC: Proxmox VE on bare metal, Home Assistant OS in its own KVM virtual machine, and containerized applications inside a separate Debian KVM virtual machine. It is an architecture contract, not a performance or resilience result.
- virtualization host: Proxmox VE on bare metal. The exact mini PC runs Proxmox VE directly; no nested host hypervisor is modeled.
- Home Assistant appliance guest: Home Assistant OS in a KVM virtual machine. Home Assistant OS keeps its supported appliance environment inside a dedicated KVM virtual machine.
- container application guest: Jellyfin Docker container in a Debian KVM virtual machine. Jellyfin runs in Docker inside a separate Debian KVM virtual machine; device passthrough remains an explicit condition.
- system
- Host and guest system volumes may use the declared internal system SSD within the maintained allocation.
- bulk data
- Media and other bulk data require separately identified storage; the small system SSD is not treated as the library.
- recovery
- A separate backup target and a recoverable storage plan remain explicit operational conditions.
default assumptions
- decision context
- existing hardware
- secure boot disabled
- must be answered
- hardware acceleration configured
- must be answered
- external media storage available
- must be answered
- redundant or recoverable storage
- must be answered
- backup target configured
- must be answered
combined checks
- Hardware virtualization
- virtualization · required
- required
The selected stack needs hardware virtualization. - 4 hardware threads planning floor
- compute · required
- at least 4
The combined stack model needs at least 4 hardware threads. - 12 GiB combined minimum allocation
- memory · required
- at least 12
The combined host and guest allocation needs at least 12 GiB. - 16 GiB combined recommended allocation
- memory · recommended
- at least 16
Twelve GiB is a tight floor; 16 GiB leaves more operational headroom. - 256 GiB host and guest system storage
- storage · required
- at least 256
The stack model allocates at least 256 GiB to host, guests, app data, and cache. - Wired gigabit networking
- network · required
- at least 1
The stack assumes wired gigabit networking. - Intel Quick Sync media device
- media · required
- required
The selected Jellyfin recipe assumes an Intel media engine. - Home Assistant OS Secure Boot condition
- operational · required
- required
Confirm the Home Assistant OS Secure Boot condition. - Jellyfin hardware acceleration passed through
- media · required
- required
Configure and verify GPU device passthrough before relying on hardware transcoding. - External media storage
- storage · required
- required
The small system SSD is not the media library; specify NAS, DAS, or another storage plan. - Redundant or recoverable storage
- operational · recommended
- required
A one-drive mini PC is not a resilient storage system. - Separate backup target
- operational · recommended
- required
Add a separate backup target before treating the stack as operationally complete.
server-rendered modeled snapshot
The same evaluator used by the checker ran this stack against Lenovo ThinkCentre M720q Tiny — i5-8500T / 16 GB / 512 GB NVMe with the default assumptions shown above. Missing operational answers remain unknown.
default prerequisite-fit result
fit result: unknown. A required fact, input, effective source, or deferred test is missing.
unknown
A required fact, input, effective source, or deferred test is missing.
Combined prerequisite and allocation fit. It does not claim measured transcoding, VM latency, thermals, power, uptime, or backup integrity.
result confidence: evidence grade d · modeled or inferred · evaluated as of 2026-07-26
decision breakdown by axis
decision breakdown
- compute
- conditional
- The modeled processor meets the stack's planning floor. The positive match is supported only by a modeled, inferred, or user-attested Grade D value, so it remains Conditional and cannot establish a Yes verdict.
- evidence grade d · modeled or inferred
- memory
- conditional
- Installed memory meets the combined minimum allocation. The positive match is supported only by a modeled, inferred, or user-attested Grade D value, so it remains Conditional and cannot establish a Yes verdict.
- evidence grade d · modeled or inferred
- media
- unknown
- The modeled CPU exposes Intel Quick Sync. The positive match is supported only by a modeled, inferred, or user-attested Grade D value, so it remains Conditional and cannot establish a Yes verdict.
- evidence grade d · modeled or inferred
- storage
- unknown
- The system drive meets the modeled host and guest allocation. The positive match is supported only by a modeled, inferred, or user-attested Grade D value, so it remains Conditional and cannot establish a Yes verdict.
- evidence grade d · modeled or inferred
- network
- conditional
- The modeled interface meets the stack's network floor. The positive match is supported only by a modeled, inferred, or user-attested Grade D value, so it remains Conditional and cannot establish a Yes verdict.
- evidence grade d · modeled or inferred
- virtualization
- conditional
- The modeled CPU can host the VM-based deployment chain. The positive match is supported only by a modeled, inferred, or user-attested Grade D value, so it remains Conditional and cannot establish a Yes verdict.
- evidence grade d · modeled or inferred
- power thermals
- unknown
- not evaluated by this workload recipe.
- evidence grade unknown · insufficient evidence
- operational
- unknown
- Confirm the Home Assistant OS Secure Boot condition. The required input or capability is unknown.
- evidence grade d · modeled or inferred
physical selection constraints
- The 2.5-inch SATA drive and PCIe card cannot be installed together — Lenovo documents the M720 Tiny 2.5-inch HDD/SSD and PCIe card as mutually exclusive. Installing a PCIe riser/card consumes the space used by the 2.5-inch drive assembly. The modeled selections do not conflict, but Grade D configuration identity cannot prove the physical assembly clear. Resolution: Choose the internal 2.5-inch SATA drive or the PCIe riser/card. Keep NVMe as the internal storage path when PCIe expansion is required.
unknowns and contradictions (4)
- Confirm the Home Assistant OS Secure Boot condition. The required input or capability is unknown.
- Configure and verify GPU device passthrough before relying on hardware transcoding. The required input or capability is unknown.
- The small system SSD is not the media library; specify NAS, DAS, or another storage plan. The required input or capability is unknown.
- power thermals is not evaluated by this recipe.
what this result will not tell you
best-value upgrade
unavailable without current price evidence
The pilot has no fresh, comparable acquisition prices, so it will not label an upgrade as the best value.
why we believe this (7 evidence records)
a grade describes how well attested a statement is, not how good the hardware is. grade a is a lab run we reproduced with a published method. grade d is a model, a reasoned inference, or a single unverified report.
- evidence grade b 5 records
- evidence grade d 2 records
evidence grade b · official sourcesupports
For production, Proxmox VE documents Intel 64 or AMD64 with hardware virtualization, at least 2 GB for host services plus designated guest memory, fast redundant storage with SSDs preferred, and redundant multi-gigabit network interfaces. Its separate evaluation-only minimum is not a production recommendation.
evidence grade b · official sourcesupports
The i5-8500T has 6 cores, 6 threads, Intel 64, AVX2, UHD Graphics 630, Quick Sync Video, VT-x, VT-d, and EPT.
evidence grade b · official sourcesupports
The M720 Tiny family supports i5-8500T configurations, two DDR4-2666 SO-DIMM slots, an M.2 SSD, and an optional 2.5-inch SATA drive; Lenovo specifies that the 2.5-inch HDD/SSD and PCIe card are mutually exclusive.
2 further grade b records · official source
evidence grade b · official sourcesupports
Jellyfin recommends 8 GB RAM, SSD storage for application data and transcode cache, wired gigabit networking, and properly configured hardware acceleration for transcoding.
evidence grade b · official sourcesupports
The generic x86-64 Home Assistant OS image requires x86-64, UEFI boot, compatible storage, and a supported network adapter; Secure Boot must be disabled.
2 further grade d records · modeled or inferred
evidence grade d · modeled or inferredsupports
The five configuration records are explicit evaluation fixtures selected for feasibility work; they are not observed retail SKUs or tested lab specimens.
limitation: This is a modeled or inferred claim. It cannot establish measured performance.
evidence grade d · modeled or inferredsupports
Resource allocations in candidate recipes and the starter stack are planning budgets, not measured throughput or latency claims.
limitation: This is a modeled or inferred claim. It cannot establish measured performance.
receipts
9 sources · 0 accepted grade A runs · best evidence grade B · reviewed 2026-07-26
record identity, publication and review
- record id
- stack-home-automation-media-starter
- canonical path
- /stacks/home-automation-media-starter/
- publication
- candidate · noindex
- reviewed
- 2026-07-26
- review again by
- 2026-08-25
evidence boundary
Grade A count: 0. A Grade B source can establish a documented specification or requirement. Grade D records are modeling inputs. Neither is proof of measured throughput, thermals, power, reliability, or physical fit.
10 attached evidence records
a grade describes how well attested a statement is, not how good the hardware is. grade a is a lab run we reproduced with a published method. grade d is a model, a reasoned inference, or a single unverified report.
- evidence grade b 9 records
- evidence grade d 1 record
evidence grade b · official sourcesupports
For production, Proxmox VE documents Intel 64 or AMD64 with hardware virtualization, at least 2 GB for host services plus designated guest memory, fast redundant storage with SSDs preferred, and redundant multi-gigabit network interfaces. Its separate evaluation-only minimum is not a production recommendation.
evidence grade b · official sourcesupports
The generic x86-64 Home Assistant OS image requires x86-64, UEFI boot, compatible storage, and a supported network adapter; Secure Boot must be disabled.
evidence grade b · official sourcesupports
Jellyfin recommends 8 GB RAM, SSD storage for application data and transcode cache, wired gigabit networking, and properly configured hardware acceleration for transcoding.
6 further grade b records · official source
evidence grade b · official sourcesupports
Proxmox VE 9.0 is an official stable release line based on Debian 13, and its ISO is installable directly on bare metal.
evidence grade b · official sourcesupports
Home Assistant documents a KVM/Proxmox QCOW2 deployment with minimum VM resources of 2 GB RAM and 2 vCPUs, requires UEFI, and directs KVM users to a non-Secure-Boot OVMF image. The example KVM command allocates 4 GB, while the guide says resources should be sized to the expected workload rather than asserting a universal higher recommendation.
evidence grade b · official sourcesupports
The official July 2026 release notes list Home Assistant Core patch release 2026.7.4.
evidence grade b · official sourcesupports
Jellyfin publishes an official Debian-based container image and documents 10.11 tags, but does not establish the pilot's additional KVM guest layer.
evidence grade b · official sourcesupports
Jellyfin 10.11 is a documented stable server release line and requires a 64-bit operating system on ARM.
evidence grade b · official sourcesupports
Jellyfin says Intel 7th through 10th generation integrated graphics remain capable for existing owners, but are no longer recommended for a new purchase because Intel deprecated the relevant toolkit.
1 further grade d record · modeled or inferred
evidence grade d · modeled or inferredsupports
Resource allocations in candidate recipes and the starter stack are planning budgets, not measured throughput or latency claims.
limitation: This is a modeled or inferred claim. It cannot establish measured performance.
source ledger
Official facts and first-party modeling are shown separately. Source prose, tables, and diagrams are not republished.
- 9 sources
- 8 with a public link
- 1 first party modeling policy
- 5 official application documentation
- 3 official release notes
first party modeling policy · 1 source
- Super Evil Robots Repositioning Master Plan
official application documentation · 5 sources
official release notes · 3 sources
record and source history
This projection is generated from homelab graph version 0.1.0. The generated lifecycle index exposes only history events that are explicitly present in the structured record. It does not invent an earlier revision when the graph contains only its creation baseline.
- — current candidate record reviewed against the attached evidence set.
- — next required review under the monthly pilot-record review interval.
- — created: Initial bounded multi-application stack record created.
inspect the complete generated lifecycle and change-history index