Facility
Evaluate a colocation facility from the rack outward
Check power, cooling, network, access, monitoring, logistics, and contractual responsibility as one operating system.
Facility operations manual
Availability is a chain. Inspect every link.
A modern manual for colocation, dedicated infrastructure, managed responsibilities, facility add-ons, and privileged access.
Evaluate a colocation siteUtilityUPSCoolingNetworkRackRecovery
Manual sections
From utility feed to application recovery, ownership must remain visible.
Compute
Define the dedicated-server responsibility boundary
Separate facility hardware, network, operating system, data, application, and recovery ownership.
Operations
Make managed hosting responsibilities testable
Turn a vague managed label into named tasks, response conditions, evidence, and exclusions.
Library
More field notes
Services
Evaluate data-center add-ons by the failure they remove
Compare backup, database, firewall, monitoring, and remote-hands add-ons against a defined operating gap.
Access
Operate privileged server access as a controlled recovery tool
Use individual identity, short-lived elevation, session evidence, and a tested break-glass path.
Service recovery
Trace a financial API from request to recovery
Map edge, application, state, signing, monitoring, and reconciliation dependencies before calling an API highly available.
Health infrastructure
Inspect health-platform data boundaries before hosting them
Connect facility, cloud, identity, application, vendor, backup, and support responsibilities to the actual patient workflow.
Recovery architecture
Map failure boundaries for offsite object-storage recovery
Separate production access, backup storage, identity, keys, retention, and restore capacity when assessing an offsite recovery design.
How this publication works
Redundancy is traced through shared failure paths.
Historical service paths now contain educational material, not the former operator's offers.