youvibe.dev
Watch it built. Remix it. Ship your own
Think of it as YouTube for the things people build. Watch what other people vibe-coded, hit remix to get your own copy running, and ship it from the code editor in your browser. Already built something? Upload it and it gets the same page.
Every thumbnail is a working app, not a video of one.
Home, subscriptions, a search bar and a grid of thumbnails. Except every thumbnail is a working app: open it, read the code that made it, and hit remix to get your own copy running.
Lecture → Notes
Build it in the browser, or bring one you already made.
Open a tab and you are in a working project: real files, a real database, real model calls, and a preview that updates as you type. Or skip all that and push up something you built elsewhere.
// api/cover.js · runs on youvibe hostingimport { db, models } from "@youvibe/sdk";export async function POST(req) { const { mood } = await req.json(); const art = await models.image( `album cover, ${mood}, film grain, 1974` ); await db.covers.insert({ mood, url: art.url }); return Response.json({ cover: art.url });}
Cover Machine
mood: "rainy sunday" → 1.8s
Illustration of the in-app editor. Files, database, models and deploys in one tab.
Build it here
The code editor runs in the browser, so there is nothing to install and nothing to configure. Pair with a model or write every line yourself, then publish straight to a live URL.
- No terminal, no setup, no local environment
- Database, file storage and API keys attached from the first line
- Every model in the catalogue, callable in two lines
Upload what you already made
Bring a project you built anywhere, in any stack. Connect a repository or drop a folder in, and it gets the same page in the same feed as everything else.
- Keep your own editor, your own toolchain, your own workflow
- Same likes, comments, shares and remix button as a build made here
- Host it with us, or point the page at where it already lives
Every kind of model, wired into the editor.
Browse by what you want done, not by who made it. Pick a model, call it in two lines, swap it for another mid-project without rewriting anything. The labs behind them are listed further down.
Reading, writing, reasoning
Making and understanding pictures
Anything you'd rather hear or say
Moving pictures
Things with volume
The unglamorous, useful ones
Logos are the property of their respective owners and are used with permission. Availability depends on each provider’s terms, and the list moves as the field does.
Request any model from inside the app and we'll look at adding it. The catalogue grows from what people actually ask for, not from what we guessed they'd want.
Request a modelEverything between the idea and the link.
Most projects die between "it runs locally" and "here, try it". youvibe removes that gap.
Post it and people turn up
Publish a project and it lands in the feed next to everyone else’s. Likes, comments and remix counts sit in the open, so decent work travels without you having to sell it.
Build it online
The code editor runs in the browser, so there is nothing to install and nothing to configure. Pair with a model or write every line by hand. Every remix opens as a working copy, not a zip file.
Hosting, database, APIs. Handled.
Hit publish and it's live on a youvibe URL. A database, file storage and API keys come with the project, so a weekend build survives contact with real users.
Models on tap
Frontier models and open-source ones, side by side, inside the editor. Speech, image and video models too. If the one you need isn't there, request it.
Never written a line, or been shipping for a decade.
Same site, same tools, two very different starting points. Nobody gets talked down to and nobody gets held back.
You've never coded. Start anyway.
Describe what you want in plain English and watch it appear. You don't need to know what a terminal is, what to install, or where the code goes. It's already running.
- Start from someone else's finished project and change one thing
- The model writes it, then explains what it wrote, line by line
- Nothing to set up, nothing to break, nothing to pay for while you learn
- If it goes wrong, roll back to the last version that worked
"I made a website for my nan's cake business on a Tuesday. I still don't know what React is."
You know what you're doing. Skip the setup.
Real files, real version history, your own dependencies, and a database you can actually query. Bring the model in when it saves time and turn it off when it doesn't.
- Swap models per task, or write every line yourself
- Server routes, migrations, environment variables and logs
- Fork any public project and read exactly how it was built
- Ship to a live URL without touching a deploy config
"Prototyped the whole thing on the train. It was in front of users before I got home."
The part that keeps you here.
Got an idea? That's the only prerequisite.
No signup to think about today. Just know it's being built.
COMING SOONyouvibe.dev · 2026
284 comments
@danj · 2 days ago
Remixed this to do meeting notes instead. Took ten minutes and I have never written a line of Python in my life.
41@ade · 1 day ago
The way it timestamps each section is better than the app I actually pay for. What model are you calling for the transcript?
28