# Where Boat says it hosts its servers

**The best supported answer is: Boat uses third-party virtual-machine hosts, including Hetzner and OVH.** Its privacy policy names “OVH, Hetzner, and similar VM providers” as infrastructure hosts used to run Boat. That rules out a claim that Boat is known to run only a self-owned data center. It does **not** establish that every Boat service, or the public website, runs on Hetzner or OVH at this moment. [Boat privacy policy][source-2]

There is no evidence in the material provided that identifies AWS as Boat’s infrastructure provider. The same policy also leaves room for other providers through the phrase “similar VM providers.” So the careful conclusion is:

- **Hetzner:** explicitly disclosed as an infrastructure host.
- **OVH:** explicitly disclosed as an infrastructure host.
- **AWS:** not identified in the available first-party disclosure.
- **Self-hosted data center:** not supported by the available evidence.
- **Exact current provider for a particular server or service:** not publicly established here.

This distinction matters because Boat has more than a marketing site. Its hosting documentation says that the Boat backend creates public routes for sandbox ports and registers them using the current machine address. That describes a backend and customer-facing machine infrastructure, but it does not name the cloud or data-center operator for those machines. [Boat hosting documentation][source-5]

A public DNS or IP lookup would normally show only the network serving a domain. It may reveal a CDN or proxy rather than the origin machine, so it cannot by itself prove where Boat’s backend or customer machines run. [DNS Robot][source-11]

In short: **Boat publicly acknowledges using Hetzner and OVH-style VM hosting. There is no supplied evidence for AWS, and no basis to claim a self-operated data center or one exclusive provider.**

[source-2]: <https://boat.dev/privacy>
[source-5]: <https://docs.boat.dev/hosting>
[source-11]: <https://dnsrobot.net/domain-ip>
