> 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.

This has always been a fear of open source development… but in reality it’s over exaggerated, thousands of FOSS ideas are posted every day…

My advice would be to treat posting your project like a launch, and get all the readme’s, docs etc ready before posting, so it has the best chance of growing an audience, which seems to be your goal.

But if you really don’t want other people to recycle your idea, then open source is not for you…

Open source but license it properly - AGPL works best if you are worried about someone making money off your idea. Honestly though with AI everything is copyable - wouldn't worry about that. Instead focus on the fastest path to get feedback and iterate

1) If it's open source, what's the incentive to steal from you anyway? It's free. That's one of the interesting moats in the age of AI.

2) If it's at risk of being stolen/copied today, it will be the same thing 10-100-1000 days from now. There is no hiding from AI copy cats. Just put it out there and find out if someone actually will want to do it. If yes, you saved yourself a bunch of time.

API security is the most common blind spot. Vibe coding tools generate endpoints fast but almost never think about broken authentication, excessive data exposure, or injection flaws. A solo dev can ship a beautiful frontend with completely exposed APIs behind it. At minimum — test your own endpoints like an attacker would before going live.

There is no way to protect your idea from being copied/stolen.

It happened a million times over, you have some brilliant idea, people start using it, and after a few months some big company puts 10-100 engineers on it and they do the same thing.

I would say that the key is to get to a big enough audience so they would rather buy you out than compete. Easier said than done :P

And the biggest question is: do you want to commit 100% of your time and money to building your company, or you would rather spend your time building new things?

If your open source code contains your technical barriers, then don't open source the code with those barriers—only open source the other parts.

If it's the other case, where you're worried about plagiarism, I actually don't think you need to be too concerned. I once saw an interview with Airbnb's founder Brian Chesky where he talked about how Airbnb also faced many imitators in its early days. These competitors grew rapidly too, but looking back, the difference between imitators and originals is that while imitators might get off to a quick start, they find it hard to persevere through difficulties like the original does in the mid-to-late stages. In the end, it's often the original who stuck with their vision that survives.

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.

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.

see also: https://ryelang.org/blog/posts/cognitive-dark-forest/

(posted on HN a couple of weeks back)

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.