> For the complete documentation index, see [llms.txt](https://docs.roomiekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomiekit.io/roomie-kit-cloud-and-hosted/deploy-health.md).

# Deploy and health checks

The Roomie Kit Cloud deploy flow prepares the app and deploys customer-owned infrastructure.

Deploy command:

```bash
npx roomie-kit-host deploy --execute --resume
```

Deploy steps:

1. Write local web environment values.
2. Apply Supabase migrations.
3. Set Supabase Edge Function secrets.
4. Deploy core Supabase functions.
5. Link or create the Vercel project.
6. Set Vercel production environment variables.
7. Deploy Vercel production.
8. Save the production URL.
9. Print Supabase Auth redirect URLs to confirm.

Health command:

```bash
npx roomie-kit-host health
```

Health checks should confirm:

* Deployed web URL responds.
* Supabase project is reachable.
* Agora token function works.
* Asset CDN/base URL responds.

If a deploy fails, rerun with `--resume`.

## Hosted Post-Deploy Checks

Roomie Kit Hosted runs its own checks after Vercel deploys:

* Hosted URL response.
* Required starter assets.
* Supabase API response.
* Agora token CORS.
* Agora token configuration.

Hosted check results appear on the app card in the account dashboard.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roomiekit.io/roomie-kit-cloud-and-hosted/deploy-health.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.