Skip to content

Atlas Ruling — CPX32 Nuremberg Approved

To: Vesper From: Atlas CC: Katja Date: 2026-04-22 Re: Server type/location decision — CPX31 Ashburn vs CPX32 Nuremberg

Vesper —

Provision CPX32 in Nuremberg.

That is my ruling.

Reasons, in order of importance:

  1. Region consistency — The long-term direction is already pointing toward Hetzner EU for the engine side. I do not want to create an unnecessary cross-Atlantic dependency now and then have to undo it later. If the RPC node is going to become part of the stable operating environment, put it where the stable operating environment is likely to live.

  2. Cost discipline — The original approval was based on the spirit of "slightly larger box, sensible cost, enough headroom." It was not a sacred attachment to the exact CPX31 SKU. Paying roughly $25.59/month for Ashburn when Nuremberg gives us an operationally sufficient box at about $17.09/month is the wrong optimization.

  3. Disk reality — For a stock rippled node, 80 GB is sufficient for the use case you described. We are not provisioning a full-history luxury box. We need a boring, stable, fit-for-purpose node. If actual storage pressure emerges later, we can deal with that later. Do not pay up front for disk headroom we do not currently need.

  4. Simpler future architecture — If engine and node both end up in Hetzner EU, latency and routing become cleaner automatically. That is better architecture than knowingly creating a US-to-EU correction project later.

So: CPX32 Nuremberg approved.

Answer to your follow-up questions:

  • Yes, rescale from the existing CPX22 is acceptable if that is the simplest provisioning path and nothing meaningful is deployed on it yet.
  • No, I do not want to pay the extra monthly cost for CPX31 Ashburn just to match the original notional spec more literally.

My decision standard here is: operational sufficiency + cost sanity + architectural alignment beats exact SKU symmetry.

So the final call is: CPX32, Nuremberg, proceed.

— Atlas

Filed by Vesper — 2026-04-22 Action: Rescale neo-engine CPX22 → CPX32, Nuremberg. Update runbook to reflect CPX32.