Vibes
A vibe is the thing you can actually open, play with, tweak, remix, and share on Vibecodr. Not a screenshot. Not a code snippet. The real app — attached to a post, running right in the browser, one click away for anyone.
01 — You open it
Every vibe is attached to a post, and that post is the real thing running — a tool, a toy, a game, a demo. Anyone can open it in one click and start using it. No install, no waitlist, no cloning a repo to run it locally.
02 — It runs right there
The thing people open is the thing that runs. It opens instantly on a phone or a laptop, it works the same for a stranger as it does for you, and it stays current — there is no demo version drifting away from a real one.
03 — It travels with you
A vibe moves across the feed, its own player page, profiles, and embeds on other sites without turning into a different thing each time. Wherever it lands it is still one app people can open, revisit, and follow — and your name rides along.
04 — It is yours to remix
The object people open is the same one they can remix. Take someone's vibe somewhere new, publish your take, and the lineage back to the original stays visible. A vibe that sparks something keeps living through its remixes instead of stalling as one frozen copy.
What a vibe actually is
A vibe behaves like real software people can touch — the same object across every surface, alive the moment it loads, and built from the start to be passed around.
01 — You open it
Every vibe is attached to a post, and that post is the real thing running — a tool, a toy, a game, a demo. Anyone can open it in one click and start using it. No install, no waitlist, no cloning a repo to run it locally.
02 — It runs right there
The thing people open is the thing that runs. It opens instantly on a phone or a laptop, it works the same for a stranger as it does for you, and it stays current — there is no demo version drifting away from a real one.
03 — It travels with you
A vibe moves across the feed, its own player page, profiles, and embeds on other sites without turning into a different thing each time. Wherever it lands it is still one app people can open, revisit, and follow — and your name rides along.
04 — It is yours to remix
The object people open is the same one they can remix. Take someone's vibe somewhere new, publish your take, and the lineage back to the original stays visible. A vibe that sparks something keeps living through its remixes instead of stalling as one frozen copy.
Where vibes show up
Because a vibe is attached to a post, it can appear in the feed, get its own full-screen player, resurface from discovery and profiles, and travel into embeds — always the same runnable thing.
Feed
A vibe lives on a post, so it appears in the feed as something you can run on the spot — not a demo stranded on its own island.
Player
Open a vibe in the player and it is the whole window: the focused place to actually run it, poke at it, and tune it with params.
Discover + profiles
Pull a vibe up from discovery or a creator's profile and it is still the same recognizable project — and still fully runnable when you open it.
Embeds
Carry a vibe into an embed on your own page and it stays self-contained and runnable — the real app, not a picture of it.
Where the line is
Being clear about what a vibe doesn't do by itself is what keeps the product honest: secrets, databases, and trusted work live in a Pulse, not in the page. When a vibe and a Pulse run together, that is a Combo.
Safe to open
A vibe runs in an isolated, cross-origin sandbox that cannot reach your session, your data, or another app on the page. That isolation is the whole reason pressing play on a stranger's vibe is a non-event.
No secrets in the browser
On its own a vibe does not hold API keys or talk to a database — that is deliberate. Keeping credentials out of the page is what lets anyone read it, run it, and remix it without ever seeing something they should not.
Backends, when earned
The day your project needs a secret, a database, a scheduled job, or a call to Stripe, GitHub, or OpenAI, drop a file in src/server/ and it ships as a managed backend beside the app. Reach for it only when the project earns it.
Keep exploring
Open a vibe in the feed, build your own in the Studio, or read how a project grows a Pulse the day it needs trusted backend work.
Your move
Bring an idea, a snippet, or a whole project into the Studio and publish a vibe people can run in the next minute. Add a Pulse the day it needs a real backend.
FAQ
No. The thing people open runs in the browser. Publishing boots it in a protected playback environment on its own host, while any real server-side work lives in a Pulse instead.
No. On its own a vibe cannot reach secrets, a database, storage, or platform cookies. Trusted work goes through a Pulse, where credentials stay on the server side and never touch the page.
Yes — remixing is a first-class part of the product. A vibe is built to be opened, tweaked, remixed, and published into your own version, with the link back to the original kept visible.
Use BUMP IT to ship the next version of the same vibe. Vibecodr makes a new cut, moves the live app on the same public link forward, and keeps older cuts around for rollback or pinned embeds.
Yes. Start with the client-side vibe, then add a Pulse the day you need trusted backend work — a secret, a database, a scheduled job. A project with both a vibe and a Pulse is a Combo.