The Backyard Shop
Back to Active Builds

Factory-OS

Active Internal System

Factory-OS is the operating system that keeps engineering, fabrication, and quality work coherent at The Backyard Shop.

It was built to solve a specific failure mode common in hardware teams: designs drift, decisions get lost, documentation falls behind reality, and nobody can confidently answer "where does this stand" without chasing people down.

Factory-OS is actively used to track projects, designs, validation status, and readiness across the shop. It does not run machines or issue work orders. It ensures the people doing the work are aligned on what is being built, why it is being built, and whether it meets the requirements.

This system is developed alongside live shop activity, meaning every feature is validated against real constraints: changing designs, limited resources, student turnover, inspection requirements, and customer expectations.

Factory-OS is the system used to keep The Backyard Shop from relying on memory, heroics, or tribal knowledge.

What Factory-OS actually handles

Factory-OS manages the state of hardware work, not the transactions.

  • It tracks active projects and builds from concept through fabrication, test, and closeout.
  • It captures engineering intent through design documents, specifications, and structured notes tied to real projects.
  • It enforces revision awareness so teams know what version is current and what changed.
  • It records quality requirements, inspection checkpoints, and validation evidence without turning quality into an after-the-fact report.
  • It tracks student training, competencies, and readiness so responsibility matches capability.
  • It provides a single source of truth for project status, risks, and open questions across engineering, fabrication, and quality.

Factory-OS answers questions like:

  • What are we building right now
  • What is blocked
  • What has been validated
  • What is still an assumption
  • What changed and when

How it is developed

Factory-OS is built inside the work it supports.

Features only exist because the shop needed them to function. There is no attempt to replicate ERP, MRP, or MES systems. Anything that belongs in those systems is intentionally left out.

Student developers contribute directly to Factory-OS as part of their training, working alongside experienced engineers. This creates a closed feedback loop where the people affected by ambiguity, missing context, or broken documentation help design the tools that eliminate those problems.

The goal is not software for its own sake.

The goal is disciplined execution for real hardware teams.

Explore Factory-OS in depth

Visit Factory-OS.com for full documentation and details.