Integrations
Read where you ship. Post where they read.
The platform has two ends: it reads what you shipped from wherever your code lives - up to five repositories under one product, each connected on the terms you pick - and it posts where the people you want to reach actually are. The middle never changes: posts built from work you really did, and nothing published until you approve it.
Source
Where your code lives
GitHub and GitLab today, three ways each: a public repository needs no credential, a webhook holds none either, and a read-only token can be revoked in a click. You decide per repository.
The middle
What you actually shipped
Every claim traced to a commit or a ship note. Nothing invented, and nothing at all in a week you did not ship.
Destination
Where your audience reads
LinkedIn first, because that is where founders and customers already are. Every draft waits for your approval before it gets there.
Available connections.
No repository
Ship notes connect nothing.
Plenty of shipped work never touches a codebase: a pricing change, a rewritten onboarding email, a doc. Write one line about it and it grounds a post exactly as a commit does - the pipeline never learns which kind of evidence it started from. A founder with no repository at all connects nothing and writes ship notes instead.
More on the habit in ship notes: what to write down when the work was not a commit.
On the way.
These are not built yet, so there is nothing to read about them. When one works, it moves up.
- GitHub to X
- GitLab to X
- GitHub to Meta
- GitLab to Meta
Ask for an invite.
The platform is in private beta. Everything above works for founders who are in; tell us what you are building and invites go out in batches.