What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- How does the system keep each person's data isolated to only the channels and tickets they can access?From this comment
- Why does the site link to an API reference page that returns a 404?From this comment
- What exactly makes the retrieval approach better than ordinary retrieval-augmented search?From this comment
- How does this differ from a similar open-source search-and-chat product?From this comment
- By what mechanism are multiple users authenticated and queries filtered to their permissions?From this comment
What they doubted or pushed back on our summary
- One commented doubted a product leading with its underlying technology rather than customer outcomes.From this comment
- Someone objected to calling an agent interface chat, saying the word is being repurposed.From this comment
- One person noted that claims about data never leaving the network conflict with using hosted model providers.From this comment
- Someone asked what semantic search adds over lexical ranking beyond finding similar documents.From this comment
What the maker answered our summary
11 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Permissions are enforced in the application today, filtering records by each user's source access, with row-level security planned.From this comment
- The maker admitted the API reference page is unfinished and undocumented, though integrations are intended.From this comment
- The maker said search combines Postgres vector search with a full-text extension for better ranking.From this comment
- The maker conceded the self-hosting claim should be clarified when external model providers are used.From this comment
What a builder can take from it: If you show a product to this crowd, expect scrutiny of permission handling, honest hosting claims, and working documentation before anything else. our reading
The title, taken apart our calculation
This post got 177 points; the median for all 1442 posts is 112. In Developer tools (185 posts) the median is 106 points and 38 comments.
When it was posted our calculation
Monday at 08:00 UTC. Of 1,451 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 31 (2.1%) reached 50 points; on Mondays it was 3.1% of 7,396. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More Developer tools teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with