Listings, recorded activity and review outcomes. These counts describe the directory, not how many visitors your product will receive. Activity scores are historical measurements, not the homepage discovery order.
The three tiers are not three grades. 23 tracked builders carry a live streak off 1.3k qualifying ships, read from public GitHub activity they never handed over, and they hold a rank on it like anyone else. Verified is the same board with the private half of the work added: connect an account and repositories nobody can see start feeding the same streak.
Every ship event belongs to a product. A streak on its own is just a number going up. What it buys you is people landing on the page where your work is.
The share of approved builders who have handed over read access to at least one account. The board itself does not wait on it. Streaks and cadence come out of activity that was already public, so rows appear here whether or not anybody connects. What connecting adds is the unseen half of the work: private repositories, and the project that only goes public on launch day. This number is the one that says how many people want to be here rather than merely appearing here.
The share of verified builders still holding a streak of four weeks or more. Four weeks is where a habit either takes or it doesn’t. Signups and page views spike whenever someone links to us; this is the one number that says whether people keep shipping after the novelty wears off. If everybody stalls at week three, this place is doing nothing for the people in it.
| Platform | Builders | Connected | Status | Reason |
|---|---|---|---|---|
| GitHub High activity · Free API | 195 | 00% | Measured | Pushes, releases and merged PRs, in real time via webhook. The artifact of building, not a post about it. |
| Reddit High activity · Free tier | 1 | 00% | Measured | r/SideProject, r/SaaS, r/EntrepreneurRideAlong. High intent, and a post history shows in seconds whether someone actually ships. The Data API has a free rate-limited tier that is ample at this scale; sustained commercial use needs a paid agreement, so confirm the current terms before relying on it. |
| Blog Medium activity · Free API | 19 | 00% | Measured | Any feed URL, polled hourly. Devlogs and build reports. |
| Newsletter Medium activity · Free API | 0 | 00% | Measured | Feed-based, same as a blog. Issue cadence counts as shipping. |
| YouTube Medium activity · Free API | 3 | 00% | Measured | Devlogs and demos. Public stats need no authorisation. |
| Mastodon Medium activity · Free API | 55 | 00% | Measured | Public tagged posts can be read from the founder’s own server. |
| Bluesky Medium activity · Free API | 21 | 00% | Measured | Public tagged posts can be read without asking for account access. |
| X High activity · Paid API only | 1528 | — | Link only | The cultural home of building in public — and the API costs a few hundred a month for metrics we can live without. Linked as proof, never scored. |
| LinkedIn High activity · No API | 48 | — | Link only | Large and growing for B2B and no-code builders. No practical creator-post API exists. Linked as proof, never scored. |
| Indie Hackers Medium activity · No API | 0 | — | Link only | The dedicated home for this behaviour. No API. Linked as proof. |
| Instagram Low activity · Free API | 7 | 00% | Measured | A real "day 47" genre exists here, but it skews toward audience-building about building. Supported, not prioritised — insights need a Professional account and App Review. |
| TikTok Low activity · Free API | 0 | 00% | Measured | Same shape as Instagram. Supported, not prioritised. |
| Website Low activity · No API | 102 | — | Link only | Linked for context. |
| showhn | 28 | 0 | Link only | Held on builder profiles but not listed in the platform table, so nothing from it reaches a score. |
Measured means ship events arrive with their own timestamps, either through a read-only connection or, on GitHub, from the public event feed that asks nobody for permission. The Connected column counts only the first kind, which is why a platform can carry more builders than connections. Link only means the handle is displayed and clickable and nothing else — no connect button is offered, because there is nothing to connect to. GitHub is measured for ships but carries no audience figure, so it never feeds engagement or growth; those are read from the connected non-GitHub account with the largest audience, and omitted entirely when there is none.
The cultural home of building in public — and the API costs a few hundred a month for metrics we can live without. Linked as proof, never scored.
Large and growing for B2B and no-code builders. No practical creator-post API exists. Linked as proof, never scored.
The dedicated home for this behaviour. No API. Linked as proof.
Linked for context.
MRR, revenue, user counts, follower screenshots, “we hit 10k”. If we cannot fetch it from an account the builder connected, it never becomes a number anywhere on this site.
These are not oversights waiting on a sprint. The first ones are the platforms where building in public is busiest and the API access is worst, and we would rather leave a hole than fill it with an estimate printed in the same typeface as a measurement. Where a component cannot be measured for a builder, their profile says so instead of showing a zero — see the methodology.