Multi-tenant Approach using One Project per Tenant
Is this sort of the ideal approach to multi-tenant (project per tenant) with Neon?
9 Replies
extended-salmonOP•15mo ago
Context: this is from Neon AI
extended-salmon•15mo ago
Hey! Do you mind sharing more details about what you're building?
Happy to point you in the right direction 😄
extended-salmonOP•15mo ago
Hey @Mahmoud I'm trying to build a single backend api that will handle multi-tenant requests. I'm essentially trying to achieve this using tenant/project.

extended-salmonOP•15mo ago
^got this from this blog: https://neon.tech/blog/multi-tenancy-and-database-per-user-design-in-postgres
Neon
Multi-tenancy and Database-per-User Design in Postgres - Neon
The first blog post of a series series dedicated to building and scaling multi-tenant, database-per-user apps in Postgres via Neon.
generous-apricot•15mo ago
I too am looking into exactly this. I.e the recommended approach / best practice (with example code would be added bonus). This is the closest I have found ... https://github.com/neondatabase/ai-vector-db-per-tenant
GitHub
GitHub - neondatabase/ai-vector-db-per-tenant: Example chat-with-pd...
Example chat-with-pdf app showing how to provision a dedicated vector database instance for each user. Powered by Neon - neondatabase/ai-vector-db-per-tenant
extended-salmon•15mo ago
This is something we're actively working on documentation-wise
Do you mind sharing more details about your tech stack of choice?
generous-apricot•15mo ago
@ʞk ... 👆 ... I don't want to hijack your thread 😉
extended-salmonOP•15mo ago
Currently using Elysia.js for backend and Next.js for frontend.
No worries!
extended-salmon•14mo ago
https://discord.com/channels/1176467419317940276/1176467419938701375/1289308541638934578 We published a video about multi-tenancy here