> ## 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.

# Supported platforms

> Operating systems, providers and where to start when something breaks.

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

## Operating systems

| | macOS | Linux | Windows |
| - | - | - | - |
| CLI and daemon | Yes | Yes | Yes |
| Desktop app | Apple silicon and Intel | AppImage and `.deb` | Not yet |
| Start at sign-in | launchd | systemd user service | Task Scheduler |
| Isolated local builds | System sandbox | Needs bubblewrap (`bwrap`) | Not available |
| Confirm it's you | Touch ID or your password | polkit password prompt | Windows Hello |

Without build isolation, Hoista stops local builds unless you allow them in **Settings → Safety**. See [Build isolation](https://docs.hoista.dev/security/builds.md). Install steps are in [Install](https://docs.hoista.dev/getting-started/install.md).

## 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](https://docs.hoista.dev/providers/overview.md).

## Remotes

`hoist remote create` and **Settings → Instances** can set up a [remote](https://docs.hoista.dev/guides/remote.md) in a Railway or Fly.io account. You can also run one with Docker on your own computer or server.

## When something breaks

```bash theme={null}
hoist doctor
hoist diagnostics
hoist diagnostics --save
```

`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](https://docs.hoista.dev/examples/failed-deployment.md). For a change whose result Hoista doesn't know, see [Backups and recovery](https://docs.hoista.dev/guides/backups.md#when-hoista-didnt-hear-back).

## Related

> [card] [Install Hoista](https://docs.hoista.dev/getting-started/install.md)
>
> Install the CLI, the daemon and Desktop.

> [card] [A failed deployment](https://docs.hoista.dev/examples/failed-deployment.md)
>
> Find where it failed and fix it.

> [card] [Backups and recovery](https://docs.hoista.dev/guides/backups.md)
>
> Back up Hoista and settle unclear changes.


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