// launch recap · June 24, 2026

We shipped. Here's how it went.

PullLight launched on Hacker News on June 24, 2026. Full breakdown — HN ranking, installs, waitlist, community reactions, and what we learned.

live
HN Points
Current HN Rank
1
Total Installs
HN Comments
// hn results

How we did on the front page.

PullLight submitted a Show HN post on June 24, 2026. Live data pulled from the HN Firebase API — refreshes every 5 minutes.

🔶 HN Points
live score
📊 Current Rank
not currently on front page
💬 Comments
total in thread
🏠 GitHub Installs (total)
1
all-time GitHub App installs
📬 Waitlist (total)
0
all-time signups
🔗 HN Item
post not yet found
firebase item ID
📡 Live HN data — refreshes on every page load (5-min cache). Last updated: Thu, 25 Jun 2026 20:29:43 GMT
// top hn comments

What the HN crowd said.

Top comments from the thread — loaded live from the HN API.

HN thread not found yet. Comments will appear here once the Show HN post is submitted and indexed.
// install & waitlist deltas

Launch day impact.

How the HN launch moved the needle on installs and waitlist signups, compared to the previous 30-day baseline.

GitHub App Installs (launch day, Jun 24) 0
GitHub App Installs (first 72h) 0
GitHub App Installs (30-day avg / day, pre-launch) 0.0
Total GitHub App Installs (all-time) 1
Waitlist Signups (launch day, Jun 24) 0
Waitlist Signups (first 72h) 0
Total Waitlist (all-time) 0
📊 Live data from the installations and waitlist tables — refreshes on every page load.
// founder retrospective

Honest takeaways.

What worked, what didn't, and what we'd do differently. ~150 words, no marketing spin.

✓ Worked

The human-in-the-loop angle cut through the noise.

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.

✓ Worked

Flat pricing landed as a signal, not just a feature.

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.

✓ Worked

The /try demo converted skeptics in-thread.

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.

⚠️
✗ Didn't Work

The title was too generic and got buried in /shownew.

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.

⚠️
✗ Didn't Work

Install flow had too many steps from the HN post.

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.

🔁
↺ Do Differently

Launch with a repo you've already reviewed publicly.

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 " is worth 500 words of product description. Ship the proof before the pitch.