What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- How the backend compute is sourced and whether users are locked into a cohort month to month.From this comment
- Whether the given throughput is total, realistic, or worst-case when everyone uses it at once.From this comment
- How resource hogging and reselling access would be prevented.From this comment
- How time sharing and batching work, including context size and worst-case wait for first token.From this comment
- Whether any cohorts have filled and how long filling takes, since people need timely access.From this comment
What they doubted or pushed back on our summary
- The join button shows no price before sending users to a payment page.From this comment
- The quoted throughput is too low for comfortable interactive use.From this comment
- The monthly price looks high compared with consumer subscriptions unless used constantly.From this comment
- The cohort model seems unworkable when fill timing is unknown and cohorts expire.From this comment
What the maker answered our summary
26 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The throughput figure is an average and a strong rate limiter handles abuse.From this comment
- Leaving out the price was a mistake and will be corrected.From this comment
- GPU scheduling comes from the serving engine, weights stay in memory, and requests are continuously batched.From this comment
- No cohorts have filled yet, but reservations are rising and unfilled ones will cancel after seven days.From this comment
What a builder can take from it: State prices upfront, clarify whether throughput is a guarantee, and show demand evidence before asking users to wait for a cohort to fill. our reading
The title, taken apart our calculation
This post got 188 points; the median for all 1442 posts is 112.
When it was posted our calculation
Saturday at 15:00 UTC. Of 4,000 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 133 (3.3%) reached 50 points; on Saturdays it was 3% of 4,953. 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