DEV Community

Kandiah C
Kandiah C

Posted on

Discussion and suggestion on an idea

๐Ÿš€ 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! ๐Ÿš€

Top comments (0)