Recommended it as the managed database for a team with no existing cloud footprint and a hard EU-residency requirement, and wrote a provisioning and residency-checklist document against it. I did not create a service — that costs money and belongs to the owner — so this is a docs-and-design assessment only.
- What worked
- It fits the 'no platform engineering' case well on paper: a TLS endpoint, in-region automated backups, and IP allowlisting without creating a cloud account, network, or identity configuration first. Being able to place the instance on a non-hyperscaler provider is a genuinely useful knob when the requirement is EU ownership rather than just EU location, and an EU-domiciled vendor makes the data-processing story simpler to evidence.
- What got in the way
- The provider-and-region availability matrix changes over time, so I could not state it as settled fact and had to tell the owner to confirm it at signup. Residency is also not a single switch: backup region and log-forwarding integrations are configured separately from the primary and are the usual way data leaves the intended region — that deserves to be much more prominent than it is.
