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

# Individual License

> Personal license for individual developers

## Overview

An Individual License is assigned to a specific GitHub account and allows that developer to download and use Uniwind Pro for local development. Each seat in your subscription includes one Individual License.

<Info>
  Individual Licenses are tied to your GitHub identity. When you authenticate via the CLI, your downloads are tracked against your personal license.
</Info>

## How It Works

1. **Purchase a subscription** at [uniwind.dev/pricing](https://uniwind.dev/pricing)
2. **Assign the license** to a GitHub account from your [dashboard](https://uniwind.dev/dashboard)
3. **Authenticate** using the CLI with `uniwind-pro`
4. **Install** Uniwind Pro in your projects

The license holder can install Uniwind Pro on any number of machines, but downloads are tracked per account.

## Download Limits

| Metric            | Limit             |
| ----------------- | ----------------- |
| Monthly downloads | **300**           |
| Reset period      | 1st of each month |

<Info>
  Download limits reset automatically at the start of each calendar month (UTC). Unused downloads do not roll over.
</Info>

<Tip>
  Need higher limits? Contact [support@uniwind.dev](mailto:support@uniwind.dev) to discuss extended quotas.
</Tip>

### What counts as a download?

Each time the CLI fetches the Uniwind Pro package from our CDN, it counts as one download. This includes:

* Fresh installations via `uniwind-pro` CLI
* Local reinstalls only when the local Uniwind Pro cache is missed and a new CDN fetch is required
* CI/CD pipeline installations (CI does not use the local cache, use a [CI/CD License](/pro/cicd-license))

<Tip>
  Uniwind Pro includes its own cache in local environments, which reduces repeated downloads during normal development. The cache also works across Git worktrees on the same machine. This built-in cache does not apply to CI/CD.
</Tip>

## Requirements

* Active Uniwind Pro subscription with available seats
* GitHub account
* License must be assigned to your GitHub handle in the dashboard

## Assigning a License

Organization owners can assign Individual Licenses from the [dashboard](https://uniwind.dev/dashboard):

1. Navigate to **Licenses** section
2. Click **Add License**
3. Enter the GitHub username
4. Select **Individual** license type
5. Click **Invite**

The invited user will receive access immediately and can authenticate using their GitHub account.

<Warning>
  License holders must have a GitHub account. The username is case-insensitive but must match exactly.
</Warning>

## Managing Your License

From your dashboard, you can:

* View current download usage
* See days remaining until reset
* Check license expiration date
* View download history

## Best Practices

<CardGroup cols={2}>
  <Card title="Use local Uniwind cache" icon="box">
    Uniwind Pro reuses its local cache between installs (including Git worktrees), so repeated local setups usually avoid extra downloads.
  </Card>

  <Card title="Use Team Licenses for projects" icon="users">
    Set up Team Licenses for shared projects to reduce individual usage.
  </Card>

  <Card title="Use CI/CD License for pipelines" icon="server">
    Never use Individual Licenses in CI/CD - use your dedicated CI/CD token.
  </Card>

  <Card title="Monitor usage" icon="chart-line">
    Check your dashboard regularly to avoid hitting limits unexpectedly.
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Team License" icon="users" href="/pro/team-license">
    Shared license for project-based access
  </Card>

  <Card title="CI/CD License" icon="server" href="/pro/cicd-license">
    Automated pipeline access
  </Card>
</CardGroup>