--- title: About Vibecodr | The home for vibe coding description: Why Vibecodr exists: a home for vibe coding where public work is runnable. Paste or generate code, ship it as a real app, and let vibecoders open and remix it — no install, no servers, no screenshots. canonical: https://vibecodr.space/about --- # Why Vibecodr Exists ## Public work should be runnable. Vibecodr is a place to play with code and ship it — where the odd tools, tiny games, visual experiments, and half-serious ideas make more sense because someone can actually open them. Not a pitch deck for software, the software itself, live at a link. Paste, upload, or generate code; watch it run as a real app; share it and let people remix it; and add a backend only the day the project earns one. That loop is the whole product — everything underneath is plumbing we handle so you can stay in the part that's fun. ## Start here ### 01 — Runnable, not described: Software is easier to understand when you can open it. A screenshot, a repo link, or a long explanation all ask people to imagine the thing. Vibecodr exists so 'here, try this' opens the real, working app in one click — on any device, with nothing to install — and the idea gets to speak for itself. ### 02 — A place to play: The best stuff starts as a toy you weren't sure would work. Paste what an AI wrote, drop in a sketch, or bring a whole repo. Nothing has to be finished or serious to deserve a public home. Small experiments are the point, not a warm-up for the real product — some stay toys, and some quietly grow up. ### 03 — Sharing is the feature: Public work should travel as the thing itself. Every app gets its own page and a link that opens the live app — in the feed, in a chat, or embedded on your own site. People press play and use it, every share carries your name, and anyone can remix it with the credit staying attached the whole way. ### 04 — Earn the backend: Start in the browser. Add a backend only when the project asks. A project can stay a browser-side app for as long as that is enough. The day it needs secrets, a database, a scheduled job, or a call out to another service, add a Pulse — server code that deploys with the project. You reach for it when the work earns it, and never before. ### 05 — Safe to open: Openness only works when the boundaries are real. Every app runs in an isolated, cross-origin sandbox that cannot touch your account, your data, or anything else on the page. That isolation is the whole reason pressing play on a stranger's app is a non-event — and why a place this open can also feel safe. ## How it works in practice ### Make: Build in the Studio, from a snippet or a whole repo. The making stays close to the publishing. Edit, preview, and shape the post without turning a first draft into an infrastructure errand. ### Ship: Publish once and it's a real app on its own page. No servers to rent, no deploy ritual, no 'works on my machine.' The moment you publish, the working app is live for anyone to open. ### Remix: Let people build on your work without erasing the trail. Others fork what you made and take it somewhere new, and the lineage stays visible. Ideas evolve in the open instead of getting quietly copy-pasted away. ### Keep evolving: BUMP IT ships the next cut to the same page and link. The project keeps one public identity as it grows. Links, embeds, and history stay intact, older cuts stick around, and the people following it just see it get better. ## Keep exploring - [The loop: How it works](https://vibecodr.space/how-it-works/index.md) - [Trust model: Security model](https://vibecodr.space/security/index.md) - [What people build: Use cases](https://vibecodr.space/use-cases/index.md) - [Plans: Plans](https://vibecodr.space/plans/index.md) ## FAQ ### Is Vibecodr only for frontend experiments? No. Browser-side apps are the easiest place to begin, but a project can grow into a backed app when it needs secrets, schedules, webhooks, or other trusted server work. You add that with a Pulse only when the project earns it. ### Do I need to install anything or know how to code? No. The default path is browser-first, so you can open published work immediately and publish your own by pasting what an AI wrote. And if you do code, nothing is hidden — bring a whole repo and wire up a real backend. ### Why make such a point of keeping one canonical app? Because a project should be able to grow without losing its audience, links, embeds, history, or remix context every time a new version ships. BUMP IT keeps it one living thing instead of a graveyard of near-identical URLs. ### How does Vibecodr keep things both open and safe? By letting browser-side code be easy to open while keeping trusted backend capability in a separate Pulse plane, with explicit rules around secrets, routing, storage, and outbound calls. Open to play with, sealed where it counts. ## Closing note Vibecodr.Space is the official home of Vibecodr, the social runtime for runnable web apps. It is for the moment when 'here, try this' should open the work itself instead of a screenshot, a repo link, or a long explanation of what it might become. Built by a solo founder who believes everyone should have a place to ship code.