LeanVibe

That’s true. Launching with multiple languages is relatively easy. What I’m trying to do is translate the user-generated content on the platform as well, which makes it a bit more challenging.

We don’t really see this as a directory. It’s closer to a community, a forum, or even a small social space.

When a lot of free or pre-revenue projects gather in one place, discovery tends to happen naturally. Otherwise, most directories just become SEO tools where builders drop their links and move on.

If you’re building something useful and want real feedback before adding pricing, feel free to participate. I wrote a bit more about why getting early users at this stage matters in the linked post.

I built a platform LeanVibe.io and I'm now curating promising pre-revenue products

I contacted you via email!

Mee too. You're doing right thing

That's so true. Can you tell me about your project?

I’ve found many useful tools here. Privacy really matters these days. A lot of products send user data to their servers, and we don’t always know how that data might be used. So I genuinely appreciate the idea of keeping everything client-side.

That said, I noticed you’ve put quite a bit of effort into blocking source view or browser inspection. I’d suggest reconsidering that. If everything truly runs in the browser, it would actually build more trust to let people verify that. Anyone can open the network tab and confirm that no data is being sent to a server.

I understand the concern about people copying your work. But realistically, with vibe coding, most of these tools can be rebuilt fairly quickly anyway. Trying to prevent copying at the browser level usually doesn’t add much protection.

Instead of focusing on blocking inspection, I’d suggest focusing on growing your user base and competing on quality. If you’re worried about code copying, lightweight obfuscation is probably a more practical solution than trying to disable developer tools.