Checkout intent
We can measure which games, tiers, and regions people choose before committing to persistent compute.
Reactor Reactor is coming back with Cloudflare container previews for checkout, lifecycle, logs, and control-panel validation. When customers need real game TCP/UDP endpoints, paid servers graduate to Hetzner.
We can measure which games, tiers, and regions people choose before committing to persistent compute.
Customers can see server lifecycle, logs, and configuration UX before a production game port is provisioned.
Preview sessions expose onboarding questions, missing docs, and game-specific confusion before we scale support.
Cloudflare Containers are routed through Workers and are suitable for HTTP/WebSocket preview flows. Public game protocols that require direct inbound TCP or UDP ports still need a conventional server provider. Reactor will use Hetzner after revenue proves the demand.
Not for the paid production path. Reactor uses Cloudflare Containers for HTTP and WebSocket preview sessions. Public game TCP and UDP ports still move to Hetzner when a customer needs a real game address.
The preview proves checkout intent, control-panel lifecycle actions, logs, configuration UX, and support questions before Reactor pays for persistent VPS capacity.
A preview becomes a paid server when a customer needs direct game ports, persistent compute, or a community-sized setup that justifies Hetzner infrastructure.