FlareKey Documentation

FlareKey is the licensing and delivery layer for protected Lua. Register a script once, hand out license keys, and let the runtime API decide who receives real code and when. These pages cover the object model, the runtime and dashboard APIs, FlareFuscator presets and macros, reward-link integrations, and the error codes you will see along the way.

Getting Started

• Getting Started - FlareKey sits between your customers and your protected Lua. Instead of shipping raw source, you register a script once, hand out license keys, and let the runtime...
• Plan Limits - Every workspace runs under a plan that sets four ceilings: how many services you can create, how many active license keys can exist at once, how many runtime API...

FlareFuscator

• Overview - What FlareFuscator protects, what it does not, and the limits to design around.
• Macros - Compile-time values, protected-literal directives, function controls and development-only code.

API

• API Overview - API keys, how they differ, what is safe to ship, and the limits that apply.
• API Usage - Every runtime and dashboard endpoint with its request, response and error codes.

Integrations

• Integrations - Connect reward-link providers and use them as checkpoints on a reward.
• Discord Bot - The bot process is a separate codebase from this server - FlareKey only exposes the data for it.

Support

• Obfuscation History - History lets you re-download a recent protected build without re-running it, but it is deliberately minimal: only VM-preset outputs are kept, only for a short window,...
• Error Codes - Every rejected request returns a short machine-readable code alongside an HTTP status. Match on the code, not the human-readable message, since messages may change....