FAQ

Questions, answered.

How the platform turns what you ship into posts - and what to expect.

What is PeerPost?

It is a content-marketing autopilot for founders who ship. It turns your real commits into LinkedIn posts that market your product, so you can build in public without stopping to write them yourself.

How does it work?

Connect your repositories once. As you ship, the platform reads what changed, drafts a post grounded in it, and hands the draft to you. Nothing is published until you approve it.

Does PeerPost work with GitHub and GitLab?

Both, and in three ways. A public repository needs no credential at all. A webhook sends only the pushes you configure and holds no credential either, so it cannot read your code. A read-only token reads the one branch you name and can be revoked at any time. It only ever reads; it cannot push, comment, or change anything in your repository.

Can I connect more than one repository?

Up to five per product, each connected on its own terms. A backend, a web app and a mobile client are one product to the people reading about it, so the platform writes one post about the release rather than one post per repository. Your internal repository names never appear in the post.

What if the work was not a commit?

Write a ship note: one line about what you shipped. A ship note is evidence exactly like a commit is, so a founder with no repository at all can still use it, and work that never touched a codebase still gets written about.

What does it write about?

Only what you shipped. Every post is built from your real commits and ship notes, so it reflects features and fixes that genuinely exist. It never invents a product milestone.

What if I haven't shipped anything worth posting?

It stays quiet. Instead of fabricating a post to fill a schedule, it produces nothing until there is real work to share. Staying quiet beats making things up.

Will the posts sound like generic AI?

No. Because each post is grounded in your actual work rather than a generic prompt, it reads like a founder sharing what they built - not an AI guessing about your industry.

Can PeerPost post without me?

No, and not as a setting you could switch on. Approval before publishing is built into the product: there is no auto-publish mode to enable. You see every draft before anyone else does.

Do I have to write or edit anything?

No writing required. Posts arrive already drafted, and you approve one in seconds. Edit it first if you want to; skip it and nothing goes out.

When do posts arrive?

When you have shipped something worth writing about, not on a fixed day. Each post belongs to a window you can see in the calendar before it opens, so you know what is queued and what already went out. A window with no evidence in it rolls forward rather than producing a post.

What happens if I disconnect a repository?

The next post is written from whatever is still connected, and nothing else changes. Evidence belongs to the product rather than to the source it arrived through, so your history, your published posts and your ship notes all survive - including if you delete the product entirely. Starting over is not the same as asking us to forget what you published.

Which platforms does it post to?

LinkedIn first. Support for Meta, X, and more is on the way.

Who is PeerPost for?

Founders and builders who ship real product but have no time to market it - especially technical founders who would rather write code than write posts. Ship notes mean you do not need a repository to use it.

How much does it cost?

Pricing is set inside the product, and everyone in the private beta sees the current plans in their console. It is not published here yet because it is still moving.

How do I get access?

The platform is in private beta and access is by invite. Request one from the homepage, tell us what you are building, and invites go out in batches.

Want the specifics for your platform? See GitHub to LinkedIn or GitLab to LinkedIn.

Ready to try it? Request an invite.