Every developer "should" have a portfolio, but building one eats a weekend you'd rather spend on real projects. So I built Porfilr — fill in your projects, link your GitHub, publish a clean portfolio in ~10 minutes. One URL for every application and recruiter DM.
Free to start; Pro is a one-time $19. Built with React/Vite, Vercel serverless functions, Supabase (Postgres/auth/storage), and Resend for email.
It's live at porfilr.com. I'd love feedback from other devs — what would you want in a portfolio builder?
Top comments (2)
Exactly why we built forg.to - instead of spending weekends building portfolios from scratch, it automatically aggregates your public work into a professional portfolio that's always up-to-date.
I remember early in my career, feeling that exact pressure to build a custom portfolio to "prove" my frontend chops. What I found was that after the initial excitement, maintaining it became just another chore, taking away from actual product development or learning new skills directly applicable to my job. The idea of skipping that cycle for something more direct definitely resonates.
For most dev roles, the portfolio's primary function is to be a clear, accessible showcase of your other projects and experience, not necessarily a demonstration of your ability to set up a CI/CD pipeline for a static site. The "build vs. buy" calculation here often leans heavily towards "buy" if your core business isn't website building. You want to spend your limited time solving interesting problems, not debugging a CSS issue on your personal site.
From a SaaS perspective, this is exactly the kind of friction that's ripe for a dedicated tool. Developers are busy, and their time is valuable. If a solution can abstract away the boilerplate and let them focus on the content – their actual work – that's a net positive. It's about leveraging specialized tools for specialized tasks, rather than reinventing the wheel for every ancillary need.