About
One developer, ten platforms, one identity.
DevIdentity turns the work you've scattered across the internet into a single, credible, self-updating portfolio.
The problem
Your real work lives everywhere — repositories on GitHub, notebooks on Kaggle, models on Hugging Face, solved problems on LeetCode, papers on arXiv and Google Scholar. But when a recruiter or collaborator wants to understand what you can actually do, there’s no single place that tells the whole story. A résumé flattens it. A GitHub profile shows only a slice. The signal is real; it’s just scattered.
What DevIdentity does
DevIdentity connects to the platforms you already use, pulls in your public work, and uses AI to turn it into one polished portfolio that updates itself as you keep building. It reads the substance of your projects — not just star counts — to surface technical depth, growth over time, and the kind of engineer you are. The result is a shareable identity page at /u/<username> that stays current without you maintaining it by hand.
It also gives the other side of the table something honest to work with. The Judge Consolelets a recruiter check how a candidate’s real work aligns with a job description, and verify code authenticity through fork provenance and commit-authorship — evidence-based, never guesswork.
Who's behind it
DevIdentity is built by Abu Ahmad, a developer based in Dhaka, Bangladesh. It started from a simple frustration: the work was there, the proof was there, but there was no good way to show it as one coherent thing. So I built the tool I wished I had — and I’m still building it in the open, shipping improvements continuously.
If you have feedback, a bug, or an idea, I genuinely want to hear it. Reach me on the contact page or any of the social links below.
Where it’s going
More platforms, deeper AI analysis, and better tools for both developers presenting their work and the people evaluating it. The goal stays the same: make it effortless to prove what you’ve actually done.