> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibely.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish your Vibely project

> Deploy your app to a live URL, choose who can see it, review security, and push updates whenever you are ready.

Publishing turns your project into a live web app on a URL you can share. Vibely [hosts the published app](/features/deploy/hosting) for you: no servers to set up, and HTTPS included. Only the version you publish is live, so you can keep building without breaking what visitors see.

<Frame>
  <img src="https://cdn.vibely.sh/doc/v1/web-app-publish-1.webp" alt="Publish your Vibely project" width="1200" height="675" />
</Frame>

## Quick start: publish your first project

<Steps>
  <Step title="Click Publish">
    In your project, click **Publish** (the rocket button) in the top-right corner of the editor.
  </Step>

  <Step title="Choose who can access your website">
    Pick **Public** to let anyone with the URL visit, then click **Continue**. The other options need a Business plan. See [Who can see your published app](#who-can-see-your-published-app).
  </Step>

  <Step title="Click Publish again">
    Vibely suggests an address based on your project name, ending in `.vibelyagent.com`. Keep it or change it, then click **Publish**. When the deploy finishes, Vibely shows **Published!** with your live link.
  </Step>
</Steps>

To push later changes, open the same popover and click **Update**. The rest of this page covers every option, republishing, and who can publish and view your app.

## The Publish dialog, step by step

<Steps>
  <Step title="Open the Publish dialog">
    Click **Publish** in the editor header. When the popover opens, Vibely runs a quick basic security scan in the background.
  </Step>

  <Step title="Choose who can access your website">
    Under **Who can access your website?**, choose **Public**, **Workspace**, **Specific groups** or **Private**, then click **Continue**. Everything except **Public** requires Business.
  </Step>

  <Step title="Set your website address">
    Type the subdomain in the **Domain** field. Your app is published at `https://<your-name>.vibelyagent.com`. Vibely checks availability as you type and shows **Available** or why the name can't be used.

    Names must be 3–63 characters, using lowercase letters, numbers and dashes, and can't start or end with a dash. Every name is unique across Vibely, so popular names may be taken.

    If your workspace has [branded app URLs](/features/deploy/branded-urls) turned on, the address uses your workspace's pattern instead.
  </Step>

  <Step title="Review security (optional)">
    Click **Review security** to add website info and see the review screen, or click **Publish** straight away.

    * **Website info**: a title (up to 60 characters) and a short description (up to 160 characters). When you publish, Vibely uses them for your live site's browser-tab title, search description and link previews (`og:title` / `og:description`) on every page where your app's code still has the template placeholder or no tag at all. A title or description your app's code sets for a page always wins. See [Website info and your app's own tags](/features/grow/seo#website-info-and-your-apps-own-tags).
    * **Ready to publish?** shows your **URL**, **Website access** and **Website info**, plus the result of the security scan: **No critical security issues detected**, or the number of critical issues to review. Critical findings don't block publishing unless your workspace requires it, but the button changes to **Publish anyway** so you notice. You can also let Vibely fix the issues first.
  </Step>

  <Step title="Publish">
    Click **Publish**. Vibely shows **Building project**, **Deploying** and **Setting up domain** as it works. When it's done you see **Published!** and **Your app is now live**, with a link to your site and a shortcut to **Connect a custom domain**.
  </Step>
</Steps>

<Tip>
  Before you share the link, fill in **Website info** or ask Vibely to set your app's title, description and social image. New apps ship with placeholder metadata. See [SEO and AI search](/features/grow/seo).
</Tip>

## Republish to make new changes live

The live site is a snapshot of your last publish. Edits you make in the editor don't reach it until you publish again.

When your project has changes that aren't live yet, a small dot appears on the **Publish** button (tooltip **Unpublished changes**). Open the popover and click **Update** to deploy them. When there's nothing new, the button reads **Up to date**.

The popover for a published project shows:

* **Visit site**, and the number of visitors in the last 7 days (click it to open [Analytics](/features/grow/analytics)).
* **Website URL** with a copy button, and **Add custom domain**.
* **Who can see this website**.
* **Edit settings** to change the URL, visibility or website info, and to run a **Deep security scan** (an AI review of your codebase that takes about 4 minutes).
* **Unpublish**, to [take the site offline](#take-your-site-offline).

Setting changes, like a new address, different access or new website info, also take effect when you click **Update**.

## Publish from an AI assistant

The Vibely agent in the project chat doesn't publish for you; use the **Publish** button. If you work from Claude, ChatGPT or Cursor through the [Vibely MCP server](/integrations/vibely-mcp-server), you can ask the assistant to publish (the `deploy_project` tool) or take a site offline (`unpublish_project`).

## Take your site offline

Open **Publish**, click **Unpublish** at the bottom of the popover, then confirm. (From an AI assistant, the `unpublish_project` tool does the same.) Unpublishing:

* stops the live URL from working,
* disconnects any custom domains attached to the project,
* resets the site's address and access settings, so the next publish starts from the first-publish steps,
* keeps your project in the editor, so you can publish again at any time.

Anyone who can publish the project can unpublish it. If a publish is still running, wait for it to finish first.

<Frame>
  <img src="https://cdn.vibely.sh/doc/v1/web-app-publish-2.webp" alt="Publish your Vibely project" width="1200" height="675" />
</Frame>

## Who can publish projects?

By default, **owners, admins and editors** can publish. Workspace owners and admins can change this in **Settings → Permissions → Publish to the web**. See [Collaboration](/features/collaboration/overview#workspace-permissions).

Workspace owners and admins can add stricter rules in **Settings → Privacy & security → Publishing**:

| Setting | What it does | Plan |
| - | - | - |
| **Default website access** | The access new projects start with: **Anyone**, **Workspace** or **Private**. | Business |
| **Who can publish externally** | **Everyone**, **Editors and above**, or **Owners only**. | Business |
| **Block publishing with critical issues** | Refuses to publish while the security scan has critical findings. | |
| **Block publishing with PII** | Refuses to publish when personal data is exposed. | Business |
| **Require basic security scan before first publish** | A project must pass a scan before it goes live for the first time. | |

If your workspace requires two-factor authentication, Vibely asks for the 6-digit code from your authenticator app when you publish. Enter it, then publish again. Set up two-factor authentication in [account settings](/features/account/settings#two-factor-authentication).

## Who can see your published app

### Free and Pro plans

Your published app is **Public**: anyone with the link can visit it. Make sure you're ready to share before you publish.

### Business and Enterprise plans

Choose who can visit in the access step:

| Option | Who can visit |
| - | - |
| **Public** | Anyone with the URL. |
| **Workspace** | Only signed-in members of your workspace. |
| **Specific groups** | Only members of the [groups](/features/workspace/groups) you select. |
| **Private** | Only you. |

Visitors to a non-public site are asked to sign in to Vibely first, and people without access can request it.

This controls who can visit the **live site**. Who can open the **project in the editor** is a separate setting. See [Share a project](/features/collaboration/sharing).

## FAQ

<AccordionGroup>
  <Accordion title="Does publishing cost credits?">
    No. Publishing and republishing don't use credits. Fixing build errors or security issues with the agent does, like any other build.
  </Accordion>

  <Accordion title="Does my published site expire?">
    No. It stays live until you take it offline, even if you close Vibely.
  </Accordion>

  <Accordion title="Does publishing expose my project and code?">
    No. Visitors see your running app. Your chat, source code and unpublished changes stay in the editor, controlled by [project access](/features/collaboration/sharing).
  </Accordion>

  <Accordion title="Why don't I see my latest changes on the live site?">
    The live site only changes when you publish. Look for the dot on the **Publish** button, open it, and click **Update**. If you still see the old version, hard-refresh the page.
  </Accordion>

  <Accordion title="How do I change my published URL?">
    Open **Publish → Edit settings → URL**, pick a new name, then click **Update**. Renaming the project doesn't change the URL. To use your own domain, see [Custom domain](/features/deploy/custom-domain).
  </Accordion>

  <Accordion title="Why is there an &#x22;Edit with Vibely&#x22; badge on my site?">
    Apps published from a Free workspace show a small **Edit with Vibely** badge on the `vibelyagent.com` address. Visitors can dismiss it for 7 days. Upgrading to a paid plan removes it, and it never appears on custom domains.
  </Accordion>

  <Accordion title="What happens to my site if I downgrade?">
    Your site stays live. On a plan without restricted access, the next publish switches website access back to **Public**, and the **Edit with Vibely** badge returns on Free.
  </Accordion>

  <Accordion title="Can I publish a mobile app to the App Store or Play Store?">
    Publishing here puts your app on the web. Store submission is a separate flow. See [Ship your mobile app](/features/mobile-apps/ship).
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Build failed — your project has errors">
    Vibely type-checks and builds your app before deploying it, and stops if either fails. Open the chat: Vibely posts the error there and can fix it. Use **Auto-fix with AI** in the popover, then publish again.
  </Accordion>

  <Accordion title="The built app exceeds size limits">
    The build is too large to deploy. Remove large images, videos or unused dependencies (ask Vibely to find them), then publish again.
  </Accordion>

  <Accordion title="A deployment is already in progress">
    Only one publish can run per project at a time. Wait for it to finish, then publish again.
  </Accordion>

  <Accordion title="That name is already taken">
    Subdomains are unique across Vibely. Try a different name, for example with your company name added.
  </Accordion>

  <Accordion title="You don't have permission to publish this project">
    Your role isn't allowed to publish in this workspace. Ask a workspace owner or admin to change **Settings → Permissions → Publish to the web**, or to publish for you.
  </Accordion>

  <Accordion title="Publishing failed. Please try again.">
    A temporary problem stopped the deploy. Try again in a minute. If it keeps failing, contact support with your project URL.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="How Vibely hosts your app" icon="server" href="/features/deploy/hosting">
    What happens after you publish.
  </Card>

  <Card title="Custom domain" icon="globe" href="/features/deploy/custom-domain">
    Serve your app on your own domain.
  </Card>

  <Card title="SEO and AI search" icon="magnifying-glass" href="/features/grow/seo">
    Get found in search and AI answers.
  </Card>

  <Card title="Monitoring" icon="heart-pulse" href="/features/grow/monitoring">
    See errors your visitors hit.
  </Card>
</CardGroup>


## Related topics

- [Publish your app as an MCP server](/features/grow/agent-integrations.md)
- [Projects in Vibely](/features/projects/overview.md)
- [Welcome to Vibely](/introduction/welcome.md)
- [Vibely for Enterprise](/introduction/enterprise.md)
- [Project analytics](/features/grow/analytics.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.