How it works

Proof of Work, explained.

Merged Network builds professional profiles from publicly available technical activity — nothing more.

01Public data only

What we read from GitHub

When a developer connects GitHub, we read their public profile: public repositories, primary languages, repository topics, stars and public contribution activity. That data becomes the foundation of their Proof of Work profile.

02Data ethics

What we never touch

We only analyze publicly available technical data. We never expose private repositories or private code without explicit authorization. No source code is stored, resold or shared, and developers control what appears on their public profile at any time.

03Matching

Evidence-based matching

There are no arbitrary developer scores and no opaque match percentages. When a profile appears for a search, we show the evidence behind it — for example: matches required stack, 8 public Python repositories. You judge the work yourself.

04Signal processing

How activity becomes useful context

Repository languages, topics, recency and public contribution patterns are normalized into readable technical signals. We preserve the underlying evidence so every claim can be inspected instead of reducing a person to a rank.

Based on publicly available technical activity.