Skip to main content
What Hoista runs on, which providers it works with, and what to do when something breaks.

​
Operating systems

Without build isolation, Hoista stops local builds unless you allow them in Settings → Safety. See Build isolation. Install steps are in Install.

​
Providers

Hoista works with Cloudflare, Fly.io, Railway, Vercel, Neon, Supabase, Render, Resend, Runpod, Modal and GitHub. What you can do depends on the provider, your plan and your token’s permissions. Run hoist providers to see what your installed version supports, or read Providers.

​
Remotes

hoist remote create and Settings → Instances can set up a remote in a Railway or Fly.io account. You can also run one with Docker on your own computer or server.

​
When something breaks

hoist doctor checks Hoista’s local state, the credential store and your connected accounts. hoist diagnostics builds a troubleshooting report without tokens or secret values. In Desktop, the same report is under Settings → General → Diagnostic report. Read the report before you share it. For a deployment that failed, follow Investigate a failed deployment. For a change whose result Hoista doesn’t know, see Backups and recovery.

Install Hoista

Install the CLI, the daemon and Desktop.

A failed deployment

Find where it failed and fix it.

Backups and recovery

Back up Hoista and settle unclear changes.