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

# Unlimited applications

> Create as many AuthForge apps as you need under one account: one credit pool, no per-app subscription.

AuthForge does **not** charge per application or cap how many products you can register. Your account is billed for **API usage** (validations and heartbeats), not for how many apps or license keys exist.

## One account, many apps

Each **app** is a separate container for:

* Its own **App ID** and **App Secret**
* Its own **license keys**, [variables](/features/variables), [webhooks](/features/webhooks), and [security lists](/features/security)

Typical uses:

* Multiple commercial products or editions
* Separate staging vs production apps (different secrets and keys)
* Different brands or teams under the same billing account

## One credit balance

[Credits](/best-practices/credit-management) are shared across **all** apps on your account. Successful validations and heartbeats deduct from the same pool; no need to buy credits separately per product.

## Practical limits

Reasonable use of many apps is expected. If you need enterprise-scale organization (many teams, compliance boundaries), structure apps and API keys so each product only accesses its own `appId`.

## See also

* **[Core Concepts; Apps](/concepts#apps)**: What an app represents in AuthForge.
* **[Quickstart](/quickstart)**: Create your first app and ship a build.
* **[Credit management](/best-practices/credit-management)**: Auto-refill, alerts, and usage.
