PullLight launched on Hacker News on June 24, 2026. Full breakdown — HN ranking, installs, waitlist, community reactions, and what we learned.
PullLight submitted a Show HN post on June 24, 2026. Live data pulled from the HN Firebase API — refreshes every 5 minutes.
Top comments from the thread — loaded live from the HN API.
How the HN launch moved the needle on installs and waitlist signups, compared to the previous 30-day baseline.
What worked, what didn't, and what we'd do differently. ~150 words, no marketing spin.
HN is oversaturated with "AI does X" pitches. The thing that got engagement was the constraint — PullLight doesn't auto-post anything. You approve before anything goes to GitHub. Multiple comments said they'd tried CodeRabbit, got burned by noise, and the approval gate was the reason to look again. Lead with the constraint, not the AI.
The $20/month flat price (vs. per-seat CodeRabbit) read as a statement about our values. Comments did the math unprompted — "at a 10-dev team this is basically free." We didn't engineer that reaction; it came from the pricing structure. Don't bury the flat-price model in fine print.
Several "I'll believe it when I see it" replies turned around after clicking the demo link. A live tool that runs on a real public PR in under 60 seconds is the best counter-argument to "AI code review is just noise." Keep the demo fast and don't require signup.
We submitted "Show HN: PullLight – AI code review with human approval." The phrase "AI code review" is table stakes on HN right now. We should have led with the outcome — something like "AI reviews your PR, you decide what to post." Lesson: your Show HN title is an ad, not a tagline.
The path was HN → landing page → /install → GitHub App auth. We should have put a direct GitHub App install link in the HN post itself. Every extra click costs a conversion. Next time: the submission URL should be the GitHub App install page or a one-click landing page, not the homepage.
The most credible thing we could have done was link to a real public repo where PullLight had already caught a real bug — in the submission, not as a separate link. A "here's what it found on