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

# Quickstart

This takes you from zero to a running, licensed script in about five minutes.

## 1. Sign in

Open the dashboard and sign in with Discord.

<figure><img src="/files/tStTLITRHZSIcJ5sZt1u" alt="" width="349"><figcaption></figcaption></figure>

## 2. Create a project

A **project** (hub) is the container for your keys, scripts, and loaders.

1. Go to **Projects > Create project**.
2. Give it a name, for example `Fluffy Hub`.

<figure><img src="/files/xXcrz3P9uuD8wm6IGmnd" alt=""><figcaption></figcaption></figure>

## 3. Add a script and build it

1. Open your project and go to **Scripts > New script**.
2. Paste your Luau source into the build panel and press **Obfuscate & set active**.

Luasec obfuscates the source, bakes in the license guard, and creates a **build** (version). Every rebuild produces a new version. The newest becomes the active build the loader serves.

```lua
-- your source, before Luasec touches it
print("Hello from my script!")
print("Running:", SEC_ScriptName, "v" .. SEC_ScriptVersion)
```

<figure><img src="/files/CKiS3Tu5xfU2Z6cojAJk" alt=""><figcaption></figcaption></figure>

## 4. Mint a key

Keys authorize end users. In your project:

1. Go to **Keys > Mint**.
2. Choose how many, an optional expiry, and an optional note or Discord ID.

Copy the key(s) now. The raw value is shown once.

## 5. Ship the loader

Give your users this snippet, filling in their key:

```lua
script_key = "" --your key here
loadstring(game:HttpGet("https://api.luasec.org/loader/<SCRIPT_ID>"))()
```

You'll find the exact snippet (with your script's ID already filled in) on the script page.

{% hint style="warning" %}
The loader URL is keyed by the **script's** public ID, not the project ID. Copy it from the script page's **Loader** box so you always get the right one.
{% endhint %}

That's it. When a user runs the snippet with a valid, HWID matching key, the server streams the sealed build and it executes.

* Read license data at runtime: [Runtime variables](/protecting-your-script/runtime-variables.md)
* Hide a webhook or secret: [Webhook protection](/protecting-your-script/webhook-protection.md), [SECRET()](broken://pages/IHs3JdfQXluuu3DPQgXL)
* Let users earn a key with ads: [Ad rewards](/licensing/ad-rewards.md)
* Automate whitelisting from Discord: [Discord bot](/discord-bot/setup.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/getting-started/quickstart.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.