Studio
Code, preview, and publish stay in one loop.
Build in-browser, watch it update live, and ship without leaving the same workspace.
The Social Runtime
Publish runnable web apps. Let people play them instantly.
Vibecodr is the community where code runs as content. Build a vibe in Studio, publish it to vibecodr.space, let people open it in the feed or on its own page, carry the same vibe onto other sites with embeds, and add Pulses when the app needs backend power.
Vibes
vibecodr.space is where people actually open the work.
Every publish becomes a runnable vibe people can open in the feed or on its own page.
Distribution
Embeds and premium vxbe.space links extend the same vibe.
Carry the same work onto another site, or point a premium link at the version you want people to see first.
Control
BUMP IT, cuts, and Pulses give the project more range without making day one feel heavy.
You can pin one exact artifact, move the live Drop forward when the next release is ready, roll back without drama, or add backend help only when the app actually grows into it.
Published surfaces
Everything around the first publish is already there.
The idea is simple: make something in Studio, publish it so people can open it right away, then keep following the same project as it spreads, evolves, and gets more capable.
Public surfaces
People discover the project on vibecodr.space. The runnable part gets its own room.
That way the public page can stay welcoming and readable, while the published artifact boots in its own protected playback space behind the scenes.
Embeds + vanity links
Carry the same vibe onto another site or route a premium vxbe.space link.
External embeds can stay first-party, blocked, or allowlisted, and premium links can point to a vibe, post, or Pulse.
Cuts
Ship live, pin an exact cut, and roll back without snapping the story in half.
Live embeds can follow the newest Drop, pinned embeds can stay fixed to one artifact, and every BUMP IT or revert becomes another cut in the same visible history.
Playback lane
Published playback stays steady even while the platform keeps getting better.
Public launches prefer mirrored artifact manifests and bundles, exact dependencies stay pinned, and older legacy artifacts can quietly heal forward in the background instead of dragging old runtime layouts around forever.
Pulses
Add backend logic only when the work needs it.
Use Pulses for encrypted secrets, OAuth, cron triggers, and edge-backed behavior without making the first build heavy.
See the whole loop
The easiest way to understand Vibecodr is to follow a project from build to share.
Start in Studio, open the public vibe on vibecodr.space, then follow the same build into embeds, premium links, and Pulses if the project grows beyond the browser.
Build
Studio
Write HTML, CSS, and JS with live preview and publish from the same place.
Browse
Discover
Open runnable vibes in the feed, on profile pages, or on permanent public URLs.
Understand
How it works
See how public pages, embeds, cuts, and sandboxed runtime surfaces connect.
Extend
Pulses
Add backend power for secrets, cron, AI inference, and edge-backed workflows.
Infrastructure
Cloudflare Workers guide
Understand how the runtime leans on KV, D1, R2, and Workers-powered execution.
Capability map
Power of Pulses
Compare what ships in a vibe versus what gets unlocked when a Pulse joins the stack.
Bottom line
Start with a vibe. Add Pulses when the app needs backend power.
If your project is better experienced than described, Vibecodr is trying to give it the right home: easy to open, easy to share, and still able to grow up when it earns that complexity.
FAQ
Questions? We've got answers.
What does Social Runtime mean?
Social Runtime is Vibecodr's way of describing a feed of runnable web apps. You build something, publish it, and other vibecoders can run and remix it immediately.
Is Vibecodr a sandbox?
The browser side is, yes, but that is only part of the picture. The vibe runs in a locked-down playback environment, the public page stays separate, and Pulses take care of the private backend work. That split is what lets Vibecodr stay playful without handing user code the keys to the platform.
How does AI Development fit in?
AI Development projects can use Pulses for server-side inference, workflows, and integrations while the vibe handles the interactive UI.
What is BUMP IT?
BUMP IT is Vibecodr's update flow for an existing app. It publishes a new cut on the same canonical app post, keeps the same public identity, and preserves rollback history.
Who is Vibecodr for?
It is for people who like making little web things, interactive demos, weird tools, games, experiments, and app ideas they want other people to actually open instead of just skim past.