Private beta · building now

Every commit becomes content.

You're already shipping. Turn each commit into a post and grow an audience while you build.

Connects to GitHub in 30sYour voiceYou approve every post
github.com/you/project
main
commit a7f3b21
src/theme/ThemeProvider.tsx+427
x.com/youbuilding
live
Y
you, building in public
@youbuilding · posted 2s ago
3 hours on a toggle animation. The actual system detection? ~15 lines of code. Priorities.
💬 24🔁 112847
listening for commits…
followers
1,847+8

You know this feeling. I know this feeling.

01
Great product. Zero users.
// the usual
02
Launch day. All that work. Silence.
// brutal
03
Self-promotion feels gross. It shows.
// fair
04
Posting is inconsistent because shipping is the job.
// every dev
05
The builders who post daily quietly pull ahead.
// noticed
06
Burnout from doing both — badly.
// been there

Three steps. Zero new habits.

Step 01
a7f3c12ee84dnew
You push code.
Connect your GitHub once. Every commit on tracked repos becomes raw material. We listen in the background. You don't change a thing.
Step 02
– tone: honest, dev– angle: struggle → win– hook: "4h debugging..."→ draft ready
We draft the post.
Your commit message, diff, and repo context get turned into a post in your voice. Not generic AI output — honest, developer-native writing with a hook.
Step 03
♥ 847 · 🔁 112
You ship it.
Approve with one tap, schedule for peak hours, or let it auto-post. Your audience grows while you keep building.
// a note from the founder
Jacob

Hey! It's Jacob

(the builder behind buildinpublic.now)

last year i shipped seven side projects back-to-back. nights, weekends, holidays. the code worked. the products were good. and every single one of them launched to nothing.

the problem wasn't the product. the problem was that nobody knew i existed. i'd spent months heads-down in a terminal and forgotten that building and being seen are two different jobs.

so i tried to post more. i was bad at it. i'd stare at a blank tweet box after a 10-hour coding session and just… close the tab. writing a post about the thing i'd just shipped felt like a whole second job on top of the first one.

then it clicked. i was already writing about the work every time i committed. the commit messages, the diffs, the late-night "fix: finally figured out why this was breaking" — that's the story. it just wasn't getting out.

so i built buildinpublic.now — the tool i wished existed. it reads your commits and turns them into posts in your voice. you approve them, they go out, your audience grows while you keep shipping.

Cheaper than the silence.

Solo
$0forever
For the curious. Connect one repo, see the magic.
  • 1 connected repo
  • 5 drafts per month
  • Manual approval only
  • Post to X
Start free
Studio
$49/month
For teams and multi-brand founders.
  • Everything in Builder
  • Up to 5 team members
  • Multi-brand voice profiles
  • Thread generation
  • Analytics + best-time-to-post
Join waitlist

The honest answers.

No. We train a voice profile on your past tweets, repo READMEs, and commit history. Every draft is edited-to-approve, not auto-spammed. If it sounds like a LinkedIn bot, delete it — we won't be hurt.
Your choice. Manual approval is the default. Once you trust the voice, you can enable auto-post with a 30-minute "undo" window, or tag specific commit patterns (like feat:) to auto-ship.
We only read commit messages and diff summaries — never raw source code. You pick which repos to connect, and you can exclude files or branches. Everything is encrypted in transit and at rest.
X on day one. LinkedIn and Bluesky on launch. Threads and Farcaster are on the roadmap. You can cross-post or customise each platform's tone.
Most are. That's the point. We find the angle — a 4-hour bug hunt becomes a story, a config tweak becomes a lesson, a feature ship becomes a milestone. Boring commits, interesting posts.
We're onboarding in waves. Waitlist signups get access in 2–3 weeks and lock in 50% off the first year.
© 2026 buildinpublic.now
made while shipping · not instead of