three bounded public-pilot recipes

Defined Homelab Workloads

Browse exactly three public-pilot workload recipes with versions, deployment methods, assumptions, and requirement axes.

record type
hub

record at a glance

public recipes
3
research-only or deferred
2
best attached evidence
grade B
accepted grade A runs
0

a workload is a falsifiable question

“Can it run Jellyfin?” is too vague. A useful recipe fixes the application release, deployment method, planning assumptions, required capability axes, and the performance claims that remain outside the evidence.

The pilot publishes exactly three recipes. Immich remains research-only and Frigate remains deferred; neither is expanded into search pages.

public-pilot recipes

7 explicit checks

Proxmox host with two light service VMs

Proxmox VE 9.x · Proxmox VE on bare metal

Prerequisite and planning-budget fit for a single-node host; not VM throughput, resilience, or storage-latency performance.

guest count
2
allocated guest memory gi b
8
redundant storage available
no
inspect recipe and evidence →

8 explicit checks

Home Assistant OS virtual machine

Home Assistant Core 2026.7.4 · Home Assistant OS in a KVM virtual machine

Prerequisite fit for the specified VM allocation; not an integration-count or recorder-performance benchmark.

vm vcpu
2
vm memory gi b
4
vm disk gi b
32
inspect recipe and evidence →

7 explicit checks

One concurrent 1080p Jellyfin hardware transcode

Jellyfin Server 10.11.x · Jellyfin Docker container in a Debian KVM virtual machine

Documented prerequisite fit only. Stream stability, quality, tone mapping, codec coverage, and concurrent throughput require Grade A lab results.

concurrent streams
1
source resolution
1080p
hardware acceleration configured
must be answered
inspect recipe and evidence →

how to use a recipe

  1. Read the decision scope and confirm it describes your actual goal.
  2. Resolve an exact mini PC profile instead of selecting only a model family.
  3. Answer every required assumption; a missing answer remains unknown.
  4. Inspect each capability axis and its attached evidence.
  5. Treat a prerequisite fit as separate from measured workload performance.

open the stack fit checker

receipts

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

record identity, publication and review

canonical path
/workloads/
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.

9 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

    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

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

5 further grade b records · official source

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

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

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

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

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

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.

  • 8 sources
  • 7 with a public link
  • 1 first party modeling policy
  • 5 official application documentation
  • 2 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 · 5 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
official release notes · 2 sources
  1. Home Assistant 2026.7 release notesOpen Home Foundation · official release notes · checked 2026-07-26
  2. Jellyfin 10.11.0 release notesJellyfin Project · 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 candidate 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