01
Source and release control
Repository source, pull requests, CI contracts, dry runs, deployment helpers, and rollback evidence.
Barndoor Platform
One operating model across source, host, public services, and edge nodes.
Barndoor combines infrastructure, operations, automation, local AI, public-safe telemetry, edge appliances, and recovery practices without hiding how the system works.
- Control model
- Centralized and human-approved
- Observation model
- Shared host and edge evidence
- Change model
- Source-controlled and reversible
Architecture
Four layers with distinct responsibilities.
Each layer shares the same standards for ownership, visibility, security, and recovery.
02
Bare-metal control plane
Ubuntu Server, system services, local AI, APIs, scheduled maintenance, backup tooling, and health collection.
03
Hosted and public surfaces
Websites, Discord applications, monitoring, Minecraft, product pages, and bounded public APIs.
04
Appliances and edge nodes
A permanent Pi NOC and authenticated apartment-edge reporting that observe state without becoming alternate control planes.
Capabilities
Built around the complete operating lifecycle.
Deployment, observation, maintenance, and recovery are connected responsibilities rather than separate tools.
Shared health model
Service checks, edge freshness, events, UPS state, thermals, and recovery evidence.
Validated releases
Reviewable source changes, automated contracts, preview-first deployment, and post-release verification.
Local intelligence
Private AI and focused automation that explain evidence and prepare human-approved next actions.
Recovery proof
Backups, checksums, rollback procedures, restore drills, and explicit runbooks.
Operating boundary
Distributed observation without distributed authority.
Small nodes may display or report health, but Barndoor remains the central source and control plane.
Edge reporting
Authenticated and bounded
Signed reports use freshness, replay, source, storage, and public-output controls.
Public access
Read-only summaries
Public pages expose operating posture without credentials, private paths, raw logs, or administrative controls.