Could you please provide the missing inputs: Parent category, Subcategory, MAIN KEYW

[Jeffrey71]

I've been genuinely pleased with the flexibility and control that open source software provides for custom business solutions. Our small marketing agency in Toronto is building a client reporting dashboard, and we've settled on using a stack built around Metabase for visualization and PostgreSQL for the backend, all deployed on a DigitalOcean droplet. The core functionality is there, but we're now facing the challenge of making the system truly multi-tenant for about 15-20 different clients, each with their own data isolation and branded UI expectations, while keeping our operational costs under $200 per month. We're unsure about the best architectural pattern to follow at this scale—should we use a single database with schema separation, separate databases per client, or rely on row-level security? Furthermore, what open source tools or libraries have you found most effective for managing user onboarding, access control, and white-labeling in a self-hosted scenario like this, and are there any hidden pitfalls with data backup strategies when using a multi-tenant approach?