> For the complete documentation index, see [llms.txt](https://docs.luasec.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luasec.org/getting-started/concepts.md).

# Core concepts

A quick look of the things you'll work with.

## Project (hub)

 A project/hub (we call it a project but feel free to say hub) owns your scripts, keys and loader. Keys are scoped to the **project**, so one key works for every script inside that hub.

Each project has:

* A **name** (display only).
* A **public ID:** appears in loader/ad URLs and it's safe to share.

## Script

A protected script inside a project. A script has its own **public ID**, which is what the loader URL points at:

```
https://api.luasec.org/loader/<script-public-id>
```

## Build (version)

Every time you upload source, Luasec produces a **build** which is an obfuscated version with the license guard. The newest build is the **active** one the loader serves. Rebuilding is how you push an update.

{% hint style="info" %}
Existing builds are **not** retroactively upgraded when the platform changes. If a new obfuscation feature ships, rebuild your script to get it.
{% endhint %}

## Key

A license key authorizes an end user. Keys carry:

* **Status:** `active`, `paused` or `banned`.
* **HWID:** bound to the first device that uses it.
* **Expiry:** optional; `null` means never.
* **Note** and **Discord ID:** optional metadata, exposed to your script as runtime variables.
* **isPremium:** a premium/freemium/whitelist flag, exposed as `SEC_IsPremium`.
* **Executions:** a running count, exposed as `SEC_ExecutionCount`.

See [Keys](/licensing/keys.md).

## Loader

The tiny bootstrap your users run. It performs the handshake, proves the key + HWID, and streams the sealed build. You never distribute the build directly, only the loader snippet.

## Subscription plan

Your account is on **Free**, **Pro** or **Max**, which sets your limits (projects, scripts, keys, monthly builds) and whether you get an API key + Discord bot. See [Subscriptions](broken://pages/qQqhrwYoWMdbe8o9oZCm).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.luasec.org/getting-started/concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.