Skip to main content

​
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.
Individual Licenses are tied to your GitHub identity. When you authenticate via the CLI, your downloads are tracked against your personal license.

​
How It Works

  1. Purchase a subscription at uniwind.dev/pricing
  2. Assign the license to a GitHub account from your 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

MetricLimit
Monthly downloads300
Reset period1st of each month
Download limits reset automatically at the start of each calendar month (UTC). Unused downloads do not roll over.
Need higher limits? Contact [email protected] to discuss extended quotas.

​
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
  • Reinstallations after deleting node_modules
  • CI/CD pipeline installations (use a CI/CD License instead)
Cache your node_modules or use a package cache to reduce download count. Most developers use only 5-10 downloads per month during normal development.

​
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:
  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.
License holders must have a GitHub account. The username is case-insensitive but must match exactly.

​
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

Cache node_modules

Avoid reinstalling unnecessarily. Use bun install --frozen-lockfile or equivalent.

Use Team Licenses for projects

Set up Team Licenses for shared projects to reduce individual usage.

Use CI/CD License for pipelines

Never use Individual Licenses in CI/CD - use your dedicated CI/CD token.

Monitor usage

Check your dashboard regularly to avoid hitting limits unexpectedly.

Team License

Shared license for project-based access

CI/CD License

Automated pipeline access