playable now
Open a vibe
Posts on Vibecodr are runnable web apps, not screenshots.
Vibecodr
Fresh Arrivals
New runnable work from the community.
Fresh Arrivals
New work from the community
Tip: click any card to run instantly
remix trail
Follow the branch
Remix lineage stays attached as ideas change hands.
make your cut
Publish the next version
Start in Studio, ship a public post, and keep playing.
source context
See what changed
community thread
Talk around the work
backend when needed
Add a Pulse later
Vibecodr is a community for runnable code
Where creative coding becomes a social space.
Vibecodr is a social platform for runnable web apps: not screenshots, not repo links, not "here's my" code. Real vibes you can play instantly, remix into your own version, and discuss with people who actually ship.
Play the thing. Trace the remix lineage. Publish your own version when the idea starts pulling at you.
How it works
Play it. Remix it. Publish the next branch.
The homepage should explain the loop quickly, then get out of the way.
01
Play instantly
Open the post and run the web app immediately. No clone, no install, no setup tax before the first impression.
02
Remix with attribution
Branch the idea into your own vibe while keeping the lineage visible. Remix culture is a product feature here, not an afterthought.
03
Publish as a real post
Turn the project into a public player page that people can revisit, discuss, and share as a living thing.
When backend work shows up
Pulses when backend work shows up
Keep the homepage focused on runnable posts first. When a vibe needs secrets, schedules, webhooks, or external APIs, that is where Pulses come in. Learn Pulses
Public paths
Follow the crawlable parts of the place.
Vibecodr's public surface is not only a JavaScript app. There are readable paths for runnable web apps, creative coding, docs, the journal, public conversations, and player pages so search engines and no-JS readers can understand what is here.
Why Vibecodr exists
Sharing working code got harder than writing it. To show off a tiny animation, toy tool, or half-finished experiment, you can end up trapped in build pipelines, hosting steps, and production ceremony before anyone touches the thing.
Vibecodr makes the shareable unit small again. A vibe is fast to publish, fast to play, and easy to remix. The social layer stays attached to the actual runnable work instead of orbiting around screenshots, repo links, and disconnected commentary.
If you miss the old build-in-public web, this is for that moment: post the runnable thing, let people feel it, and let the next branch start from there.
FAQ
Is Vibecodr a no-code builder?
No. You write real code. Vibecodr is about making that code runnable, shareable, and remixable - with community feedback built in.
Do I need JavaScript enabled?
For playing and editing vibes: yes. But this page is intentionally readable without JavaScript, and you can still browse links and understand the product.
What is a Pulse?
A Pulse is serverless edge logic deployed from src/server/ (or server/). Each file maps to /api/* so your vibe stays interactive while the trusted backend work stays separate.