A server fleet is a power, cooling, firmware and spare-parts system
A LibreInfra field note on physical infrastructure control planes, BMCs, firmware baselines, spares and hardware recovery.
LibreInfra dispatch
Newsletter
Subscription entry point for careful notes on open infrastructure, operations, security, data stewardship and AI-ready systems.
Latest Research Articles
GPUs run LLMs because memory movement is the real workload
A LibreInfra field note on accelerator sizing for LLM inference, memory capacity, KV cache, interconnect and software support.
The R730 generation is still useful—inside a deliberate boundary
A LibreInfra field note on using R730-class hardware responsibly for labs, backup targets and recoverable internal platforms.
A server type is a workload decision, not a chassis preference
A LibreInfra field note on choosing server types from workload shape, serviceability, power, cooling and failure boundaries.
A historian, a broker and a data lake are different systems
A LibreInfra field note on brokers, historians, data lakes, archives, time, asset identity and recovery contracts.
Latest Reviews & Analysis
Edge infrastructure must survive the loss of the centre
A LibreInfra field note on edge autonomy, local identity, store-and-forward integrity, updates and recovery.
Infrastructure as code is only as ownable as its state
A LibreInfra field note on infrastructure-as-code state, provider versions, drift, execution authority and recovery.
Kubernetes is an orchestration engine, not an operating model
A LibreInfra field note on treating Kubernetes as one control plane inside a wider platform contract.
AI agents are infrastructure identities, not assistants with tools
A LibreInfra field note on governing AI agents as delegated infrastructure identities with bounded permissions, memory, tools, budgets and evidence.
Digital sovereignty is the ability to change course
A LibreInfra field note on digital sovereignty across authority, data, identity, operations, interoperability, open source and exit capacity.
Ownable infrastructure for the AI era
A LibreInfra field note on why AI-ready systems need open foundations, clear ownership and practical operations.
Jose
Observability should produce evidence, not just dashboards
A LibreInfra field note on observability as evidence: control-plane events, recovery records, alerts, retention and incident reconstruction.
Jose
Automation that cannot be transferred is another dependency
A LibreInfra field note on automation ownership, transferability, state, credentials, failure behaviour and operational evidence.
Jose
Reproducibility is an infrastructure property, not a documentation task
A LibreInfra field note on clean reconstruction, controlled inputs, drift, provenance and why reproducibility must be exercised rather than merely documented.
Jose
Managed platforms need an exit design before migration becomes urgent
A LibreInfra field note on designing exit across data, configuration, identity, evidence, operations and supplier boundaries.
Jose
Identity is the control plane most infrastructure diagrams leave out
A LibreInfra field note on identity as the control plane for human access, workload access, recovery authority and evidence.
Jose
Open source does not automatically make infrastructure ownable
A LibreInfra field note on why open-source rights must be connected to reproducibility, recovery, maintenance and transfer.
Jose