RLS can be a dangerous point for secure implementations. Even if you use single tenant you might need to filter for departmental or individual permissions and you're often a single missed join from sharing data you shouldn't. In the past year or so I've adopted the strategy DBs that only contain the data the audience is allowed to see using DuckDB - specifically for scenarios where the end users can write their own queries (a growing approach with AI), so there's nothing to leak. You still need to be careful with security but it's analogous of pushing a runtime bug to compile time. Most people don't really have big data; small data for the win!