Built by a developer, for developers.

I got tired of writing the same README updates. Every time I shipped something, the docs fell behind. And let's be honest — nobody reads them anyway, because everyone already knows they're wrong.

Most documentation tools ask you to write manually, maintain separately, and hope you remember to update them. That's not sustainable. Docs should be a byproduct of shipping, not a second job.

Pushpen started as a weekend project: a webhook that reads your diff and writes your docs for you. No prompts, no copying, no manual updates. Just push code, get docs.

If you've ever closed a PR and thought "I should update the README" but didn't — this is for you.

After watching the same pattern play out on team after team — pristine docs at kickoff, stale docs within months, weeks lost onboarding new hires into documentation that lied to them — it became clear the problem was structural, not a matter of discipline. Code changes continuously; documentation only changes when a human remembers. That gap is where every stale README lives.

The insight behind Pushpen is simple: if documentation updates on every push, the gap never opens. So instead of asking developers to write docs, Pushpen ties documentation to the one event that always happens when code changes — the push — and delivers updates as pull requests you review and merge. We wrote about the thinking in detail in why developer documentation goes outdated and how to automate your GitHub documentation.

Pushpen is built by David Kubgak. For now, that's the whole team — a solo founder shipping in public. That means every decision is made by someone who uses the product daily and feels the same documentation pain you do. It also means feedback reaches the person who can act on it directly.