Now that WeWeb has a backend built-in, I’m trying to decide if I should build one app with a multi-tenancy structure, or duplicate the app for each institution using my product. I know that multi-tenancy is generally better for scale, but it also introduces complications. Each organization using my product will require some human-assisted onboarding, so it wouldn’t be crazy to just duplicate each app for each organization. Anyone weigh this before, or does anyone at weweb have specific guidance for this?
Hey Kyan! Good to hear from you 
If you’re going to go with the duplication approach, I would highly recommend that you have one project that’s not used by anyone but that you share as a library to all the other projects. That way, if you need to make a change in style, you can push that change to all the projects.
That said, I think that, for maintenance, there are a lot of downsides to choosing the duplication approach because, when you make an update (add a feature, change a workflow, etc.), you have to do it multiple times instead of just once 
Hey Kyan - as someone who built a single tenant application and went the duplication route, I’d highly suggest against it.
Multi-tenancy is the way to go, especially because of the pure difficulty in making updates across multiple versions of your product. It’s a real nightmare and becomes unmanageable at even the smallest scale. I eventually just rebuilt as multi-tenant and life is much much easier now.
I haven’t used the new data tables from weweb yet, so not sure where they stand for multi-tenancy, but I’d highly suggest using Supabase and building out the multi-tenancy from their using RLS. It’s pretty straightforward and the supabase AI can help you do it.
Hope this helps!