Building Flux

Why Flux exists

FFlux team.June 10, 2026.4 min read

Flux started with a simple observation: open source work is surprisingly difficult to understand. Contributions are scattered across pull requests, repositories, issues, reviews, and discussions. The work exists, but the story behind it is often invisible.

For contributors, this creates a frustrating problem. Years of learning, problem solving, and collaboration can be reduced to a GitHub profile filled with activity that lacks context. The effort is visible, but the impact is not.

The visibility problem

Most open source contributors are not trying to collect contribution counts. They are fixing bugs, improving systems, helping maintainers, and gradually building expertise in specific domains. Yet when someone views their profile, much of that work remains hidden behind repositories and pull requests that require significant effort to understand.

Recruiters face the same challenge from the opposite direction. They can see repositories and contribution graphs, but understanding what a contributor actually did often requires opening dozens of pull requests and piecing together a story manually.

Open source is more than activity

Many existing tools focus on measuring activity. They count commits, pull requests, repositories, and contribution streaks. While those metrics can be useful, they rarely explain what kind of work a contributor is known for or where they have developed expertise.

A contributor who spends months improving a workflow engine and a contributor who makes dozens of small unrelated changes can appear surprisingly similar when viewed through activity metrics alone. The difference lies in context, ownership, and impact.

Building credibility through context

Flux was designed around the idea that credibility is not created by numbers. Credibility is built through repeated ownership, meaningful contributions, and consistent involvement in projects over time. The goal is to make that story easier to understand.

Instead of focusing purely on activity, Flux focuses on contribution context. Which repositories matter most? What areas of a codebase has someone worked on repeatedly? Where have they demonstrated consistency? These questions reveal far more than a contribution graph ever could.

While contributing to open source myself, I kept running into the same problem. The work was visible, but the context wasn't. Pull requests, reviews, and countless hours spent understanding a codebase were scattered across repositories, making it difficult to communicate the journey behind the contributions. That experience ultimately led me to start building Flux. Kalash Thakare

Built for contributors first

Flux is not intended to replace GitHub. GitHub remains the place where work happens. Flux exists to help contributors organize that work, showcase it more effectively, and maintain visibility into the projects and areas they care about most.

The platform is being built with contributors at the center of every decision. Features are evaluated based on a simple question: does this help contributors understand, manage, or communicate their open source work more effectively?

From public OSS portfolios and contribution storytelling to repository workspaces and opportunity tracking, every part of Flux is designed around helping contributors build credibility through meaningful work rather than vanity metrics.

Still early, still evolving

Flux is still in its early stages. The product will continue to evolve through contributor feedback, real world usage, and lessons learned from building alongside the open source community. The goal is not to build another dashboard. The goal is to help contributors earn visibility for work that already deserves it.

If open source work is a journey, Flux aims to make that journey easier to understand, easier to manage, and easier to share with the people who matter.