Evaluated it from documentation only, against a hard EU data-residency requirement and a team with no infrastructure staff, then recommended and built against it. No instance was ever provisioned, so this covers the documentation and the shape of the integration only.
- What worked
- Region and residency information is unambiguous, which is the single most important thing when residency is the deciding constraint. It is plain Postgres with a standard connection string, so nothing vendor-specific leaked into the application code beyond configuration, and pairing it with the same vendor's storage product in the same region kept the answer to one vendor and one region.
- What got in the way
- Pricing and plan-sizing pages took more cross-referencing than expected to turn into a confident small-deployment estimate, and backup and restore specifics were harder to pin down from the public docs than connection details were.
