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

# Quickstart

> Connect a provider and add or deploy your first project.

Connect your provider accounts, add the projects already running on them, and look at one. It takes a few minutes. [Install Hoista](https://docs.hoista.dev/getting-started/install.md) first.

## Pick your providers

Open Desktop and choose **Set up Hoista**. Tick every provider your projects run on, then choose **Connect**.

![The Where do your projects live? step, with a checkbox on each provider card](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/screens/setup-providers-light.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=9d87f49a91653bc85bd45a45379a7d5f)

![The Where do your projects live? step, with a checkbox on each provider card](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/screens/setup-providers-dark.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=f5f59142157d6998ef39924106e62a20)

Setup, step 1, with Cloudflare, Vercel, Neon and GitHub picked.

## Connect each one

Choose **Connect** beside a provider. Where the provider offers it, Hoista opens its page so you can approve Hoista in your browser. Otherwise, paste an API token: **Open the tokens page** takes you to the right page, and **Step-by-step guide** walks you through it. Hoista checks the token works before saving it.

![The Connect your providers step, with Cloudflare connected and Neon asking for a token](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/screens/setup-connect-light.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=68bbcf215a44402d16a292716543d754)

![The Connect your providers step, with Cloudflare connected and Neon asking for a token](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/screens/setup-connect-dark.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=1dd71a18044a20a434ac901df13538f5)

Cloudflare is connected. Neon is waiting for a token.

From the command line:

```bash theme={null}
hoist accounts add
hoist accounts
```

`hoist accounts add` asks which provider to use, then reads its token through a hidden prompt.

The token stays in this computer's keychain and only the daemon reads it:

![You approve Hoista on the provider’s page or paste a token. hoistd checks it works, keeps it in the keychain, reads the account and lists the projects it finds, ready to add.](https://mintcdn.com/mirt-lab/xnVa5lZdCrkkDEzj/assets/diagrams/connect-flow-light.svg?fit=max\&auto=format\&n=xnVa5lZdCrkkDEzj\&q=85\&s=35235a42f8d8d50ce9012de61328da75)

![You approve Hoista on the provider’s page or paste a token. hoistd checks it works, keeps it in the keychain, reads the account and lists the projects it finds, ready to add.](https://mintcdn.com/mirt-lab/xnVa5lZdCrkkDEzj/assets/diagrams/connect-flow-dark.svg?fit=max\&auto=format\&n=xnVa5lZdCrkkDEzj\&q=85\&s=92f4aeb73e5612d368fed05d0a9a027a)

The token stays in this computer’s keychain. Hoista reads the account and changes nothing on it.

## Pick what Hoista watches

Each project found on a provider comes in as a Hoista project of the same name. Untick anything to leave out, or change which Hoista project it goes into, then choose **Import**.

Imported projects are in **watching** mode: the provider keeps running them its own way, and nothing changes there. From the command line, `hoist import` lists what it found and lets you pick. In a script, run `hoist import --list` and pass the resource IDs: `hoist import RESOURCE_ID --new my-app`.

## Look at a project

Open a project to see its **Overview**, **Deploys**, **Logs** and **Metrics**.

```bash theme={null}
hoist status my-app
hoist logs my-app
```

## Deploy something new

Desktop has no deploy form. Deploy from the CLI, or ask a [connected agent](https://docs.hoista.dev/agents/connect.md) to "Deploy this project with Hoista".

```bash theme={null}
hoist deploy ./my-app --project my-app
```

The CLI follows the deploy step by step until it is live or fails. You can also follow it in **Deploys**. See [plan and deploy](https://docs.hoista.dev/guides/deploy.md) to review a plan first.

## Without Desktop

Every step above works from the CLI alone. Commands start the daemon when they need it, so Desktop does not have to be open. Run `hoist doctor` if something fails, and see the [CLI reference](https://docs.hoista.dev/cli/overview.md) for every command.

## Related

> [card] [Connect an agent](https://docs.hoista.dev/agents/connect.md)
>
> Let a coding tool or chat app use Hoista.

> [card] [Plan and deploy](https://docs.hoista.dev/guides/deploy.md)
>
> Review a plan, deploy it and roll back.

> [card] [How Hoista works](https://docs.hoista.dev/getting-started/concepts.md)
>
> Accounts, projects, resources and the daemon.


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