iKB by ThoughtsMachine

Hi Product Hunt, I’m Sanjay Willie from ThoughtsMachine. Over the past few months, I’ve been building iKB an AI powered knowledge base platform for teams who need more than basic RAG. I kept looking for something like this in the market, but most options either felt designed for personal use, or they didn’t have the knowledge sharing capabilities I needed. So I built one. It started as a way for us to share our own technical knowledge base with customers, but it quickly evolved into a platform our clients asked to use for their own internal knowledge as well. What is iKB? iKB is a self hosted platform that lets you build conversational interfaces over your document libraries. It combines traditional vector based retrieval with knowledge graph construction, which materially improves accuracy for complex, multi document queries. Users can create topics, include one or many documents in those topics, including dimensional data like worksheets (excel, etc) and can perform analytics from it by dynamically generating isolated pandas queries. It can also ingest open drawing format (DXF), extract layers and visually understand drawings like humans could. 1) Trust, Safety, and “No Leaks” If iKB can’t be trusted with sensitive internal knowledge, nothing else matters. The first priority is making sure confidential content stays confidential, and that we can confidently deploy it without fear of data exposure. 2) Control Over Who Sees What In a real organisation, not everyone should see everything. The next most important value is the ability to define access cleanly by department, team, group, topic, and channel so the knowledge is shared with the right people and hidden from the wrong ones. 3) Governance and Accountability (Audit Trail) When something changes, or a mistake happens, you need traceability. Business leaders care that there is an audit trail: who did what, when, and from where so the platform supports internal governance, compliance expectations, and operational discipline. 4) Reliability and Operational Stability A business user doesn’t want a “smart demo.” They want something that works every day. The platform needs to be stable, recover cleanly from issues, and handle failures gracefully without breaking workflows or silently losing data. 5) Accurate Answers on Real World Questions (Not Just Simple RAG) This is the point of iKB: accurate answers to complex questions that span multiple documents, policies, departments, and versions. Business users care less about how retrieval works, and more about: “Does it give me the right answer, consistently, with the right sources?” 6) Proof of Answer Quality (Measurable Confidence) Beyond “it seems correct,” iKB gives a way to measure and monitor quality over time. For a business user, this means you can spot weak areas, track improvement, and build confidence internally especially when the platform becomes relied upon for real decisions. 7) Rollout Across Real Channels (Where Work Actually Happens) A platform is only useful if it fits the day to day workflow. Business users care that iKB can be deployed where employees and customers already communicate web chat, embedded widgets, and omni channels like WhatsApp, Telegram, SMS, email without reinventing the way teams operate. 8) Human Handover When It Matters AI shouldn’t be a dead end. When the user needs help, escalation must be seamless. Business users value clear handover triggers, proper routing, and a clean way for an agent to take over without losing context or creating chaos. 9) Easy Knowledge Ingestion From “Messy Reality” Organisations don’t have perfect documents. They have PDFs, Word files, spreadsheets, slide decks, web pages, and images stored across drives and systems. Business users care that iKB can absorb this reality, keep it organised, and stay updated when content changes. 10) Data Retention Controls and Sensitive Conversation Options Some conversations should be stored, others should not. Business users value the ability to apply retention rules and enable private/ephemeral modes when needed so the platform can be used even in sensitive or regulated contexts. 11) Cost Visibility and Usage Control Once AI is deployed broadly, cost becomes a business problem. Business users want visibility: usage by topic, by channel, by time period, and controls that prevent runaway spend without requiring a data team to interpret it. 12) A Platform That Fits Enterprise Procurement Reality This is often the deciding factor: the company wants ownership and control. Self hosting, data ownership, no lock in, and predictable licensing matter because they reduce procurement friction and long term risk. 13) Administration That Doesn’t Become a Full Time Job Business adoption fails when the admin overhead is too high. Business users care that topics, widgets, channels, users, access rules, and configurations can be managed cleanly preferably with bulk actions and predictable defaults. 14) Branding, UX Polish, and Localization This matters for adoption and user comfort, especially in external facing deployments. But it’s not what makes the platform enterprise grade. It’s what makes it feel natural once the fundamentals above are solid.