# Fayz deploy

The official deploy for Fayz apps: one command that handles build, hosting, database and domain — with no rewrites or variables to configure by hand. You connect the app and the platform does the rest.

```bash
fayz login          # once, with your access token
fayz deploy         # creates/connects the project, uploads the code and publishes
```

The platform builds the app in a managed container and publishes it at its own URL (`https://<your-app>.live.fayz.ai`), with custom domain support.

{% callout type="info" %}
**Access is rolling out.** `fayz deploy` is being opened up to the invited developer network. If your token doesn't have deploy access yet, come talk to us in the [community](/en/docs/resources/community).
{% /callout %}

## What it does

It closes the gap between "the app runs on my machine" and "the app is live", removing the manual steps of a [static deploy](/en/docs/deploy/static):

- **Build + hosting** — the platform builds (install + Vite build) and serves the app; no `vercel.json` / `_redirects`, no output directory.
- **Connected project** — the app is linked to a Fayz project (`.fayz/project.json`), with a management dashboard on the platform.
- **Database** — provisioning and migration (`fayz db apply`) in the same workflow.
- **Environments and domain** — your own production URL + custom domain, with variables managed by the platform.

## Alternative: static hosting

[Static deploy](/en/docs/deploy/static) puts the same app live on any file host (Vercel, Netlify, Cloudflare Pages) and remains fully supported. Moving from one to the other changes the publishing flow, not the app.

---

Next: the full walkthrough in [07 · Publish](/en/docs/tutorial/07-publish).