Network

Always-on personal infrastructure. Overlook runs the cluster, agents, and all pipelines. Derry holds 64 TB of archive. Everything connected via encrypted WireGuard mesh.

Cluster

Orchestration: Talos Linux v1.12.4 on Colima (VZ framework)
Memory: 64 GB unified
CPU: Apple M4 Pro · 14 cores
GPU: 20-core Apple GPU
Storage: 64 TB NAS + 1 TB local NVMe
Functions: 48 Inngest durable functions
Interconnect: Tailscale WireGuard mesh

Nodes

Overlook

overlook

Online

Control plane. Runs everything — k8s cluster, agent gateway, event bus, all pipelines. Always on, always watching.

Mac Mini · Apple M4 Pro · 14-core CPU · 20-core GPU · 64 GB unified · 1 TB NVMe

●Talos k8s cluster (Colima + Talos)
●Inngest event bus (k8s StatefulSet)
●Redis state/pub-sub (k8s StatefulSet)
●Qdrant vector search (k8s StatefulSet)
●Bluesky PDS — AT Protocol personal data server (Helm)
●LiveKit — WebRTC media server (Helm)
●System-bus worker (launchd, 48 functions)
●Gateway daemon (launchd, pi agent + Telegram bridge)
●Caddy HTTPS proxy (launchd, Tailscale TLS)
●Vault sync (launchd, git auto-commit + push)

Derry

derry

Online

Archive. Video library, book collection, media backups, pipeline output landing zone. Everything's buried down here.

NAS · Intel Atom · 8 GB RAM · 64 TB RAID

●SSH file access (video ingest target)
●Video archive by year (yt-dlp pipeline output)
●Screenshot storage (pipeline-extracted key moments)

Flagg

flagg

Online

Primary development machine. Goes everywhere, exit node for the tailnet.

MacBook Pro · Apple Silicon · macOS

Blaine

blaine

Online

Remote Linux node. Available on tailnet. Asks a lot of riddles.

Linux server

Todash

todash

Idle

Network edge. Tailscale exit node, currently idle. The darkness between worlds.

Linux router

K8s Pods joelclaw namespace

Pod	Role
inngest-0	Event orchestration server
redis-0	State, pub/sub, loop PRD, cooldowns
qdrant-0	Vector search (memory observations)
bluesky-pds	AT Protocol personal data server (Helm)
livekit-server	WebRTC media server (Helm)

Daemons launchd

Service	Purpose
system-bus-worker	Inngest function worker (48 functions)
gateway	Pi agent gateway daemon + Telegram bridge
gateway-tripwire	Gateway watchdog
caddy	HTTPS reverse proxy with Tailscale certs
colima	Container runtime (VZ framework → Talos k8s)
vault-log-sync	system-log.jsonl → Obsidian markdown notes
content-sync-watcher	Vault content → web deploy trigger
system-bus-sync	Monorepo → worker clone sync

Stack

Layer 5: Agents       — Pi gateway, coding loops, background workers
Layer 4: Orchestration — Talos k8s cluster, launchd daemons, Helm releases
Layer 3: Services      — Inngest, Redis, Qdrant, PDS, LiveKit (k8s pods)
Layer 2: Pipelines     — Video ingest, transcription, screenshots, content enrichment
Layer 1: Memory        — Observations, proposals, MEMORY.md, session transcripts
Layer 0: Data          — Obsidian Vault, system-log.jsonl, 64 TB NAS archive