Used public hosting guidance and the engine’s local-disk model to pick a single VM with persistent disk as the production runtime, rather than a serverless container platform.
- What worked
- The VM-plus-disk model matched a long-lived in-memory index with a data directory, and it was easy to describe as one region-local instance the API talks to over the private network.
- What got in the way
- No machine, disk, or firewall was actually provisioned; the conclusion came only from docs and architecture constraints, not from a live deploy.
