> For the complete documentation index, see [llms.txt](https://docs.genvibe.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.genvibe.pro/features/deployment.md).

# Deploying your app

When your app is ready, you can put it online in one click, connect your own domain, export the code, or download it.

There are two ways to go live:

1. **GenVibe hosting** — the fastest path. One click publishes your app to a live `genvibe.app` link. No accounts, no config.
2. **Netlify** — connect your Netlify account and deploy there instead.

## Publish to GenVibe hosting

The quickest way to share your app. GenVibe builds it and hosts it for you at a live URL — nothing to set up.

1. Click **Publish** in the top bar. *(After a successful build you'll also see a **“Publish your app”** button right in the chat.)*
2. GenVibe builds your app and uploads it to GenVibe hosting.
3. You get a live link like **`your-app.genvibe.app`** you can share immediately.

Re-publishing after changes is one click and **keeps the same URL**. From the Publish menu you can always copy your live link, open it, or update it.

{% hint style="info" %}
On the **Free** plan, published apps show a small **“Made with GenVibe”** badge in the corner. It's removed automatically on any **paid** plan.
{% endhint %}

## Custom domains

On any **paid plan** (Standard or Pro) you can connect your **own domain** — like `www.yourbusiness.com` — to an app you've published on GenVibe hosting. HTTPS/SSL is set up for you automatically.

**Steps:**

1. **Publish your app** to GenVibe hosting first (above).
2. Open the **Publish** menu → **Custom domain**.
3. Enter your domain. If you type a bare domain (e.g. `yourbusiness.com`), pick **`www.`** — it's recommended and works on every registrar. (A bare root domain is possible too, but needs a registrar that supports CNAME flattening / ALIAS.)
4. GenVibe shows you the exact **DNS records** to add — a `CNAME` pointing your domain to `fallback.genvibe.app`, plus a one-time record that turns on SSL (and, for a root domain, an ownership record).
5. Sign in to wherever your domain's DNS is managed (GoDaddy, Namecheap, Hostinger, Cloudflare, etc.), add the records exactly as shown, and save.
6. Back in GenVibe, click **Check status**. Once DNS propagates (usually a few minutes), your domain goes **Live** with SSL — no further action needed.

{% hint style="warning" %}
For a **root/apex** domain (no `www`), most providers need you to use **Name = `@`** and to **delete any existing A record on the root first** (a name can't have both an A record and a CNAME). If your provider doesn't support CNAME flattening, use the `www.` version instead. To make the bare domain redirect to `www`, add a free URL redirect (`yourbusiness.com` → `www.yourbusiness.com`) in your registrar's dashboard.
{% endhint %}

## Deploy to Netlify

Prefer to host on Netlify? Connect your Netlify account from the deploy menu and click deploy — GenVibe builds and publishes your app to Netlify and gives you a live URL. Re-deploying keeps the same URL. You can then add a custom domain from the Netlify dashboard.

{% content-ref url="/pages/eW1kQHhUz2QWc5APbVgM" %}
[Netlify](/integrations/netlify.md)
{% endcontent-ref %}

## Export to GitHub

Push your project to a GitHub repository to take the code with you, collaborate, or set up your own CI/CD. Connect GitHub from the integrations menu, then export.

{% content-ref url="/pages/dm1m55P75wcxwjJyu5Hs" %}
[GitHub](/integrations/github.md)
{% endcontent-ref %}

## Download the project

You can also download your project as a zip to run locally or host anywhere you like.

## Mobile apps

Mobile (React Native + Expo) projects are deployed differently from web apps — export the code to GitHub and use the standard Expo build and submit flow for the App Store and Google Play. See [Mobile apps](/features/mobile-apps.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.genvibe.pro/features/deployment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.