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.

Join the waitlist See how it works

Connects to GitHub in 30sYour voiceYou approve every post

github.com/you/project

main

commit a7f3b21

▋

src/theme/ThemeProvider.tsx+42−7

x.com/youbuilding

live

you, building in public

@youbuilding · posted 2s ago

3 hours on a toggle animation. The actual system detection? ~15 lines of code. Priorities.

💬 24🔁 112♥ 847

listening for commits…

followers

1,847+8

The loop

You know this feeling. I know this feeling.

Great product. Zero users.

// the usual

Launch day. All that work. Silence.

// brutal

Self-promotion feels gross. It shows.

// fair

Posting is inconsistent because shipping is the job.

// every dev

The builders who post daily quietly pull ahead.

// noticed

Burnout from doing both — badly.

// been there

How it works

Three steps. Zero new habits.

Step 01

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

We draft the post.

Your commit message, diff, and repo context get turned into a post in your voice. Not generic AI slop — honest, developer-native writing with a hook.

Step 03

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

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.

Join Now

Pricing

Cheaper than the silence.

Solo

$0forever

For the curious. Connect one repo, see the magic.

1 connected repo
5 drafts/month
5 regenerations/month

Get started free

The honest answers.

No. We train a voice profile on your past tweets 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.

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.

Currently the posts are written for X and have to be manually copied and posted but we are working on adding auto post and other platforms as you read this :).

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.