Sandboxed execution
Every vibe runs in a sandboxed iframe so experiments stay isolated while still feeling instant and shareable.
Where your code
becomes playable.
Vibecodr is a social runtime where people publish runnable web apps instead of static posts. Build, share, and remix interactive experiences in a sandboxed environment designed for vibecoders.
Why it works
Why vibecode projects live better in a Social Runtime
Social by default
Follow creators, remix projects, and see what the community is building. A true social network for coders.
AI Development ready
Add Pulses for server-side inference, secrets, or automation so AI Development workflows ship with real backends.
Remixable artifacts
Publish creates immutable artifacts with lineage, so vibecoding stays traceable and collaborative.
Explore
Dive deeper into Vibecodr
Studio
Build and publish in-browser
Pulses
Serverless automation for vibes
Discover
Browse remixable projects
Use cases
See what vibecoding unlocks
How it works
Understand the runtime
Plans
Compare limits and tiers
Cloudflare Workers guide
Programmatic KV, D1, R2 access
Power of Pulses
Capability matrix & features
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?
Yes. Vibes run in a sandboxed iframe, and Pulses handle backend work like secrets, webhooks, and storage. The separation keeps user code isolated.
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.
Who is Vibecodr for?
Vibecodr is a coding social network for coders who want to ship runnable demos, remixable experiments, and vibecoding prototypes without setup overhead.