Hosting upgrade fieldbook

Change the host. Keep the evidence.

Migration and hosting runbooks built around verification, recovery, and explicit ownership.

BaselineCopyVerifyRouteObserve

Active runbooks

Begin with the failure boundary, not the provider logo.

Migration

A staged hosting migration that preserves a working origin, verifies the new stack, and treats DNS as the final routing change.

Planning

Translate traffic shape, storage growth, recovery needs, and operator capacity into a hosting baseline.

Infrastructure

Compare isolation, predictable resources, hardware responsibility, and recovery work before renting an entire server.

Library

Real-time hosting

Use latency, simulation rate, player concurrency, mod behavior, and recovery needs instead of generic web-hosting metrics.

Operations

Inventory panel-managed services, reproduce them explicitly, and avoid losing mail, scheduled work, or certificate renewal.

Support

Turn a vague outage into a timestamped, bounded report that a provider can act on without exposing credentials.

Health infrastructure

Separate application, provider, identity, data, support, and recovery ownership before evaluating a care platform.

Every change has a comparison point and rollback condition.

Historical paths are used for modern educational material, not old offers or identities.