--- title: How vibe coding works on Vibecodr | Paste, run, share, remix description: How vibe coding works on Vibecodr: paste, upload, or generate code and it runs as a real app anyone can open in one click — then share it, let vibecoders remix it, and add a backend only when the project earns one. canonical: https://vibecodr.space/how-it-works --- # How Vibecodr Works ## Paste it. It runs. Share it. Remix it. 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. ## Start here ### 01 — Bring code: Paste, upload, or generate. If it runs in a browser, it runs here. 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: One click turns code into a live app, not a screenshot. 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: A link that opens a working app, and points back to you. 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: Anyone can build on your app, and the credit stays attached. 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. ## How it works in practice ### Backends, when earned: Add a Pulse and your app gets a real backend, with no servers to run. 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: Every app runs sealed off from your account and everyone else's. 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: BUMP IT ships the next cut to the same page and link. 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: The thing people discover is the thing that runs. 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. ## Keep exploring - [Start building: Open the Studio](https://vibecodr.space/studio) - [Add a backend: The power of Pulses](https://vibecodr.space/power-of-pulses/index.md) - [Get inspired: What people build](https://vibecodr.space/use-cases/index.md) - [Go deeper: Read the docs](https://vibecodr.space/docs/index.md) ## FAQ ### Do I need to know how to code? 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. ### Where does my app run? Do I have to host or deploy anything? 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. ### What if my app needs a backend, secrets, or a database? 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. ### What happens when someone remixes my app? 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. ### Is it safe to open an app a stranger made? 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. ## Closing note The short version: bring your code, get a living app people can open and remix, and add a backend only when the project earns one. Everything underneath — hosting, scaling, isolation, versioning — is plumbing we handle so you can stay in the part that's fun.