
It's a real Postgres database, so I'm never boxed in. I can write proper queries when I need real answers, not just what a limited tool allows. Row-level security lets me scope access properly (I built a read-only role for our Metabase reporting layer, and separate scoped roles for different schemas) without maintaining a separate auth/permissions service. The dual-schema support has also been valuable for keeping staging and core data cleanly separated in one project rather than spinning up multiple databases. Combined with the dashboard for direct table/data inspection, it's made verifying data quality mid-build (checking a contractor's work against source data) fast instead of a multi-tool ordeal. Review collected by and hosted on G2.com.
Some permission setups aren't obvious. Granting proper access for certain schemas took trial-and-error to get right. Row-level security rules also weren't straightforward to configure correctly the first time. Documentation could be clearer on these edge cases, so I ended up relying on testing things directly to confirm they actually worked. Review collected by and hosted on G2.com.