Tyler Rodgers / Infrastructure, Operations, and Software

Building self-hosted infrastructure, local AI, and operations software.

I’m Tyler Rodgers, a datacenter technician building Barndoor: a personal self-hosted infrastructure and AI operations platform. The project combines bare-metal Linux, Discord applications, public websites, monitoring, Minecraft, power telemetry, backups, recovery practice, and dedicated Raspberry Pi appliances.

Now Building · Build Log · Barndoor · NOC · Barndoor Labs · Haystack

Built and hosted from Barndoor

This site, TM44.link, Barndoor Labs, the full Barndoor NOC, the compact Pi wallboard, Haystack, and supporting project services are operated from my self-managed environment. Source changes move through Git review, automated release checks, guarded deployment previews, and rollback-backed live updates.

Self-Hosted Source-Controlled Public-Safe Telemetry Rollback-Backed Online

Current Focus

Turning a verified multi-node platform into clearer operator guidance

Barndoor now has authenticated edge telemetry, a touch-first Pi NOC with service intelligence, UPS awareness, shared health APIs, strict maintenance checks, and documented recovery paths. The current phase is about extracting better decisions from that evidence rather than adding another control plane.

The next improvements center on Shepherd’s bounded operator guidance, historical metrics and event quality, continuously fresh restore evidence, and documentation that can prove source, live deployment, and public copy still describe the same system.

See what I’m working on now →

Shepherd Historical Metrics Restore Evidence Source / Live Parity AI-Assisted Operations

Build Log

The latest verified milestone is highlighted below. Open the archive for the complete history of infrastructure, software, operations, and recovery work.

Latest build log

Barndoor Edge telemetry gained an operations and recovery layer

Barndoor Edge telemetry now has a focused bdops health check, bounded outage classification, and a complete operations and recovery runbook.

Synthetic contracts cover healthy, stale, critical, and recovered states while keeping runtime output public-safe and all recovery actions explicit.

Read the full build log →

Barndoor Monitoring Operations Recovery

Current Stack

The platform connects bare-metal hosting, containerized services, local AI, Discord applications, public-safe telemetry, authenticated edge reporting, source-controlled automation, and recovery documentation.

Ubuntu Server systemd Docker Caddy Node.js Ollama Discord.js Uptime Kuma Tailscale Network UPS Tools Raspberry Pi

Operating Principles

Barndoor is developed with small changes, exact source/live boundaries, read-only checks before mutation, automated contracts, explicit dry runs, selective deployment, and rollback evidence. Private credentials and raw operational details stay outside the public site and outside source control.

Small Changes Fail Closed Test Before Deploy Document Recovery

Contact / Links

Start here

Follow the build.

This site documents the infrastructure, software, appliances, and operational practices I’m building and running through Barndoor.