How Vibecodr Works
You don't ship a stack on Vibecodr — you ship the thing itself. Drop in code you wrote, code you imported, or code an AI just generated, and it becomes a real app anyone can open and use in one click.
No install. No servers to babysit. No deploy ritual. Publish once and your project is a living app on its own page: ready to share, open to remix, and able to grow a real backend the day it actually needs one.
It is the same handful of beats every time, and you can stop after any of them: bring code, watch it run, share it, let people remix it, and add a backend only if the project grows into one.
01 — Bring code
Type it in the Studio, drop in a ZIP or a GitHub repo, or paste whatever your AI assistant wrote. HTML, a React component, a static site, a whole project — Vibecodr figures out how to run it. There is nothing to configure before you start.
02 — It runs for real
Publishing makes your project a working app on its own page that opens instantly, on any device, for anyone. No 'works on my machine,' no broken links, no setup instructions for the people you share it with.
03 — Share anywhere
Post it to the feed, drop it in a chat, or embed it on your own site. People press play and use the real thing right in the browser, and every share carries your name with it.
04 — Remix is the default
Others can fork what you made, take it somewhere new, and the lineage stays visible the whole way. Ideas evolve in the open instead of getting quietly copy-pasted into the void.
None of this is required reading. But when a project grows up, the machinery is already waiting: real backends, hard isolation, clean versioning, and one app that shows up everywhere.
Backends, when earned
When a project needs secrets, a database, a scheduled job, or a call out to Stripe, GitHub, or OpenAI, drop a file in src/server/ and it deploys as an /api endpoint on managed edge infrastructure. You write the function; Vibecodr runs, scales, and secures it.
Safe to open
Code executes 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.
Versions, not link rot
Improve your app and the public URL, embeds, and history all stay intact. Older cuts stay around for rollback. One identity, many versions, no fragmentation.
One app, everywhere
You never maintain a 'demo' and a 'real' version. The same app shows up in feeds, on its own page, and inside embeds — always live, always current.
Jump into the Studio, see what people are building, or go as deep as the docs allow.
Short answers for the places where marketing copy should stop hand-waving and say the plain thing.
No. If you can paste what an AI wrote, you can publish a working app and share it. And if you do code, nothing is hidden from you — bring a whole repo and wire up a real backend.
Nowhere you have to manage. There are no servers to rent, no deploy step, and no dashboard to configure. Vibecodr runs your app on managed edge infrastructure the moment you publish.
Add 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 when the project actually needs it.
They get their own copy to build on, and the link back to your original stays visible. You keep the credit, and the idea keeps moving forward.
Yes. Every app runs in an isolated 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.