Multitenant
I am contemplating on vibe coding a multitenant saas with multiple subdomains, so basically for teams. The built in auth for opensaas has scant ways on how to achieve that, and my tries are just error ridden. any elegant way of doing that?
4 Replies
Hi @ondiekijunior. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, there isn't a built-in elegant solution for implementing multi-tenancy with subdomains in Wasp or OpenSaaS out of the box. However, I can provide some insights and suggestions based on the available information:
1. Custom Implementation: You would need to implement multi-tenancy yourself, as Wasp doesn't have native support for it. This aligns with the response from a Wasp community member in the Discord support thread about multi-tenancy.
2. Database Design: A community member shared a Prisma schema for a GitHub-like multi-tenant SaaS, which might be helpful as a starting point. It includes features like individual user accounts, organization accounts, team support, and role-based access control. You can find this schema in the Discord thread about Prisma schema for a github-like multi-tenant saas.
3. Deployment Strategy: One approach suggested in the Discord thread is to deploy your app multiple times, each with a different database. However, this might not be the most efficient solution for true multi-tenancy with subdomains.
4. Security Considerations: When implementing multi-tenancy, ensure proper data isolation between tenants. The typical approach is to have a single database with data from many users, and your server ensures each user can access only their own data.
5. Custom API Endpoints: You might need to set up custom API endpoints to handle tenant-specific logic. Wasp supports creating custom API endpoints, as mentioned in the Wasp documentation on advanced APIs.
To implement subdomains for teams, you would likely need to:
1. Modify your DNS settings to support wildcard subdomains.
2. Implement logic in your app to determine the current tenant based on the subdomain.
3. Adjust your authentication and authorization system to work with the multi-tenant setup.
Given the complexity of implementing true multi-tenancy with subdomains, you might need to extend Wasp's capabilities significantly or consider using additional tools or services alongside Wasp to achieve your desired architecture.
If you're running into specific errors or issues, it might be helpful to share those in the Wasp community Discord for more targeted assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ondiekijunior, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Would love to know as well.
Add middleware on the API routes, based on the subdomain, that determine the relevant organization and check the user is a part of it. thats the high level approach
Can explain more if you want more details, I do this on block-spot.com
@Noah please do share, it's also interesting to the Wasp team to see what you had to do to achieve it so we can find ways to improve Wasp 🙂