What builders are shipping

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

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!

**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

# BuildBoost: Public Shipping Feed & AI Post Generation I've been working on BuildBoost, a tool that helps indie developers who can code but struggle to promote their work. The idea is simple: connect your GitHub repo, and we generate social media posts from your recent commits. ## What's new ### Public Shipping Feed I added a Supabase-backed public feed that shows recent commits from all users. It's like a mini build-in-public timeline. Each commit shows the repo, message, and timestamp. This makes it easy for others to discover what you're working on. ### DeepSeek AI Post Generation Now when you select a repo, we use DeepSeek to generate a post about the latest commits. The prompt is designed to sound human and specific, avoiding corporate jargon. You can then edit and post to X or LinkedIn. ### Improved Auth Flow I fixed the GitHub OAuth flow so the admin client is used internally for `storeGithubToken`, and the callback redirect is smoother. Also fixed a bug where the authenticated client wasn't passed to satisfy RLS policies. ## Tech Stack - Next.js (App Router) - Supabase (auth, database, RLS) - GitHub OAuth & REST API - DeepSeek API - Excalidraw for planning snapshots ## How it works 1. Sign in with GitHub 2. Select a repo 3. See recent commits 4. Click "Generate Post" – AI writes a draft 5. Edit and share ## Future plans - Scheduled posting - Multi-platform support - Analytics on post performance Check out the repo: [github.com/aaronmyatt/build-boost](https://github.com/aaronmyatt/build-boost) Feedback welcome!

Show HN: BuildBoost – Turn your GitHub commits into social posts BuildBoost is a tool that helps indie developers promote their work by automatically generating social media posts from recent commits. It uses DeepSeek for AI copywriting and Supabase for storage with RLS. New in this update: - Public shipping feed showing everyone's recent builds - AI post generation from selected repos - Smoother GitHub OAuth flow Built with Next.js, Supabase, GitHub REST API. Open source at github.com/aaronmyatt/build-boost. Would love your thoughts on the approach – do AI-generated posts feel too generic? How do you handle promotion?

**BuildBoost just got a public shipping feed + AI post generation** I've been building BuildBoost, a tool that turns your GitHub commits into social media posts for indie devs who want to build in public but hate the promo grind. Recent updates: - Public shipping feed: shows recent commits from all users, stored in Supabase - DeepSeek integration: pick a repo, get a generated post - Improved GitHub OAuth flow with proper client handling - Visual plan snapshots synced via Excalidraw Would love feedback on the feed UX and if the AI posts feel authentic enough. Repo: github.com/aaronmyatt/build-boost

I've been working on BuildBoost, a tool that helps indie devs promote their work by generating social posts from their GitHub commits. The latest update adds a public shipping feed powered by Supabase, so anyone can see what projects are being built in public. We also integrated DeepSeek for AI post generation from selected repos. The stack is Next.js, Supabase, and GitHub OAuth. Check it out at buildboost.app.

Just shipped a public shipping feed for @buildboost. Now you can see every commit and promo move your fave indie devs are making. Built with Supabase + GitHub OAuth. #buildinpublic

# How I stopped fearing `git branch -D` I had close to 40 dead branches in one repo and kept avoiding them because deleting the wrong one is a bad afternoon. So I built **Sweep**: it scores every branch by age and activity, previews what it would delete with a dry run, and refuses to touch anything with an open PR. Here's how the scoring works, and what I learned shipping it as a single Rust binary…