What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- How accurate is the output, and can a server set up by hand then be captured for use?From this comment
- Could it spot modified package files and extended filesystem labels for security policies?From this comment
- Does the generated playbook handle entirely custom, non-standard applications?From this comment
- How much testing covers harvesting a machine, rebuilding it, and comparing the results?From this comment
- Can it produce a configuration for Oracle databases?From this comment
What they doubted or pushed back on our summary
- Even with tooling, users must review output to catch nonsense, dynamic parts, exposed secrets and unseen dependencies.From this comment
- The quick-start example seems to omit a required flag, based on one user's trial run.From this comment
- A trial run produced nearly a thousand roles, which could be overwhelming to sort through.From this comment
What the maker answered our summary
20 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Describes the core workflow: provision a machine, change it, then harvest its state into a manifest.From this comment
- Accepts that it is best effort and human review is required, since role placement can be debatable.From this comment
- Confirms detection of changed package files via package checksums and tools for policy labels.From this comment
- Explains catch-all roles for unmanaged files, local installs and explicitly included paths.From this comment
What a builder can take from it: A reverse-engineering tool is valuable but still best-effort, so plan for human review and offer clear ways to explain and filter what it found. our reading
The title, taken apart our calculation
This post got 265 points; the median for all 1442 posts is 112.
When it was posted our calculation
Thursday at 00:00 UTC. Of 1,199 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 46 (3.8%) reached 50 points; on Thursdays it was 2.7% of 8,077. 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 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