> This page is for version V3 - Beta (default).
> For other versions, use one of these documentation indexes:
> - V3 - Beta (default): https://docs.authlyx.dev/v3/llms.txt
> - V2 - Legacy: https://docs.authlyx.dev/v2/llms.txt
> - V1 - End of support: https://docs.authlyx.dev/v1/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.authlyx.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.authlyx.dev/_mcp/server.

# How AuthlyX works

> What you manage in AuthlyX and what happens when someone opens your app.

AuthlyX gives developers a server and dashboard for managing access to their software. Licensing is one part of it. You can also manage users and approved devices, customer plans, remote app data, releases, webhooks and management integrations.

## The three parts

* **Dashboard:** where you create applications, define access and change settings.
* **API:** checks requests against the application's stored records and rules.
* **SDK:** handles the API protocol in your application's language and returns results to your code. Developers can also call the HTTP API directly.

```mermaid
flowchart TD
    DEV[You manage MyApp in the dashboard] --> ACCESS[Licenses, users, devices and customer plans]
    DEV --> DATA[Cloud variables, scripts, features and metadata]
    DEV --> RELEASE[Release channels and Allowed Versions]
    DEV --> EVENTS[Webhooks, logs and management integrations]
    APP[Customer opens MyApp] --> API[MyApp connects through an SDK or direct API requests]
    ACCESS --> API
    DATA --> API
    RELEASE --> API
    API --> RESULT[Your code receives access decisions and requested data]
    API --> EVENTS
    RESULT --> UI[MyApp decides what to show and which operations to allow]
```

## Access and licensing

You create the records your customers use to sign in: licenses, usernames and passwords, or whitelisted devices. Each record can have its own expiry and device limits. A successful login creates a session; later requests are checked against that session and the current rules.

A license is not necessarily a long random string. It is a value you issue and AuthlyX checks. You can generate a key or use your own value. See [Choose how customers sign in](/v3/guides/access-methods) for the alternatives and [Sessions and heartbeats](/v3/guides/sessions) for what happens after login.

## Plans and identity data

Your customer plans describe what you offer within MyApp. Features can represent permissions or values such as video quality. Metadata stores additional information about a plan or identity; app-readable fields can be fetched remotely, while private fields stay out of the customer app.

These customer plans are separate from your own Free, Basic, Plus or Elite AuthlyX billing plan.

## App data and releases

Cloud variables let MyApp read shared values you can change without rebuilding. Scripts deliver verified text for your app to interpret. Release channels let different customers receive different update details, while Allowed Versions controls which running versions may connect.

## Events and operations

Webhooks send selected events to your services. App logs help you investigate events reported by customer software. Team permissions let authorized staff or resellers manage permitted work without sharing your own account credentials.

AuthlyX does not build your login screen, execute downloaded scripts, install updates or decide your product's pricing. Your application handles its own interface and business operations. Use the guides for the behaviour, SDKs for language examples, and API Reference for HTTP fields and responses.