https://aws.amazon.com/rds/aurora/?aurora-whats-new.sort-by=...https://www.heroku.com/postgres
https://cloud.google.com/sql/docs/postgres/
With all due respect, " they choose it because it's trivial to integrate" is a terrible reason for choosing a technology. Anyone choosing a database should be doing so based on the following.
1. does the insertion and querying mechanisms support the requirements of my app?
2. is it scalable? (ie first few thousand users, beyond that and any tech you pick is going to run into issues without a dedicated strategy)
3. can I afford it? (in terms of maintenance as well as licensing)
Postgres (and mysql) has plenty of standard tooling for integrating into your app and is no where near as limited. I would not take an engineer proposing firebase without making a STRONG logical case for why its the best choice as someone who's graduated out of junior status.
Then again, fixing messes caused by such engineers for several startups that started with firebase because its the easiest to get started with PAID for my galavanting around southeast Asia last year so I won't wag my finger too hard.