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

# Install the Tappify CLI

> Install the Tappify command line interface on macOS, Linux, or Windows and authenticate with your Tappify account.

The Tappify CLI (`tappify`) lets you manage deployments, configure CI code signing, and publish apps from your terminal. It ships as a standalone binary (no Node.js required) and, for Node users, on npm as [`@tappify/cli`](https://www.npmjs.com/package/@tappify/cli).

## Prerequisites

* A Tappify account — sign in at [app.tappify.ai](https://app.tappify.ai)
* **Node.js 20 or newer** — only for the npm install; every other method is a self-contained binary

## Install

<Tabs>
  <Tab title="curl (macOS/Linux)">
    ```bash theme={null}
    curl -fsSL https://get.tappify.ai | sh
    ```
  </Tab>

  <Tab title="winget (Windows)">
    ```powershell theme={null}
    winget install Tappify.CLI
    ```
  </Tab>

  <Tab title="Homebrew (macOS/Linux)">
    ```bash theme={null}
    brew tap tappify-dev/homebrew-tap
    brew trust tappify-dev/tap
    brew install tappify
    ```

    Recent Homebrew requires you to trust a third-party tap before installing
    from it — the `brew trust` step does that. If you skip it, `brew install`
    errors with "Refusing to load formula … from untrusted tap".
  </Tab>

  <Tab title="Scoop (Windows)">
    ```bash theme={null}
    scoop bucket add tappify https://github.com/tappify-dev/scoop-bucket
    scoop install tappify
    ```
  </Tab>

  <Tab title="Chocolatey (Windows)">
    ```bash theme={null}
    choco install tappify
    ```
  </Tab>

  <Tab title="npm">
    ```bash theme={null}
    npm install -g @tappify/cli
    ```
  </Tab>
</Tabs>

On Windows, PowerShell can also run the install script directly:

```powershell theme={null}
irm https://get.tappify.ai/install.ps1 | iex
```

## Verify the install

```bash theme={null}
tappify --help
```

You should see the list of available commands. If `tappify` isn't found, make sure its install directory is on your `PATH` — the installer prints the path to add if needed.

## Authenticate

Log in once to link the CLI to your Tappify account:

```bash theme={null}
tappify login
```

This opens your browser to confirm the sign-in (a device authorization flow). Once approved, your session is stored locally and every command authenticates automatically.

<Note>
  Your session lives in a per-user config file (`~/.config/tappify/config.json` on
  macOS/Linux, `%APPDATA%\tappify\config.json` on Windows). Run `tappify logout`
  to clear it.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="CLI commands" icon="rectangle-terminal" href="/guides/cli/commands">
    Every command, its options, and examples.
  </Card>

  <Card title="Set up code signing" icon="shield-check" href="/guides/signing/setup">
    Configure signing so your builds can ship.
  </Card>
</CardGroup>