19
35 Comments

I got tired of explaining myself with 5 different links, so I built this

Every time someone asked what I've built, I'd start with GitHub. They'd see a wall of repos with no context. Half abandoned. None of them making sense to someone who doesn't read code for fun. So I'd send a Product Hunt link. Then a Twitter thread. Then a Notion page I half-finished 6 months ago. By the time I was done explaining, the person had already lost interest. I was doing my own work a disservice.

The problem wasn't the projects. It was that there was no single place that told the full story of what I built, whether it's alive, and why it matters. Linktree and Bento are great but they're built for influencers. They have no concept of projects, live status, or proof that you actually ship things.

So I built IndieDeck, a link-in-bio for everything you ship. Also, I put together a demo page so you can see exactly what it looks like in practice
https://www.indiedeck.page/mehsssi

I'm still early and would genuinely love feedback from people here, you're exactly who I built this for.

posted toAvatar for product IndieDeck
IndieDeck
  1. 2

    Nice I can relate I have github projects that are 10+ years old and some in GitHub others in GitLab and even some in Code Commit (yea that was a thing)

    1. 1

      CodeCommit 💀 that's a deep cut right there. 10 years of projects scattered across three platforms, that's exactly the kind of chaos IndieDeck was made for. One page, everything in one place, regardless of where the code actually lives.

  2. 2

    It looks very cool, and the idea is very useful. I think you also need to add “ status was not implemented.” During the last 10 years, I had a lot of ideas. I noted them, imagined features, thought about marketing struggles, or developed limitations (my own), and postponed them. Sometimes, I started to develop but, released maybe 1 or two. Now I've pushed myself to release at least one small product, and I've found that I still hate the marketing phase. I love to develop, imagine, and implement features and test them. But when the product is done, I'm like, “Okay, I'm also done with this.” Someone asked me how many projects my cemetery has. I said maybe 6, but then when I started to remind them, I counted at least 11, so I'm sure I can find more. It's upsetting, but it shows the lesson: we must continue to do what we like and fight against what we don’t need.

    1. 2

      11 projects in the cemetery, that hit close to home for a lot of us honestly. 😅

      The "Not Implemented" status idea is really interesting. There's something powerful about owning your abandoned ideas publicly instead of hiding them. It actually shows the full journey of a builder, not just the wins.

      Adding that to the roadmap. And the marketing struggle you mentioned is real that's partly why I built IndieDeck. The page does a lot of the passive marketing work for you just by existing and showing what you're building.

      Thanks for sharing this, genuinely one of the most thoughtful comments so far.🙏
      Good luck man !

      1. 1

        I registered and want to share my small feedback, just because I appreciate any feedback for my products. I hope mine will be useful.

        1. Your premium description has the 1st place - "Everything in Free plan". But for me, as a new user, it is not clear what is in the free plan.

        2. I can’t find how to set a logo to a project. I saw them in your demo. Maybe it’s a premium feature, but this is not mentioned in that list

        3. Landing of my profile page. If a project doesn't have a logo, there is just a broken image. I would say some placeholder (the logo of IndieDeck or anything else) will improve ui

        4. This form, "Follow my journey Get notified when I ship" has an email input. The hint in it in dark mode uses dark text color.

        In general, everything is on a good level. It was easy for me to register, fill in the info, and create a project.

        1. 1

          Alex thank you so much for taking the time, genuinely useful stuff

          1. Free plan wording: you're right it's confusing. "Everything in Free plan" means Pro includes all free features plus more. Going to reword that to make it clearer.

          2. Project logo: they're actually fetched automatically from the URL you provide! If it's not working for your project let me know which URL you used and I'll check it.

          3. Broken images: totally valid. Adding a default IndieDeck fallback icon for edge cases where favicon fails to load. Fixing right away.

          4. Dark mode email input: great catch. Dark text on dark background is a CSS bug. Fixing today.

          Really appreciate you registering and sharing this. This is exactly what makes the product better 🙏

            1. 1

              what's this? your product ? explain pls in one line.

      2. 1

        Thanks. Good luck to you, too. I think I'll use your service and at least add my current project.

        1. 1

          That means a lot, welcome aboard! Would love to see your page once it's live, Alex

    2. 1

      hey alex, excited to share that we just shipped 3 new features on IndieDeck (one of them was your suggestion 👀)
      Here's what shipped:

      1. Build Log: a public timeline of your builder journey. Launches, milestones, updates, archived projects. Visitors can upvote and comment directly on each entry. The goal was to turn a static page into a living story. It's live and working.

      2. GitHub Stars: paste your repo URL and your star count auto syncs and shows on your project card with a verified badge. One API call, zero manual work.

      3. Verified MRR: connect Stripe and your real MRR shows on your page. No fake numbers. Cryptographically verified.

        pricing is at its lowest right now, doubling in 24 hours.
        → claim your indiedeck.page today !

  3. 1

    Nice idea. A single link that explains everything can save a lot of time. Did you build it mainly for personal use or are you planning to turn it into a product?

    1. 1

      Thanks! Both honestly, started as something I needed myself, but it's very much a product now.

      Live at indiedeck.page, free to start. Would love for you to try it 🙏

  4. 1

    I really relate to what you said about being early and wanting feedback from people here.

    I’m also in the very early stages of an idea I’ve had for years. It’s still mostly a vision in my mind right now, but being here and reading posts like this gives me hope that one day it might become a real MVP.

    It’s encouraging to see builders creating tools that help people tell the story behind what they’re building.

    Wishing you success with IndieDeck — and thanks for sharing the journey.

    1. 2

      This means a lot honestly. Everyone starts with just a vision, the gap between idea and MVP is mostly just showing up consistently.

      Ship something small, get it in front of people, and let the feedback pull you forward. That's the whole game.

      Good luck with yours, hope to see it on an IndieDeck page one day 😄

  5. 1

    “Something I’ve noticed: two startups with similar traction can get completely different reactions from investors depending on how the founder is perceived publicly.

    Does anyone intentionally work on their authority/credibility as a founder?”

    1. 2

      Yes, and it's something most builders underestimate until it's too late.

      The credibility gap usually comes down to one thing: how quickly someone can understand who you are and what you've built. If that takes more than 10 seconds, you've already lost them.

      That's actually one of the reason why I built IndieDeck. one page that shows everything you've shipped, your active projects, and lets people subscribe to follow your journey. It doesn't replace deep credibility but it removes the friction of explaining yourself every single time.

      Public presence is a slow game but the compounding is real !

  6. 1

    The gap between "what I built" and "what someone else understands I built" is genuinely underrated as a problem.

    GitHub makes sense to builders. Nobody else. And by the time you've assembled four different links into a coherent story, you've already lost the room.

    Checking out the demo now. Does it support projects that are still in trial/early access, or is it more portfolio-style?

    1. 3

      Totally, GitHub is builder language, not human language. That gap is exactly what IndieDeck tries to close.
      And yes, fully supports early access and trial projects. You can add any link waitlist page, landing page, beta signup and set the status to "In Progress." You're not forced to only show finished work. Some of the most interesting pages will probably be makers showing what they're building right now, not just what they've shipped.

  7. 1

    Having one link that explains everything you’re building is underrated. Once you start sharing projects publicly, context switching between multiple links gets messy fast.

    Curious if this is mostly being used as a founder profile or more like a lightweight product landing page.

    1. 1

      Both honestly and that tension is interesting. Right now most people are using it as a founder profile. One page that shows everything they've shipped, their status, and lets visitors subscribe to follow their journey.

      But I can see it naturally becoming a lightweight product landing page too, especially for makers with one main project they want to push. The status badges and subscriber capture already do a lot of that work.

      Curious which use case you'd personally find more valuable?

      1. 1

        I like the idea of it evolving between the two. A founder profile that naturally doubles as a landing page feels pretty powerful, especially for indie builders who are constantly shipping new things.

        Instead of rebuilding a new landing page for every project, it becomes more like a living hub that shows what you're working on right now.

        I’m curious if over time it leans more toward “follow the builder” or “discover the product.” Both feel valuable but slightly different audiences.

        1. 1

          "Living hub" is exactly the framing I had in my head when building this, really glad that came through.

          On your question, I think both audiences exist and honestly the product serves both right now. But if I had to bet, "follow the builder" wins long term. Products come and go but people who consistently ship build real audiences.

          The most valuable IndieDeck pages will probably belong to makers where you don't just want to use their product , you want to see what they build next.

          1. 1

            I think that’s a really interesting point about the audience forming around the builder rather than any single product.

            It reminds me a bit of how people follow certain indie hackers or open-source maintainers — the trust builds over time because they consistently ship thoughtful work. At that point the individual projects almost become chapters in a longer story.

            If IndieDeck ends up highlighting that trajectory — showing what someone built before, what they’re building now, and what they launch next — it could turn those pages into something closer to a builder timeline rather than just a project profile.

            Curious if you’ve thought about that direction at all: making the page feel more like a “build log” of a maker rather than a static product page?

            1. 1

              "Build log of a maker" haha that's already on the roadmap curtis.

              The static project profile is just the starting point. As makers keep updating their status, shipping new things, and adding context over time, the page starts telling a much richer story automatically.

              The chapter analogy is spot on too. Each project isn't just a link, it's a moment in someone's builder journey. That's the kind of thing that makes people want to follow a maker, not just bookmark a tool.

              Really appreciate you thinking this deeply about it Curtis 🙏

              1. 1

                That’s a great way to frame it. Once projects start showing the story behind the work, it becomes much more interesting than just a list of links.

                The “moment in a builder’s journey” idea is powerful — people tend to follow the process and evolution, not just the finished product. Curious to see how the build log aspect evolves as makers start adding updates over time.

                1. 1

                  Exactly, people follow builders not just products. The process, the pivots, the decisions along the way are often more interesting than the finished thing.

                  The build log will be the feature that unlocks that. Once makers start logging updates over time the page stops being a snapshot and starts being a story. Really excited to see how that evolves with real users.

                  1. 1

                    That’s a really strong point — especially the shift from “project page” to “living narrative.”

                    What’s interesting is that once a build log becomes consistent, it almost turns into a lightweight form of distribution too. Each update isn’t just documentation, it’s a touchpoint for people to re-engage, follow along, and feel invested in the outcome.

                    I think the real unlock will be when builders stop thinking of updates as “extra work” and start seeing them as part of the product itself — almost like shipping progress, not just features.

                    Curious if you’re planning to keep the updates more raw and frequent, or more curated and milestone-based?

                    1. 1

                      "Shipping progress, not just features", that's exactly the framing I've been looking for honestly. Saving that.

                      On your question, I think both have a place but for different types of makers. Raw and frequent works for builders who are deeply in the process and want to bring their audience along in real time. Milestone based works better for makers who want a cleaner narrative around their work.

                      The goal with Build Log is to make both feel natural without forcing either. You shouldn't have to think about whether an update is "worth posting." If it moved the product forward in any way. ship it. Let the audience decide what resonates.

                      The re-engagement angle you mentioned is what excites me most though. An update isn't just documentation, it's a reason for someone to come back, comment, and feel invested. That's the loop I'm trying to build.
                      And good news ! Build Log is already live on IndieDeck. You can start documenting your journey right now at indiedeck.page 🙏

  8. 1

    This is amazing.. Great job....

    1. 1

      Thanks man !

  9. 1

    Looks good, works good! Well done, you should be proud.

    I created my page at /astarrh

    I would like to see is indicators of which fields are required and which ones aren't when putting information into forms. It took me a few tries to realize that I could just leave the URL field blank when posting a project.

    I could see myself paying for this if it had some community features. Being able to post under a project and interact with potential users of all of my projects in one place could be pretty useful.

    1. 1

      Hey, really appreciate you trying it out and creating your page! 🤠

      Great catch on the required fields, that's exactly the kind of friction I want to eliminate. Adding indicators is going on the list right now.

      The community feature idea is really interesting. Hadn't thought about project-level interaction but it makes a lot of sense, especially for makers who want direct feedback from potential users. I'll think about how that could work.

      Thanks for the honest feedback, this is exactly what I needed to hear at this stage

  10. 1

    Good job bro. It's honestly fire

    1. 1

      Heyy thanks bro