version-scoped application and deployment ledger

Version-Scoped Homelab Applications

Browse the maintained application releases, supported deployment methods, bounded workload recipes, known issues, and the pilot's primary deployment pattern.

record type
hub

record at a glance

pilot application scopes
3
deferred application scopes
2
primary deployment patterns
1
best attached evidence
grade B
accepted grade A runs
0

an application name is not a compatibility claim

Each record fixes a release range, supported or discouraged deployment method, bounded workload recipe, and known-issue scope. A newer release, different runtime chain, or unmodeled workload needs a reviewed record; it does not inherit a positive result from the same product name.

This hub is intentionally non-index-candidate during the pilot. It helps people navigate maintained records without increasing the exceptional detail-page ceiling.

pilot application releases

>=9.0.0 <10.0.0 · 1 bounded recipe

Proxmox VE 9.x

supported deployment
Proxmox VE on bare metal
known issues in scope
0
  • Proxmox host with two light service VMs
inspect the version contract →

>=2026.7.4 <2026.8.0 · 1 bounded recipe

Home Assistant Core 2026.7.4

supported deployment
Home Assistant OS in a KVM virtual machine
known issues in scope
0
  • Home Assistant OS virtual machine
inspect the version contract →

>=10.11.0 <10.12.0 · 1 bounded recipe

Jellyfin Server 10.11.x

supported deployment
Jellyfin Docker container in a Debian KVM virtual machine
known issues in scope
1
  • One concurrent 1080p Jellyfin hardware transcode
inspect the version contract →

one 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.

  1. virtualization host: Proxmox VE on bare metal. The exact mini PC runs Proxmox VE directly; no nested host hypervisor is modeled.
  2. 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.
  3. 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 volumes
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.

inspect the combined starter-stack rules →

modeled but outside the public pilot

candidate · >=3.0.0 <4.0.0

Immich 3.x

This release stays in the private graph for rule and maintenance testing. It has no graduated application page and cannot expand the pilot by implication.

deferred · >=0.17.0 <0.18.0

Frigate 0.17.x

This release stays in the private graph for rule and maintenance testing. It has no graduated application page and cannot expand the pilot by implication.

receipts

14 sources · 0 accepted grade A runs · best evidence grade B · reviewed 2026-07-26

record identity, publication and review

canonical path
/apps/
publication
preview · 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.

18 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.

  1. 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.

    source: Proxmox VE Administration Guidechecked 2026-07-26claim: claim-proxmox-base-requirements

  2. 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.

    source: Proxmox Virtual Environment 9.0 release announcementchecked 2026-07-26claim: claim-proxmox-ve-9-release

  3. 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.

    source: Home Assistant OS generic x86-64 board supportchecked 2026-07-26claim: claim-haos-generic-x86-requirements

14 further grade b records · official source

  1. 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.

    source: Home Assistant OS virtual-machine installationchecked 2026-07-26claim: claim-haos-vm-requirements

  2. evidence grade b · official sourcesupports

    The official July 2026 release notes list Home Assistant Core patch release 2026.7.4.

    source: Home Assistant 2026.7 release noteschecked 2026-07-26claim: claim-haos-release-2026-7-4

  3. 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.

    source: Jellyfin hardware selection guidechecked 2026-07-26claim: claim-jellyfin-hardware-requirements

  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.

    source: Jellyfin container installationchecked 2026-07-26claim: claim-jellyfin-container-deployment

  5. evidence grade b · official sourcesupports

    Jellyfin 10.11 is a documented stable server release line and requires a 64-bit operating system on ARM.

    source: Jellyfin 10.11.0 release noteschecked 2026-07-26claim: claim-jellyfin-10-11-release

  6. evidence grade b · official sourcesupports

    Immich v3 requires a 64-bit Linux-like environment, at least 6 GB RAM and 2 CPU cores, Docker Compose, and x86-64-v2 for the amd64 machine-learning container; 8 GB and 4 cores are recommended.

    source: Immich installation requirementschecked 2026-07-26claim: claim-immich-v3-requirements

  7. evidence grade b · official sourcesupports

    Immich recommends keeping PostgreSQL data on a local SSD and estimates thumbnails and transcodes can add roughly 10–20 percent to library size.

    source: Immich installation requirementschecked 2026-07-26claim: claim-immich-storage-requirements

  8. evidence grade b · official sourcesupports

    Frigate recommends Docker on bare-metal Debian-like Linux for low-overhead access to GPU and detector devices and does not recommend a virtual machine as the default path.

    source: Frigate installation documentationchecked 2026-07-26claim: claim-frigate-installation-constraints

  9. evidence grade b · official sourcesupports

    Frigate is designed around a supported detector and documents several accelerator families; camera count depends on streams, codecs, models, activity, and detector throughput.

    source: Frigate recommended hardwarechecked 2026-07-26claim: claim-frigate-detector-guidance

  10. evidence grade b · official sourcesupports

    Frigate 0.17 adds and changes accelerator support, including Intel OpenVINO improvements and NPU support.

    source: Frigate 0.17 release noteschecked 2026-07-26claim: claim-frigate-0-17-release

  11. 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.

    source: Jellyfin hardware selection guidechecked 2026-07-26claim: claim-jellyfin-legacy-intel-guidance

  12. evidence grade b · official sourcesupports

    Immich does not recommend Docker inside LXC and recommends a supported full virtual machine when virtualization is required.

    source: Immich installation requirementschecked 2026-07-26claim: claim-immich-lxc-guidance

  13. evidence grade b · official sourcesupports

    Frigate recommends H.264 camera video for the broadest feature compatibility and notes that multi-stream cameras can avoid unnecessary re-encoding.

    source: Frigate recommended hardwarechecked 2026-07-26claim: claim-frigate-camera-codec-guidance

  14. evidence grade b · official sourcesupports

    Frigate highly recommends an integrated or discrete GPU for hardware-accelerated video decoding and documents Intel integrated graphics as a supported acceleration path.

    source: Frigate hardware-accelerated video decodingchecked 2026-07-26claim: claim-frigate-video-decoding-guidance

1 further grade d record · modeled or inferred

  1. evidence grade d · modeled or inferredsupports

    Resource allocations in candidate recipes and the starter stack are planning budgets, not measured throughput or latency claims.

    source: Super Evil Robots Repositioning Master Planchecked 2026-07-26claim: claim-ser-workload-budget-model

    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.

  • 14 sources
  • 13 with a public link
  • 1 first party modeling policy
  • 9 official application documentation
  • 4 official release notes
first party modeling policy · 1 source
  1. Super Evil Robots Repositioning Master PlanSuper Evil Robots · first party modeling policy · checked 2026-07-26 · docs/super-evil-robots-repositioning-plan.md
official application documentation · 9 sources
  1. Proxmox VE Administration GuideProxmox Server Solutions · official application documentation · checked 2026-07-26
  2. Home Assistant OS generic x86-64 board supportOpen Home Foundation · official application documentation · checked 2026-07-26
  3. Home Assistant OS virtual-machine installationOpen Home Foundation · official application documentation · checked 2026-07-26
  4. Jellyfin hardware selection guideJellyfin Project · official application documentation · checked 2026-07-26
  5. Jellyfin container installationJellyfin Project · official application documentation · checked 2026-07-26
  6. Immich installation requirementsImmich · official application documentation · checked 2026-07-26
  7. Frigate installation documentationFrigate · official application documentation · checked 2026-07-26
  8. Frigate recommended hardwareFrigate · official application documentation · checked 2026-07-26
  9. Frigate hardware-accelerated video decodingFrigate · official application documentation · checked 2026-07-26
official release notes · 4 sources
  1. Proxmox Virtual Environment 9.0 release announcementProxmox Server Solutions · official release notes · checked 2026-07-26
  2. Home Assistant 2026.7 release notesOpen Home Foundation · official release notes · checked 2026-07-26
  3. Jellyfin 10.11.0 release notesJellyfin Project · official release notes · checked 2026-07-26
  4. Frigate 0.17 release notesFrigate · official release notes · checked 2026-07-26

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.

  1. — current preview record reviewed against the attached evidence set.
  2. — next required review under the monthly pilot-record review interval.
  3. This route does not map to one simple lifecycle entity. Inspect the generated index for its component records; no route-level revision is implied.

inspect the complete generated lifecycle and change-history index