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

# Core concepts

Understanding these core concepts will make it easier to design your pricing and integrate the SDK.

***

## Products

A product is the main thing you sell.
Examples: "Cursor", "TimeMaster Pro", or "API Service".

[Learn more about products →](/product-catalog/products)

***

## Plans

A plan is how you package and price your product. You attach features and prices to a plan.

Examples: Free, Starter, Pro, Enterprise.

[Learn more about plans →](/product-catalog/plans)

***

## Features & Entitlements

A feature is a capability a customer can access. Entitlements define how that feature gets used within a specific plan.

You define features once and reuse them across multiple plans. Entitlements control the access, limits, or configuration for those features.

Examples:

* API access with 1,000 requests per month
* AI tokens with a limit of 10,000 tokens per month
* Storage feature with 100 GB included
* Priority support enabled for Pro customers

Entitlements come in three types

* **Boolean** to toggle a feature on or off
* **Metered** to track usage like AI tokens, workflow runs, or compute time
* **Config** to pass custom values or settings to your application

[Learn more about features & entitlements →](/product-catalog/entitlements)

***

## Digital downloads

A digital download is a file that your customers can download after purchasing.

Examples: e-books, software, music, videos.

[Learn more about digital downloads →](/product-catalog/digital-downloads)

***

## License keys

A license key is a code that your customers can use to activate a digital download.

Examples: software activation, game keys, e-books.

[Learn more about license keys →](/product-catalog/license-keys)

***

## Links

Links allow you to share important URLs with customers after they purchase your plan.

Examples: Discord servers, Slack workspaces, Notion pages, member-only dashboards.

[Learn more about links →](/product-catalog/links)

***

## Customers

A customer is a person or company that purchases your product.

Typically, you create a customer record when someone signs up in your app.
When they complete a purchase, Kelviq maps the transaction to the customer record automatically.

[Learn more about customers →](/coustomers-management/overview)

***

## Typical workflows

### AI and usage based products

Billing for actual work delivered rather than just seat access.

1. Create features like AI tokens, API calls, or workflow runs
2. Create a product
3. Create plans with a flat base fee plus metered usage charges
4. Add entitlements to set soft or hard caps on compute
5. Integrate the SDK to report usage back to Kelviq as the AI performs work
6. Customer subscribes and pays automatically based on their actual consumption

### One-time products

Selling digital downloads, license keys, or access links:

1. Create a **product**
2. Create a **plan** with one-time pricing
3. Add **digital downloads**, **license keys**, or **links** to the plan
4. Share your checkout link or embed a pricing table
5. Customer purchases → receives their files, keys, and links

### SaaS subscriptions

Selling recurring access with feature limits:

1. Create **features** (e.g., API calls, storage, AI tokens)
2. Create a **product**
3. Create **plans** with recurring pricing (monthly/yearly)
4. Add **entitlements** to each plan (e.g., 1,000 API calls/month)
5. Integrate the **SDK** to check feature access and enforce limits
6. Customer subscribes → SDK controls what they can access

***

## Integrate with your app

To bring everything you set up in the dashboard into your app, use one of these options:

* **[SDKs](/frontend-integration/react-sdk)** — check feature access and enforce usage limits in code
* **[APIs](/api-reference/authentication)** — use for custom needs such as syncing usage or triggering upgrades

<Tip>
  **No webhooks required.** Kelviq SDKs and UI widgets stay in sync automatically—no need to build webhook handlers or manage event processing.
</Tip>

[See the full integration guide →](/quickstart/integrate-with-your-app)

***

## Need help?

Have questions, need help with implementation, or want a walkthrough?\
Email us at **[hi@kelviq.com](mailto:hi@kelviq.com)** or [book a demo](https://tidycal.com/neravath/15-minute-meeting).

***