The gap between creating something with AI and sharing it with the world has always been frustrating. You prompt Claude or ChatGPT to build a landing page, get clean HTML back, then spend an hour wrestling with hosting providers, DNS settings, and build configurations. By the time it's live, the creative momentum is gone.
MyVibe eliminates that friction entirely. It's a publishing layer built specifically for vibe-coded projects—the apps, sites, and tools that emerge from conversations with AI. No Git repositories, no build pipelines, no infrastructure decisions. Just your creation and a URL.
What Actually Happens When You Publish#
When you push a project to MyVibe, the platform handles several things you'd normally configure manually:
- Asset optimization: Images are compressed, CSS is minified, and JavaScript is bundled automatically
- CDN distribution: Your files deploy to edge locations globally via ArcBlock's infrastructure
- SSL certificates: HTTPS is provisioned immediately with no configuration
- DID-based ownership: Your creation is cryptographically linked to your decentralized identity
This isn't magic—it's opinionated defaults. MyVibe assumes you're deploying static sites or client-side applications, which covers the vast majority of AI-generated projects.
Publishing from the Command Line#
The fastest path from AI output to live URL is the MyVibe CLI. Here's a complete workflow for taking a Claude-generated React component and publishing it:
# Install the MyVibe CLI globally
npm install -g @myvibe/cli
# Authenticate with your DID wallet
myvibe auth
# Create a project directory with your AI output
mkdir my-dashboard && cd my-dashboard
# Save your Claude-generated code to index.html
cat > index.html << 'EOF'
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Analytics Dashboard</title>
<script src="https://cdn.tailwindcss.com"></script>
</head>
<body class="bg-gray-900 text-white min-h-screen p-8">
<div class="max-w-6xl mx-auto">
<h1 class="text-3xl font-bold mb-8">Weekly Metrics</h1>
<div class="grid grid-cols-1 md:grid-cols-3 gap-6">
<div class="bg-gray-800 rounded-lg p-6">
<p class="text-gray-400 text-sm">Total Users</p>
<p class="text-4xl font-bold text-cyan-400">12,847</p>
<p class="text-green-400 text-sm mt-2">↑ 12% from last week</p>
</div>
<div class="bg-gray-800 rounded-lg p-6">
<p class="text-gray-400 text-sm">Active Sessions</p>
<p class="text-4xl font-bold text-purple-400">3,291</p>
<p class="text-green-400 text-sm mt-2">↑ 8% from last week</p>
</div>
<div class="bg-gray-800 rounded-lg p-6">
<p class="text-gray-400 text-sm">Conversion Rate</p>
<p class="text-4xl font-bold text-pink-400">4.2%</p>
<p class="text-red-400 text-sm mt-2">↓ 0.3% from last week</p>
</div>
</div>
</div>
</body>
</html>
EOF
# Publish to MyVibe
myvibe publish
# Output:
# ✓ Optimized 1 file (2.1 KB → 1.8 KB)
# ✓ Deployed to edge network
# ✓ SSL certificate provisioned
#
# Live at: https://my-dashboard-7x2k.myvibe.so
The entire process completes in under 10 seconds. Your dashboard is now globally accessible with a permanent URL tied to your identity.
Handling More Complex Projects#
Single-file HTML works for prototypes, but AI tools increasingly generate multi-file projects with component structures. MyVibe handles these through directory publishing:
# Typical output structure from Lovable or v0
my-saas-landing/
├── index.html
├── css/
│ └── styles.css
├── js/
│ └── app.js
├── images/
│ ├── hero.png
│ └── features.png
└── components/
└── pricing-table.html
# Publish the entire directory
cd my-saas-landing
myvibe publish .
# Or publish a specific build output
myvibe publish ./dist
If your project includes a package.json with a build script, MyVibe will detect it and run the build before publishing:
{
"name": "my-vite-app",
"scripts": {
"build": "vite build"
},
"dependencies": {
"vite": "^5.0.0"
}
}
# MyVibe detects the build script and runs it
myvibe publish
# Output:
# ✓ Detected Vite project
# ✓ Running npm install...
# ✓ Running npm run build...
# ✓ Publishing ./dist (12 files, 847 KB)
#
# Live at: https://my-vite-app-3j9p.myvibe.so
Programmatic Publishing for Automation#
When you're building workflows that generate and publish content automatically, the CLI isn't always practical. MyVibe exposes a simple HTTP API for programmatic publishing:
import { createReadStream } from 'fs';
import { createGzip } from 'zlib';
import archiver from 'archiver';
async function publishToMyVibe(projectDir, apiKey) {
// Create a ZIP archive of the project
const archive = archiver('zip', { zlib: { level: 9 } });
const chunks = [];
archive.directory(projectDir, false);
archive.on('data', chunk => chunks.push(chunk));
await new Promise((resolve, reject) => {
archive.on('end', resolve);
archive.on('error', reject);
archive.finalize();
});
const zipBuffer = Buffer.concat(chunks);
// Upload to MyVibe publish endpoint
const response = await fetch('https://api.myvibe.so/v1/publish', {
method: 'POST',
headers: {
'Authorization': `Bearer ${apiKey}`,
'Content-Type': 'application/zip',
'X-Project-Name': 'automated-landing-page'
},
body: zipBuffer
});
if (!response.ok) {
throw new Error(`Publish failed: ${response.statusText}`);
}
const result = await response.json();
return result.url; // https://automated-landing-page-8k2m.myvibe.so
}
// Usage in an automation pipeline
const liveUrl = await publishToMyVibe('./generated-site', process.env.MYVIBE_API_KEY);
console.log(`Published: ${liveUrl}`);
This pattern works well for scheduled content generation, A/B testing different AI outputs, or building custom publishing integrations.
Understanding DID-Based Ownership#
Unlike traditional hosting where you're essentially renting space, MyVibe ties each deployment to your Decentralized Identifier (DID). This means:
- Portable ownership: If MyVibe shuts down tomorrow, your DID still proves you created these assets
- No vendor lock-in: Export your projects anytime with full provenance
- Cryptographic attribution: The link between you and your creation is verifiable, not just a database entry
When you authenticate with myvibe auth, you're connecting a DID wallet (DID Wallet from ArcBlock or any compatible identity provider). Every publish operation is signed with your private key, creating an immutable record of authorship.
This matters for vibe-coded projects because AI-generated content exists in a murky attribution space. Having cryptographic proof that you prompted, curated, and published a specific creation provides a clear ownership trail.
Limitations Worth Knowing#
MyVibe is purpose-built for a specific use case, which means it intentionally doesn't do several things:
No server-side code: You can't deploy Node.js backends, Python APIs, or database-connected applications. If your AI generates a full-stack application, you'll need to split the frontend (MyVibe) from the backend (elsewhere).
No custom domains yet: Projects publish to *.myvibe.so subdomains. Custom domain support is on the roadmap but not available today.
Storage limits: Free tier projects are capped at 50MB. This is generous for most vibe-coded outputs but won't work for media-heavy applications.
No incremental deploys: Each publish is a complete replacement. There's no diff-based deployment or rollback mechanism yet.
These constraints keep the publishing experience simple and fast. For projects that need more infrastructure, ArcBlock's broader Blocklet ecosystem provides those capabilities.
When MyVibe Makes Sense#
The platform excels for:
- Rapid prototyping: Share an AI-generated concept with stakeholders in minutes instead of hours
- Portfolio pieces: Publish one-off projects that demonstrate an idea without maintaining infrastructure
- Landing page tests: Deploy multiple variations quickly to test messaging before committing to a full build
- Educational content: Share interactive examples, calculators, or visualizations without setup overhead
It's less suitable for:
- Production applications requiring backends
- Projects with custom domain requirements
- Teams needing preview deployments and staging environments
- Applications exceeding storage limits
Getting Started#
The friction between AI output and deployment is a solved problem. If you're generating web content with AI tools and manually handling hosting, you're spending time on infrastructure that should be invisible.
Install the CLI:
npm install -g @myvibe/cli
myvibe auth
Publish your next AI creation:
myvibe publish ./your-project
The URL you get back is permanent, globally distributed, and cryptographically yours. That's the entire workflow—no configuration files, no CI pipelines, no waiting for DNS propagation. Just your vibe, shipped.