THE HOMELAB

A place to ask
“what happens if?”

Compact infrastructure. Useful experiments. A way to learn how AI, data, and operations fit together.

01 / THE BIG PICTURE

One lab. Different kinds of compute.

A NAS for applications and AI, Proxmox for virtualized workloads, and a compact RK1 cluster for MongoDB experiments. The RAG stack also uses managed MongoDB cloud services.

HOMELAB / LOGICAL OVERVIEW Application and hardware roles

STORAGE & APPLICATIONS

NAS

HOSTED APPLICATIONS

OllamaModel servingHermesAI agent
Other hosted apps
RTX GPUAI compute acceleration

Storage meets application hosting and local AI compute.

VIRTUALIZATION

Proxmox

VIRTUAL MACHINES

VM
Docker workloadsApplication containers
VM
Docker workloadsExperiments & services

VMs provide separate environments for containerized workloads.

DATABASE EXPERIMENTS

RK1 cluster

MongoDBMongoDBMongoDB
Three data-bearing replica-set members
Control & monitoringAnsible · Prometheus · Grafana

A Turing Pi platform for repeatable builds and database measurements.

PUBLIC CLOUD / RAG DEPENDENCIESMongoDB Atlas & AI services

Atlas stores and searches the knowledge base. MongoDB’s AI Models API provides embeddings; managed reranking is an optional retrieval step.

Explore the RAG Gateway ↗
Conceptual roles only. The VM boxes illustrate workload groups; addresses, hostnames, network links, access paths, and detailed configurations are omitted.

02 / THE HYBRID AI LOOP

Local generation. Cloud-backed knowledge.

Hermes calls the RAG Gateway, which gathers evidence from managed MongoDB services and prepares the prompt for Ollama. The RTX GPU accelerates local model generation.

HOMELAB / AGENT, ORCHESTRATION & GENERATION
01 / AGENTHermes

Agent tasks & chat requests

Chat request
02 / ORCHESTRATIONRAG Gateway

Ingestion, retrieval & evidence assembly

Prompt + evidence
03 / GENERATIONOllama

Local model execution

Acceleration
04 / HARDWARERTX GPU

Compute for model inference

Ollama’s answer returns through the Gateway to Hermes, with source labels
RAG Gateway ↔ managed cloud servicesEmbedding requests · retrieval · optional reranking

PUBLIC CLOUD / MONGODB MANAGED SERVICES

EMBED

AI Models API

Embeddings for document passages and user questions.

STORE & RETRIEVE

MongoDB Atlas

Chunks, metadata & vectors. Vector search and optional hybrid search.

OPTIONAL / RERANK

Native reranking

Managed reranking of candidate passages before evidence assembly.

Retrieved evidence returns to the Gateway before the prompt is sent to Ollama. Atlas serves the RAG knowledge base; the RK1 cluster supports separate database experiments.

Generation runs locally, while document text and questions are sent for cloud embeddings. Chunks, metadata, and vectors reside in Atlas. When enabled, managed reranking also receives the query and candidate passage text. This is a logical data-flow view, with no private endpoints or network routes.

03 / THE RK1 DATABASE LAB

Three database members. A dedicated control node.

The public MongoDB project separates the replica set from the tools used to deploy, observe, and test it.

TURING PI / FOUR RK1 MODULES

MONGODB REPLICA SET

Data node APrimary*
Data node BSecondary*
Data node CSecondary*

*Illustrative roles. A replica-set election can change which member is primary.

Deployment · observation · load testing
FOURTH RK1Control & monitoring
AnsiblePrometheusGrafanaLoad tests
The control node is separate from the three MongoDB replica-set members. See the MongoDB project for the build and measurement stories.

04 / DOMOTICS & HOME AUTOMATION

A connected home. One control layer.

Home Assistant brings together home monitoring and control across Z-Wave, LoRa, Zigbee, and Wi-Fi. An MCP connection links this home automation layer to Hermes.

HOME AUTOMATION / LOGICAL VIEWObserve · automate · optimize
AI AGENTHermes

Agent interaction with home automation tools

Tool calls
TOOL INTERFACEMCP

Model Context Protocol connection

Tools & responses
HOME AUTOMATION HUBHome Assistant

Monitoring, automations & control

Device readings & states · automation and control actions

PROTOCOLS & INTEGRATIONS

Z-WaveLoRaZigbeeWi-Fi

Devices connect through the appropriate integrations and gateways.

Home systems & monitored conditions

Pool

Monitoring & control

Temperature

Measurements & trends

Air quality

Visibility into indoor conditions

Heating & cooling

Climate monitoring & control

Power monitoring

Understand energy consumption

Power optimization

Coordinate energy use to help control costs

COMFORT & ENERGY COSTS

Monitoring makes conditions and consumption visible. Automations coordinate home systems and optimize power use to help manage running costs.

A high-level capability map. Protocol blocks represent integrations, not network routes. Device identities, locations, endpoints, credentials, automation rules, and detailed operating schedules stay private.
01

Make it repeatable.

Turn setup steps into automation. Keep the configuration understandable and make rebuilding part of the learning process.

02

Measure the system.

Use observability and controlled experiments to distinguish a promising idea from a demonstrated result.

03

Keep asking questions.

Follow a build into the next experiment: from running MongoDB on ARM to understanding memory, and from a local model to grounded answers.

HOW THE IDEAS CONNECT

Infrastructure as
a learning tool.

The public projects explore three complementary layers. This map describes those themes, rather than a deployed network.

Sharing the learning.

This notebook publishes conceptual architecture, public project details, and selected results. Internal addresses, hostnames, access paths, private documents, and operational dashboards stay private.

Read the approach →