๐ Exploring an idea โ would love to hear your thoughts!
Iโve been thinking about building a platform that can help businesses provide AI-powered customer support using their own business data, documents, policies, product information, and more.
But one question Iโm currently exploring is not the AI model itself โ itโs the architecture and delivery.
For a platform that may serve multiple businesses:
๐น Should we maintain completely separate vector databases for each business?
๐น Or would a shared, multi-tenant vector architecture with proper metadata isolation be more efficient and scalable?
๐น How should the knowledge be organized when a business has products, policies, FAQs, documents, and constantly changing information?
๐น More importantly, how should the final product actually be delivered to the client?
Should it be:
โ A simple website-embeddable chatbot
โ An SDK/component they can integrate into their existing application
โ An API-first platform
โ Or a combination of these approaches?
Iโm currently exploring the best balance between scalability, data isolation, infrastructure cost, ease of integration, and the actual value delivered to businesses.
Iโd genuinely appreciate perspectives from developers, architects, SaaS builders, and anyone who has worked with RAG, vector databases, multi-tenant systems, or AI-powered customer support platforms.
Iโm still shaping the architecture, so Iโd love to learn from different approaches and experiences. ๐
If you have any ideas, suggestions, or architectural approaches, please feel free to comment or DM me. Iโd be really excited to discuss and learn from you! ๐
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)