The Social Runtime
For years "here's my project" meant a screenshot, a repo, and a "works on my machine." Vibecodr makes the app itself the thing people meet: build a vibe in the Studio, publish it as a runnable post, let people open and remix it in the feed, and add a Pulse only when the app needs backend power.
Studio
Write it in the browser, drop in a ZIP or a repo, or paste whatever your AI assistant wrote. Code, preview, and publish stay in one loop, so an idea becomes a working thing in minutes.
Runs as a post
The thing in the feed is not a screenshot or a repo link — it is the real app, running, on any device, for anyone. No install, no setup instructions for the people you share it with.
People press play
Scrolling turns into using. People run your app in the browser the moment they find it, and every share carries a link that opens the working app and points back to you.
Remix carries it
Anyone can fork what you made and take it somewhere new while the lineage stays visible the whole way. Ideas evolve in the open instead of getting quietly copy-pasted into the void.
What "runs as content" means
Publish once and the same running app shows up in the feed, on its own page, inside embeds, and across every version — always live, always current.
In the feed
Your app sits in the feed as the live thing itself. People try it next to everyone else's instead of clicking out to a demo that may or may not still work.
On its own page
Drop the link in a chat, a tweet, or a README and it opens the working app — no login wall, no build step, no broken 'try it live' button.
Embedded anywhere
Embed it in a blog post or a portfolio and it is still the same app, still live, still current — not a video of something that used to run.
One link, every version
Improve your app and the public URL, embeds, and history all stay intact. Older cuts stay around for rollback — one identity, many versions, no link rot.
Under the hood, for when you want it
The runtime that makes a feed of strangers' apps safe to open, the backend that shows up only when earned, and the one-artifact-everywhere guarantee are all plumbing — here when you go looking, invisible when you do not.
Safe to open
Code runs in an isolated, cross-origin sandbox that cannot reach your data, your session, or another app on the page. That isolation is the whole reason pressing play on a stranger's app is a non-event.
Backends, when earned
When a project needs secrets, a database, a scheduled job, or a call to Stripe, GitHub, or OpenAI, drop a file in src/server/ and it ships as an /api endpoint beside the app — most never need one.
One app, everywhere
Each publish becomes an immutable artifact and a live cut, so the feed, the page, and every embed all play the same current app. You never maintain a 'demo' and a 'real' version.
Follow the loop
Start in the Studio, open a runnable vibe on its public page, then trace the same app into embeds, versions, and a Pulse if it grows beyond the browser.
Your move
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
It means a web app is treated as a piece of content. Instead of a screenshot or a repo link, the post in the feed is the running app itself, and other people can open, use, and remix it right away.
No. If you can paste what an AI wrote, you can publish a working app people can run and share. And if you do code, nothing is hidden — bring a whole repo and wire up a real backend.
Yes. Every app runs in an isolated browser sandbox that cannot touch your account, your data, or anything else on the page. Making that safe is the entire point — it is what lets you press play without a second thought.
BUMP IT is how you ship an update. It publishes a new cut to the same app post, keeps the same public link and identity, and preserves the older cuts for rollback — so improving an app never breaks the link people already have.
In a Pulse. Put server code in src/server/ and it becomes a managed /api endpoint with secrets, storage, and scheduling handled for you. You only reach for it the day the project actually grows into it.