HACKER Q&A
📣 langs

How do solo devs protect their work in the age of vibe coding?


I am working on a new open-source project. (My project is in AI infrastructure. It already gets SOTA results on several well-known benchmarks.) The core value is not just the code, but a fairly specific algorithmic approach that came out of many failed attempts, experiments, and design iterations.

The dilemma I am facing is this:

If I open-source early, I get feedback, trust, users, and maybe contributors. But I also expose the core design and algorithm. With LLMs, turning a repo into a different implementation is much cheaper than it used to be.

If I keep it closed, I protect the work for longer, but I also lose the main advantages of OSS: adoption, review, community, and credibility. Worse, someone else may still build something similar and become the default project in the space.

I’m a new solo dev with almost no audience. If a large org or a well-known developer sees the idea and ships a similar implementation, they can get more attention immediately than I can get in months. And in the end I get nothing for open-sourcing my project.

How would you handle this as a solo dev?


  👤 anigbrowl Accepted Answer ✓
Vibe litigation

Seriously, I think you should just do it closed source and pursue adoption by other channels. If people ask you why it's not open source, say you're not ready to manage it yet.


👤 bigyabai
Is your project a vibe-coded application? It sounds like you're insecure about someone copying your idea, which will could happen regardless of licensing if anyone has access to Claude Code and a description of your product.

If your primary motivation to use an Open Source license is gaining trust and users, you're just going to be disappointed.


👤 shivang2607
If you are building something which can be vibe-coded easily then it ofc people will create it. You can copyright a product but you can't copyright an Idea.

Selling things online was an idea by Amazon, now everyone sells online.

If you really want people not to copy your idea then make something which cannot be easily vibe-coded or copied easily i.e. which require serious skills.