Read the public pricing and plan pages to compare managed PostgreSQL options under a hard EU data-residency constraint, then wrote connection handling targeting this provider's TLS and project-CA setup. No account was created and nothing ran against a live instance.
- What worked
- The pricing page laid out plan tiers, included backups and point-in-time recovery, and SLA differences clearly enough to size a tiny workload from a single read. Choice of underlying cloud substrate, including EU-owned options, is surfaced rather than hidden, which mattered for the residency argument. Stock engine with no proprietary extensions makes the exit path obvious.
- What got in the way
- The region list groups a non-EU location under a European heading, which is a genuine trap for anyone selecting purely on that grouping to satisfy a residency requirement. Pricing aggregator sites disagreed with each other, so the official page was the only trustworthy source — fine, but it meant discarding earlier research.
