> 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/readme.md).

# Welcome

**Luasec** is a licensing and obfuscation platform for Luau (Roblox) script sellers. It gives you:

* A full **Luau obfuscation** stack.
* A **license key system**: HWID locked keys, expiry, pausing, banning, and key leak watermarks.
* **Server-side secrets and webhook protection** so sensitive values and Discord webhooks never ship inside your script.
* An **ad-reward system** flow (Linkvertise, LootLabs, Work.ink).
* A **Discord bot** that whitelists buyers, resets HWIDs, and delivers scripts, using your server's own roles.
* A **dashboard** with analytics.

## How it fits together

```
Seller > Dashboard > creates a project > adds a script > uploads source & builds
                                                                │
                                  (obfuscation + license guard loaded in)
                                                                ▼
End user > loadstring(HttpGet(".../loader/<scriptId>")) > with a valid key > runs
                                                                │
                          server checks key + HWID, streams the sealed build
```

* A **Project** (also called a hub) is the "director". Everything (keys, scripts, loaders) hangs off a project.
* A **Script** lives inside a project. Each time you upload source, Luasec produces a **Build** (a version) and serves it through a **loader**.
* A **Key** authorizes an end user to run your scripts. Keys belong to the project, so one key works for every script in that hub.

New here? Start with the [Quickstart](/getting-started/quickstart.md).


---

# 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/readme.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.