BROCK FISCHER

Useful systems, built deliberately.

A personal platform for technology, home automation, infrastructure, and practical projects.

PROJECTS

What I’m building

HOMELAB

Self-hosted, but maintainable

Unraid, containers, monitoring, backups, and remote access built around explicit security and recovery boundaries.

Infrastructure

AUTOMATION

Useful over flashy

Automations that reduce friction, expose useful state, and keep working without unnecessary cloud dependencies.

Home Assistant

PLATFORM

BrockFischer.com

A small public surface with private tools, operational dashboards, and authenticated applications behind clear boundaries.

Cloudflare · self-hosted apps

PLATFORM MAP

Different jobs, different trust zones

Convenience should not collapse the boundary between a public page, a private household app, and an administrative control plane.

01PUBLIC

Public surface

Static pages meant to be readable by anyone. No household telemetry, admin controls, or private application state belongs here.

brockfischer.com · minimal data
02AUTHENTICATED

Private applications

Dashboards and utilities can be reachable in a browser without exposing their upstream credentials or turning them into infrastructure admin consoles.

Identity-gated · purpose-built
03LOCAL / PRIVATE NETWORK

Administration

Infrastructure control stays on the narrowest practical access path. A useful dashboard is not a reason to publish an administrative interface.

Least exposure · explicit recovery

Design rule: move summarized state outward only when it has a clear purpose; keep credentials and privileged control at the source.

PRINCIPLES

How I want it to work

Local-firstKeep core home functions useful even when outside services fail.
Secure by separationPublic content, private apps, and administration are different trust zones.
ObservableKnow when something breaks, why it broke, and whether backups are actually recoverable.
MaintainableDocumentation and rollback matter as much as getting something running once.