getfolio.dev

I'm a frontend developer based in Nice, France, with about 5 years of experience. For most of those years, my portfolio was either embarrassingly outdated or just didn't exist.

I knew I wasn't alone. Every developer I talked to had the same story: "Yeah, I really need to update my portfolio." Nobody ever does. Because after a full day of writing code, the absolute last thing you want is to open another project and manually copy-paste your latest repos.

The irony hit me: the work is already done. It's all sitting on GitHub. So I started building getfolio.dev.

What it does

Connect your GitHub, claim a username, get a live portfolio at getfolio.dev/username in under two minutes. Your pinned repos, contribution graph, language breakdown, stars — all pulled in automatically and refreshed daily. Pick from 5 developer-focused themes (Terminal, DarkPro, Glass, Minimal, Editorial), customize with a drag-and-drop editor with live preview, and publish.

Pro adds custom domains, blog sync from Dev.to/Hashnode, analytics, and testimonials for €9/month.

What I've learned building this as a solo indie dev

1. Solve your own problem first, validate second. I didn't start with market research. I started because I was tired of my own broken portfolio. Turns out, when you solve a problem you deeply understand, the product decisions become obvious. Every feature I've built started with "I wish I had this."

2. The "magic moment" is everything. For getfolio.dev, it's the instant your GitHub data populates a beautiful theme. That feeling of "wait, that's MY portfolio?" in the first 30 seconds. I've redesigned the onboarding three times to make sure that moment hits as fast as possible. If your users don't feel the value before they've had time to get distracted, you've lost them.

3. Scope is the real enemy, not competition. I have a Notion board with 30+ feature ideas. "Open to work" toggle, PDF export, team plans, explore page, referral system... I had to learn to say no repeatedly. Ship the thing that matters, get real users, then iterate. The hardest part of being a solo dev isn't coding — it's deciding what NOT to build.

4. Your tech stack doesn't matter (until it does). I went with Next.js, Firebase, Stripe, Vercel. Familiar tools, fast iteration. Some people would argue I should've gone with Supabase or built my own auth. Maybe. But I'm shipping, and that matters more than architecture debates. Pick what you know, move fast, refactor later.

5. Marketing as a developer is uncomfortable — and necessary. I've spent more time writing LinkedIn posts and DEV.to articles than I expected. Building in public, sharing progress, creating a waitlist with email nurturing. None of it comes naturally to a dev who'd rather be in the code. But nobody will use a product they don't know about. The code is maybe 60% of the work. The other 40% is making sure humans find out it exists.

6. Pricing is a feature, not an afterthought. I went back and forth on pricing for weeks. Free forever? Freemium? One-time payment? I landed on a generous free tier (full portfolio, 3 pinned projects) with Pro at €9/month unlocking the power features. The logic: let developers see value instantly for free, then earn the upgrade when they want to go further. Early waitlist subscribers get a permanent 30% discount — scarcity that's real, not manufactured.

Where I am now

Pre-launch, building the waitlist, polishing the last rough edges. Solo developer, bootstrapped, no funding. The goal is straightforward: help developers have a portfolio that actually reflects their current work without any maintenance.

If you're a developer who's been meaning to update your portfolio for the last six months — you're my target user. I'd love your feedback.

getfolio.dev