MyVibe: Ship Your Vibe-Coded Apps in One Command

You just spent twenty minutes describing your app idea to Claude. The AI understood exactly what you wanted. It generated a working React app, complete with state management, responsive design, and even some slick animations. You ran it locally, made a few tweaks, and now you're staring at something you actually want to use.Now what?This is where most vibe-coded projects go to die. The gap between "it works on my machine" and "here's a link you can click" has killed more side projects than scope creep and burnout combined. You start googling deployment options, comparing pricing tiers, configuring build pipelines, and somewhere around minute forty-five of wrestling with environment variables, you close your laptop and do something else.MyVibe exists to delete that gap entirely.## What Vibe Coding Actually ProducesBefore we talk about deployment, let's be clear about what we're deploying. Vibe coding—the practice of describing what you want to an AI and having it generate working code—typically produces one of three things:**Static HTML/CSS/JS bundles.** Single-page apps, landing pages, interactive tools, data visualizations. No server required, just files that need to be accessible via HTTP.**Client-side React/Vue/Svelte apps.** More sophisticated single-page applications that build down to static assets. These might fetch data from external APIs, but the app itself is static.**Full-stack applications.** Apps with their own backend logic, databases, authentication. These need actual server infrastructure.MyVibe handles the first two categories with zero configuration. You have files. MyVibe puts them on the internet. That's it.## The Publish CommandHere's the entire deployment workflow:```bashmyvibe publish ./my-app```That command does the following:1. Detects what kind of project you have (static files, React build output, etc.)2. Packages everything into a deployable bundle3. Uploads it to MyVibe's infrastructure4. Returns a live URLNo account creation flow. No credit card. No YAML files. No build configuration. No DNS settings. No SSL certificate management.The first time you run it, you'll authenticate via a browser redirect. After that, it just works.## Real Scenarios Where This Matters### The Demo That Needs to Exist in Ten MinutesYou're preparing for a meeting. You need to show a concept, not explain it. You vibe-code a quick prototype—maybe an interactive diagram, a pricing calculator, or a mock dashboard. The AI generates it. You run it locally. It's good enough.```bashmyvibe publish ./pricing-calculator# => https://pricing-calculator-a3f7.myvibe.me```You paste that link into Slack. Done. Your colleagues can click it from their phones, their tablets, their ancient work laptops. No "let me share my screen" required.### The Tool You Built For YourselfYou wrote a little utility. Maybe it converts between file formats. Maybe it generates placeholder data. Maybe it's a specialized calculator for something niche. You use it constantly on your own machine.Then a coworker asks if they can use it too. Then someone in another department. Then someone external.With traditional hosting, you'd need to think about authentication, rate limiting, terms of service, monitoring. With MyVibe, you just publish it. If it gets popular, that's a nice problem to have later. Right now, you're just unblocking someone.### The Portfolio PieceYou're learning a new framework. You followed a tutorial, then deviated, then built something that actually demonstrates what you can do. It's not a production app—it's a proof that you understand how things fit together.```bashmyvibe publish ./portfolio-project --name my-first-svelte-app# => https://my-first-svelte-app.myvibe.me```That URL goes on your resume. That URL goes in your GitHub README. That URL is something a hiring manager can actually click instead of reading your description of what it would look like if they cloned the repo and ran it.## How It Handles Different Project TypesMyVibe inspects your directory and makes reasonable decisions.**Plain HTML:** If it finds an `index.html` at the root, it serves that directly. CSS, JS, images, and other assets are served from their relative paths.**React (Create React App, Vite):** If it finds a `build` or `dist` directory with static assets, it serves from there. If it finds a `package.json` with a build script and no build output, it runs the build first.```bash# MyVibe detects this is a Vite project and builds itmyvibe publish ./my-vite-app# Or publish pre-built output directlynpm run buildmyvibe publish ./dist```**Single HTML file with embedded assets:** Sometimes vibe coding produces a single self-contained HTML file with inline CSS and JavaScript. MyVibe handles this fine—one file is still a valid website.**ZIP archives:** Already have a bundled archive? Publish it directly.```bashmyvibe publish ./site-export.zip```## What You GetEvery published project receives:**A persistent URL.** The format is `https://{name}-{hash}.myvibe.me` or just `https://{name}.myvibe.me` if you specify a name that's available. URLs don't expire. They don't get recycled. A link you share today will work in six months.**HTTPS by default.** No certificate management. No mixed content warnings. No "your connection is not private" screens scaring away visitors.**Global CDN distribution.** Your files are served from edge locations worldwide. A user in Tokyo gets fast load times even if you published from Toronto.**No cold starts.** Static hosting means static performance. There's no container spinning up, no serverless function initializing. The first request is as fast as the hundredth.## What You Don't Get (And Why That's Fine)MyVibe is deliberately limited. It hosts static assets. It doesn't run your backend code. It doesn't give you a database. It doesn't handle authentication.This isn't a missing feature—it's the point.The moment a hosting platform offers backends, databases, and auth, it also offers configuration for those things. Environment variables. Connection strings. Secret management. Build hooks. Deploy previews. Rollback strategies. Monitoring dashboards.These features are valuable when you need them. They're friction when you don't.Most vibe-coded projects don't need them. They're front-ends that call external APIs. They're self-contained tools. They're demos. They're experiments. They're "I wonder if this would work" made tangible.For those projects, MyVibe's answer to "how do I configure the database?" is "you don't have one." And that's a feature.## When to Use Something ElseBe clear-eyed about what MyVibe is for. It's not your production infrastructure for a business-critical application. It's not where you host customer data. It's not a replacement for proper DevOps when proper DevOps is warranted.If you need:- Server-side code execution- Persistent data storage- User authentication- Custom domains with your branding- SLAs and support contractsThen you need a different tool. There are many good options. MyVibe isn't competing with them—it's serving a different use case entirely.## The Workflow That Actually HappensHere's what vibe coding looks like when deployment isn't a barrier:**9:00 AM:** You have an idea for a tool that would help with your actual job.**9:15 AM:** You've described it to Claude. It generated a first version. You're running it locally.**9:30 AM:** You've iterated twice. The third version is actually useful.**9:31 AM:** You run `myvibe publish ./tool`.**9:32 AM:** You share the URL with your team.**10:00 AM:** Three people are using it. Someone found a bug.**10:15 AM:** You fix the bug. You run `myvibe publish ./tool` again. The URL updates.**10:16 AM:** The bug is fixed for everyone.This loop—idea to feedback in under an hour—changes what you're willing to build. Projects that would never have justified the setup cost become trivial to attempt. "I could build that" becomes "I did build that, here's the link."## Getting StartedInstall the CLI:```bashnpm install -g @anthropic/myvibe```Publish something:```bashmyvibe publish ./your-project```That's genuinely it. There's no step three.The first publish takes a few seconds to authenticate. Subsequent publishes are near-instant for small projects—you're just uploading files.If you want to see what's deployed:```bashmyvibe list```If you want to take something down:```bashmyvibe unpublish {project-name}```If you want to see logs or analytics—well, you don't get those. This isn't that kind of platform. It's simpler than that, on purpose.## The PointVibe coding changed how fast you can build things. It didn't change how annoying deployment was.MyVibe fixes that mismatch. It treats deployment as the trivial operation it should be for static web projects. No decisions required. No infrastructure to understand. No pricing tiers to compare.You built something. Now it exists on the internet. Now you can share it.That's the whole product.