
A social space for runnable code where creative coding becomes a community
What makes Vibecodr special is that it treats code like something you can actually experience, not something you scroll past. Most places force you into screenshots, repos, or “link in bio.” On Vibecodr, the post is the app. You publish a vibe and anyone can run it instantly, react to it, remix it, and learn from it by changing real working code, not by reading a thread. I built it because I got tired of how hard it is to deploy tiny projects, and how lonely it feels to build without a community unless you already have an audience. Vibecodr is my attempt to bring back that playful “try this thing I made” part of the internet, but with safety boundaries and a social layer built around interaction and craft, not engagement farming. And for the people who want more than front-end experiments, the platform has real power behind it. Vibes run in a locked-down embed runtime with security rules that are treated as first-class, not an afterthought. If you need secrets or server-side logic, you can attach a Pulse, which is a dedicated Cloudflare Worker deployed per project, the same underlying tech Vibecodr itself runs on. Pulses exist so you can do the “real app” stuff (webhooks, API calls, automation) without ever putting secrets in the browser, without weird duct tape, and without a gap between what you built and what you can safely ship.
No comments yet. Start the conversation!