The rack everything else gets tested against
Owned server infrastructure in San Diego used as the proving ground for remote-operability work: if a change cannot be made safely from another continent, it does not leave this rack.
What this is
A lab. Not a data centre, not a commercial hosting facility, and not a service with a support contract behind it. It is the hardware I own and run, and it exists so that architecture decisions get made against real equipment instead of a diagram.
Why it matters to a client
Most infrastructure advice is written by people who will never have to fix the thing at 3am from a different time zone. Everything I recommend for a remote or constrained site has failed here first, on purpose, so I know what the recovery actually looks like rather than what the vendor documentation claims.
What is deliberately not published
No live dashboard, no management interfaces, no network diagram, no addresses, no uptime figure. A public marketing site has no business exposing an operator's infrastructure, and an uptime number without a measurement method and a defined scope is decoration rather than evidence.