build in public, finally

Stop procrastinating.
Start shipping.

We know how to code. We just don’t know how to sell. BuildBoost reads your GitHub commits, hypes you up, and writes the posts, so you actually share what you build.

Connect GitHubSee the feed

Free in early access · No auto-posting, ever

your commits this week

  • a1b2c3dfeat: dry-run flag so sweep previews before it deletes
  • 9f3e1a7fix: keep branches with an open PR even when they look stale
  • 7c0d2b5refactor: extract branch-age scoring into its own module
Boost writes
XXCopy

Shipped a dry-run mode for Sweep 🧹 It shows exactly which stale git branches it'll delete before touching anything. Single Rust binary → sweep.dev

Boost

You pushed 9 commits and told no one. Let’s fix that.

the feed

What builders are shipping

See the whole feed

meherullah97

@meherullah97 · shipping quick-memorial-web

X

Just shipped a B2B owner console with memorial analytics and billing. Plus fixed blog SEO. Building in public for funeral home software. 🚀

Jul 21 0 cheers

meherullah97

@meherullah97 · shipping quick-memorial-web

LinkedIn

Over the past few weeks, I've been building out a B2B feature for Quick Memorial Web — a platform that lets funeral homes (brokers) create and manage memorial pages for their clients. Here's what went down. Phase 0 was the foundation: auth, membership, RLS policies, and a script to provision a test broker org. I needed to make sure brokers could sign up, log in via magic link, and have their users scoped to the right organization. Phase 1 shipped the broker dashboard with a guarded stub, a session helper, and the ability to list an organization's memorials. The dashboard now shows brokers which memorials they own. Phase 2 added the ability to create memorials — auto-premium, live, and permanent — from a new form. I extracted shared display helpers (isLiveMemorial, memorialLifeSpan) to keep the dashboard and the new public directory consistent. And the latest: a public broker directory at /b/<slug>. Now anyone can browse a funeral home's memorials without logging in. The directory reuses those same display helpers. Why this matters: most memorial sites lock content behind login walls. I wanted brokers to have a shareable, public presence that feels professional and drives engagement. The directory is simple — just a slug-based URL — but it's the kind of feature that makes a platform sticky. Next up: analytics and maybe a way for families to contribute photos. Let me know what you think!

Jul 8 0 cheers

meherullah97

@meherullah97 · shipping seorankslab

Reddit

**SeoRanksLab: Open-source SEO toolkit now fully free, just shipped key fixes and features** I've been building SeoRanksLab, an open-source SEO analytics platform. This week I merged several fixes and features that might interest folks dealing with Google Search Console and SEO tooling. **Key changes:** - Fixed audit page crash for 'sc-domain' GSC properties (the www redirect check doesn't apply there) - Made migration 009 idempotent (drop policy if exists) – no more failed migrations on re-runs - Removed hardcoded API key from CrUX audit, switched to keyless POST endpoint (security win) - Added product roadmap: rank tracking, content briefs, MCP server, audit, portfolio - Added 'This Week' card with effort tags and 'What Moved' wins – focused on solo founder needs - Free SEO tools hub: CTR by position, striking distance, CTR audit - Removed pricing page – now fully free and open source **What I learned:** Never hardcode API keys. Even in early stages, it's a bad habit. The keyless POST endpoint for CrUX is cleaner and more secure. The sc-domain fix was subtle: Google Search Console properties set to 'sc-domain' don't have a www/non-www distinction, so the redirect check was crashing. Easy fix once I understood the data model. **Looking for feedback:** - Anyone else run into sc-domain gotchas? - What SEO tools would you like to see next? Repo: https://github.com/raj-khan/seorankslab

Jul 1 0 cheers

without a hype buddy

Great work, shipped into the void

  • You forget to share what you build
  • When you try, you stare at a blank tweet box
  • No idea which sites are even worth posting to

with BuildBoost

Every commit becomes momentum

  • Boost turns your commits into ready-to-post copy
  • A nudge when you go quiet, a streak when you don’t
  • A curated directory of where to actually post

how it works

From commit to posted in three steps

  1. 01

    Connect GitHub

    One click. We read your commit history to understand what you shipped, never your secrets.

  2. 02

    Boost reads your commits

    An LLM summarizes what you actually built this week and finds the story worth telling.

  3. 03

    Copy, paste, post

    Pick a platform and language, copy the draft, and share it. You stay in control. Nothing posts itself.

everything in the box

Built for shippers who hate marketing

Post generator

Turn this week’s commits into platform-ready posts for X, LinkedIn, Reddit, Hacker News, and Dev.to.

Any language

Draft in English, Bahasa Indonesia, Español, and more. Reach the community you’re actually in.

Your hype buddy

Encouragement that’s specific to what you shipped, plus a clear nudge on what to do next.

Where-to-post directory

A curated list of sites and communities, with notes on audience and effort for each one.

Reminder checklist

A short pre-post checklist so every share lands: demo gif, clear link, replies ready.

Public shipping feed

Get discovered. Every post you share shows up in the feed of builders shipping in public.