Fini's self-maintaining knowledge layer. It writes help articles from resolved tickets, flags conflicts, and grounds every AI answer in one cited source.
Hey Product Hunt :wave: Deep here, co-founder of Fini.
Over the past few months we spent 300+ hours with our customers just watching how they maintain their knowledge. One thing was constant: everyone hates it. Support teams lose 20 hours a week updating the help center by hand. A feature ships, a policy changes, and someone on the CX team spends their Friday rewriting articles. Every one of those updates is "urgent."
The deeper problem: when an AI support agent gives a bad answer, the model is almost never the reason. The knowledge is. Stale articles, contradicting articles, missing articles. You can't prompt-engineer your way out of bad source data.
So we built Knowledge Atlas, a self-learning knowledge base that updates itself:
- Connect your sources (help center, PDFs, past tickets, Slack) and Atlas builds a structured tree of cited articles
- Every resolved ticket becomes a new article automatically
- Conflicts between articles get caught and flagged before customers ever see them
- Every answer traces to exactly one source
And there's no RAG underneath. Search is LLM-native: the agent navigates the tree and reads whole articles the way a person would, instead of retrieving chunks and stitching them into blended answers. Our compliance-heavy customers in banking and healthcare care about that single-source traceability more than any accuracy stat.
Wefunder is already live on it: 22% increase in autonomous resolution, 30% increase in knowledge coverage, same team. The knowledge compounds now instead of decaying.
We'll build a free Atlas from your real docs in 24 hours, so you can judge it on your own knowledge instead of a polished demo.
I'll be here all day. Ask me anything, especially the hard questions about why we walked away from RAG.
The knowledge-tree-as-single-source makes sense for the ingest side. The contradictions that got us though weren't visible at ingest, they only showed up at answer time: two docs each internally fine, but a specific question pulled a clause from each and the combination was wrong. Nothing flagged on load because individually they were consistent. Do you run any contradiction check at answer-assembly, or is it all resolved when the tree gets built?
Sounds very interesting, I have not seen per resolution pricing. I would be more cautious about the setup/onboarding. If it needs to tie into your APIs, this is basically like a full-on product integration vs. an additional extension. What is the typical onboarding time for a customer from signup to full autonomy for a SaaS? I would think it would take lots of time from your CTO to get it done.
Auto-writing help articles from resolved tickets is the maintenance loop everyone skips, so the input-quality gate is what I would trust-test first. When a ticket gets resolved with a workaround or a wrong-but-accepted answer, what stops that from becoming a canonical article the AI then cites confidently? And the conflict flagging: is that just detecting two contradictory articles, or does it also catch an article that has gone stale against a product change no one has filed a ticket about yet?
Conflict detection as the mechanism is more robust than a plain TTL, that makes sense. The case that burned us wasn't two articles that obviously overlap, it was two that never shared keywords but still contradicted: an old refund window buried in a policy doc versus a newer one sitting in an FAQ. Nothing textual linked them, so a naive same-topic check slid right past it. Are you clustering on meaning or on citation overlap to decide two articles are really about the same thing?
The promotion gate reads solid, and Gal's thread pushed you to show the diff and reject UI, which helps. The failure I'd watch is the opposite direction: retirement. Auto-generating articles grows the base fast, but a resolution that was correct in March becomes a confidently-cited wrong answer the day a policy changes. In our own self-updating knowledge store, adding was trivial and detecting that a new article contradicts and should supersede an old one was where the real engineering went. Does Atlas check a new article against existing ones for conflict, or is the loop mostly additive?
Plugged it into our helpdesk and the gap detection alone saved us hours of retraining each week. Honestly impressive how accurate it stayed on banking edge cases without us babysitting it.
"fully autonomous in 30 days" for banking support is the line that'd make our compliance team nervous, not because the accuracy number is wrong but because autonomous means nobody signed off on the specific answer that went out. in a regulated industry the audit trail of who approved what usually matters as much as the answer being correct. does a human ever get a say before an article it wrote itself starts getting cited to customers?
Congrats on the launch. Looks impresive. Do you have any support for images / screenshots also?
plugged it into our helpdesk last week and it caught gaps in our knowledge base we hadn't noticed for months, which was a nice surprise.
Took it for a spin on our support inbox last week and it actually flagged its own gaps instead of guessing, which is rare. Loved that it dropped into Zendesk without forcing a migration.
the part that gives me pause is "every resolved ticket becomes a new article automatically." a resolved ticket isn't the same thing as a correct or generalizable answer, sometimes a resolution is a one-off workaround, a support agent's judgment call that shouldn't be policy, or honestly just the AI getting lucky on an edge case. auto-promoting that into a permanent cited article feels like it could bake exceptions in as rules over time, which seems like exactly the kind of slow-drift problem you're trying to solve with the conflict flagging. is there a review step before a ticket-derived article goes live, or does it publish straight into the tree and rely on the conflict detector to catch it later
About Knowledge Atlas by Fini on Product Hunt
“The self-learning knowledge base that improves itself”
Knowledge Atlas by Fini launched on Product Hunt on July 8th, 2026 and earned 104 upvotes and 29 comments, placing #18 on the daily leaderboard. Fini's self-maintaining knowledge layer. It writes help articles from resolved tickets, flags conflicts, and grounds every AI answer in one cited source.
Knowledge Atlas by Fini was featured in Productivity (655.7k followers), Customer Success (6.2k followers) and Artificial Intelligence (473.1k followers) on Product Hunt. Together, these topics include over 252.2k products, making this a competitive space to launch in.
Who hunted Knowledge Atlas by Fini?
Knowledge Atlas by Fini was hunted by Deepak Singla. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Knowledge Atlas by Fini stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Deepak Singla