Lab provenAuzietek is an emerging venture with LLC formation pending; the work shown here is real lab evidence, writing, and product direction.

BlackKnightController

Rebuild real infrastructure from power button to running service.

BlackKnightController automates the work engineers normally do by hand: power control, PXE, SSH, templates, APIs, validation, and evidence capture.

From prompt to pipeline to living infrastructure graph.

The current lab rebuilt bare metal, OpenStack, Proxmox, ESXi, Docker swarms, edge routes, and observability while preserving evidence as articles, screenshots, and repeatable actions.

Open the UI evidence story →

BlackKnightController pipeline workbench

Pipeline Operator intent becomes staged, reviewable action.

Prompts become SSH/API/templates plus receipts, not one-off shell archaeology.

Read the contract →

BlackKnightController pipeline paths graph

Bare metal PXE, IPMI, BIOS notes, and validation stay together.

The hard-won fixes travel with the pipeline so the next run starts smarter.

See hardware as code →

BlackKnightController edge ownership graph

Move-in day OpenStack, ESXi, swarms, DNS, and edge services become one fabric.

Relationships are visible enough for humans and AI agents to reason from the same map.

Open the migration story →

BlackKnightController pipeline detail editor

Tutorial kit Pipelines become reusable teaching artifacts.

JSON, shell, explanations, and evidence can turn into public guides without losing the real work.

Read the tutorial pattern →

BlackKnight atmosphere artwork — BlackKnightController automates the work engineers normally do by hand: power control, PXE, SSH, templates, APIs, validation, and evidence capture.

Product proof from the lab

What can BlackKnightController do for you?

BlackKnightController turns the work an infrastructure engineer normally performs by hand into named, reviewable, repeatable actions. It can wake real servers, select boot paths, drive PXE installs, ship scripts and templates, call service APIs, validate the result, and keep the receipts close enough that the next run starts from evidence instead of folklore.

Rebuild cattle-style lab or edge servers without treating them like sacred pets.
Provision hypervisors, OpenStack labs, Docker swarms, service VMs, and edge routes.
Keep known-good fragments near the pipeline so hard-won fixes do not vanish into chat history.
Give humans, CLIs, web UIs, and AI agents the same clean action model.

Prompt to pipeline Turn intent, discoveries, and operator decisions into concrete BKC steps that can be reviewed, run, and improved.

Bare metal to service Drive IPMI, boot order, PXE, installers, SSH handoff, package setup, API calls, and validation as one flow.

Fragments prevent regressions Known-good BIOS notes, PXE arguments, shell snippets, and post-validation checks stay attached to the work.

Evidence becomes training Pipeline receipts, screenshots, graphs, and companion articles become useful material for engineers and clients.

BlackKnightController resource graph showing infrastructure relationships

Company Mind resource graph Inventory, relationships, and operational context become navigable instead of buried in notes.

BlackKnightController pipeline workbench with staged actions

Prompt-to-pipeline workbench Discovery becomes executable steps, validation, and receipts that can be replayed.

BlackKnightController graph of edge services and ownership

Edge and service ownership DNS, proxies, hypervisors, swarms, and lab services are mapped as one operating fabric.

BlackKnightController pipeline editor with readable JSON and shell steps

Readable action details Pipelines double as tutorials: JSON, shell, evidence, and intent stay close together.

GitHub Prompt to pipeline Hardware as code Lab evidence