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

# Introduction

> A brief introduction to what Frost Auth does, how it operates, and how to begin your integration.

### What Frost Auth is

Frost Auth is a License-as-a-Service platform for developers. It handles license issuance, verification, users, and subscriptions for paid software so you don't build and maintain licensing infrastructure yourself. Create a product, generate cryptographically signed license keys, and verify them from your application with a single API call. Hardware locking, live analytics, and full key control come built in.

> [card] FrostAuths SDKs
>
> SDKs handle request formatting, response signature verification, and retries automatically. Official wrappers are available for C++, C#, Rust, Go, Python, Node.js, and Java.

> [card] REST API
>
> All communication with Frost Auth runs over HTTPS. Endpoint groups handle license verification, license management, users, subscriptions, activity logs, and webhooks.

> [card]
>
> It is important to note that FrostAuth is solely an authentication service and not and obfuscation service. Clients are still reasonable for the security of their overall application.

### Basic flow

Every integration follows the same path:

1. **Issue a license** — generate a key from the dashboard with your desired expiry, device limit, hardware resets, etc.
2. **Activate** — your app calls `/api/v1/activate` with the key, hardware Id, and optional metadata (OS, app version, binary hash, device label).
3. **Validate** — the server checks the key, applies version/platform gates, enforces device limits automatically, and returns a signed verdict.
4. **Heartbeat** — periodically re-validate to catch revocations. Revocation takes effect within one heartbeat.

There is no mandatory `Init()` handshake or session token to manage. Verification is stateless per call, which means revocation takes effect immediately — the next heartbeat sees the updated status.

## **Credentials**

These four values authenticate every request. The `owner`, `product`, and `version` identify your app configuration. The `publicKey` acts as a encryption key — do not change this


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