Skip to main content
Connect your provider accounts, add the projects already running on them, and look at one. It takes a few minutes. Install Hoista 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 cardThe Where do your projects live? step, with a checkbox on each provider card

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 tokenThe Connect your providers step, with Cloudflare connected and Neon asking for a token

Cloudflare is connected. Neon is waiting for a token.

From the command line:
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.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.

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.

​
Deploy something new

Desktop has no deploy form. Deploy from the CLI, or ask a connected agent to “Deploy this project with Hoista”.
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 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 for every command.

Connect an agent

Let a coding tool or chat app use Hoista.

Plan and deploy

Review a plan, deploy it and roll back.

How Hoista works

Accounts, projects, resources and the daemon.