Share your vibe-coded app online in seconds

No cloud setup required, deploy in your AI chat

Q: How do I host a Cursor or Claude Code UI without AWS?

Register at vibepage.cloud, install the vibepage CLI, run vibepage token YOUR_TOKEN, then vibepage deploy. You get a public HTTPS subdomain without opening a cloud account.

Q: Can Claude Code, Cursor, or Codex deploy for me?

Yes. Paste fetch https://vibepage.cloud/ai.md into the same chat and ask the agent to follow it. Agents authenticate with your API token and run deploy. See https://vibepage.cloud/for-agents.md.

Q: What kinds of projects can I put online?

Static UIs — an index.html, or a publish folder like dist/ or build/. vibepage is for frontend demos, landing pages, and vibe-coded experiments — not full backends, databases, or server apps.

Q: Do I need to set up SSL certificates?

No. Project URLs on *.app.vibepage.cloud are served over HTTPS for you.

Q: What is the difference between deploy and tunnel?

vibepage deploy publishes static files to your public subdomain. vibepage tunnel points that same URL at a server on your laptop for live demos. When the tunnel stops, the last static deploy remains.

Q: Do I need a custom domain to share my idea?

No. Your default *.app.vibepage.cloud subdomain is enough to share. Custom domains are a later Pro-oriented feature and are not required to go live.

Q: Can I update the site after it is live?

Yes. Change your UI, run vibepage deploy again from the project folder, and the same subdomain updates. Keep your API token handy or set VIBEPAGE_TOKEN so you or your agent can redeploy anytime.

Get started with your coding agent

# paste into Claude / Cursor / Codex

fetch https://vibepage.cloud/ai.md

How it works

Stay in the chat. Keep the vibe.

Deploy, share, and iterate without opening a cloud console — Claude Code and Cursor run the loop for you.

Step 1

Vibe-code the app

Build the UI in Claude Code or Cursor until you’d actually send it to a friend.

Step 2

Ask your agent to go live

Paste fetch https://vibepage.cloud/ai.md — deploy stays in the same chat.

Step 3

Share with friends

Public HTTPS subdomain in seconds — then measure and improve without breaking flow.

Features

Four things. One vibe.

Go live fast, store data without a database, control access — manage it all from your coding agent.

Go live fast

Shareable link in seconds

Public HTTPS subdomain — the fastest path to deploy online.

No database setup

Virtual data table

Tables owned by your project — store and read data without worrying about a database.

Basic access control

Public or private

Share openly, or keep it private — simple authorization control for your project.

Keep the vibe

Skills library

Manage everything from your favorite coding agent — deploy, tables, access — with our skills library.

Compare

50x faster than cloud setup

Share a live link with friends in minutes — or still be stuck creating cloud accounts while the vibe dies.

In your AI chat

Ready

Cloud setup

Ready

Testimonials

Why builders keep the vibe here

Go live, share with friends, learn from visitors, improve — without leaving Claude Code or Cursor.

I told Cursor to deploy it. Three commands later I had a real link to send my friend. No AWS rabbit hole.

Jordan Lee Weekend builder · shipped a landing page in one night

FAQ

Questions about the loop

Going live, measuring traffic, A/B testing, and staying inside your AI chat.

How do I host a Cursor or Claude Code UI without AWS?

Register at vibepage.cloud, copy your API token, then install the CLI and run vibepage token YOUR_TOKEN followed by vibepage deploy from your UI project. You get a public HTTPS subdomain — no AWS account, DNS, or SSL setup.

Can Claude Code, Cursor, or Codex deploy for me?

Yes. Paste fetch https://vibepage.cloud/ai.md into the same chat and ask the agent to follow it. Agents authenticate with your API token (non-interactive) and run deploy for you. Full playbook: for-agents.md.

What kinds of projects can I put online?

Static UIs — an index.html, or a publish folder like dist/ or build/. vibepage is for frontend demos, landing pages, and vibe-coded experiments — not full backends, databases, or server apps.

Do I need to set up SSL certificates?

No. Every project URL on *.app.vibepage.cloud is served over HTTPS for you. No certbot, nginx, or “not secure” browser warnings to fight.

Is there a free plan?

Yes. Early access Free is $0 with no credit card — limited storage, one subdomain, and a monthly traffic cap. Upgrade when you need more. See pricing for Free, Pro, and Enterprise details.

How fast can I get a shareable link?

Once you have a token, deploy usually lands a live URL in seconds — fast enough to text someone the same night you finish the UI. No waiting on cloud account approvals or DNS propagation.

What’s the difference between deploy and tunnel?

vibepage deploy publishes your static files to your public subdomain. vibepage tunnel points that same URL at a server on your laptop (for live demos while you edit). When the tunnel stops, the last static deploy is still there.

Do I need a custom domain to share my idea?

No. Your default *.app.vibepage.cloud subdomain is enough to share with friends, investors, or Twitter. Custom domains are a later Pro-oriented feature — not required to go live tonight.

Is vibepage like Lovable or Base44?

No. Those tools build and host inside their own product. vibepage is for UIs you already vibe-coded in Claude Code, Cursor, Codex, or similar agents — then need a public HTTPS link without cloud setup.

Can I see traffic and where visitors came from?

Yes — built-in insights show views, visitors, and referrers for your subdomain so you can learn quickly after you share the link. No Google Analytics account required.

Can I A/B test and keep improving?

That’s the loop: ship a variant from Claude Code or Cursor, compare results, keep the winner, redeploy. Continuous improvement without leaving the chat.

Can I update the site after it’s live?

Yes. Change your UI, run vibepage deploy again from the project folder, and the same subdomain updates. Keep your API token handy (or set VIBEPAGE_TOKEN) so you or your agent can redeploy anytime.