Key quota: — · API: Live
Generate keys
Create license strings your app accepts at login. Resellers spend keys from the per-app balance in the dropdown (set under Admin → Users & grants). Developers can also create applications here; apps you own use unlimited generation in this panel.
Pick the product, how many keys, and whether they expire. Generated keys appear in the box below — copy them to your customer.
Which product these keys unlock. The label shows how many keys you can still generate.
How many distinct keys to create in one go.
Lifetime = no end date. Temporary = expires after the number of days below.
1 = single PC/device bind (typical). Higher = that many activations before the key is exhausted. 0 may mean unlimited — check your bot’s rules.
Only used when type is Temporary. After this many days from creation, the key stops working.
All keys
Inspect or remove keys for one application at a time. Use Load after changing the app — the table does not auto-refresh.
Deleting a key immediately prevents new logins with it. Existing sessions may depend on your app’s behavior.
Keys are stored per product — choose the app first, then load.
| Key | Expires | Uses |
|---|
App accounts
End-user username + password pairs your application checks — not the same as signing into this web panel. Use this when your product uses account login instead of (or as well as) license keys.
Creates a customer login for the selected app. Set lifetime or a time limit with Expiry and Amount.
Lifetime never ends. Days / Hours use the amount field as the length.
Number of days or hours until the account expires (ignored for lifetime).
Load accounts for one app, then ban or delete as needed.
| User | Expires | Ban |
|---|
HWID & expiry
HWID ties a key or account to one machine so it can’t be shared freely. Reset when a customer changes PC. Extend adds time to a temporary key or account. Check shows current expiry without changing anything.
Clears the machine bind for this key so it can be activated on a new device.
Paste the full key string your customer was given.
Same as above, but for username/password logins under App accounts.
Adds more days or hours to a temporary key or account. Lifetime keys don’t need this.
First row = license key. Second row = app account (pick app + username).
Read-only: shows when a key or account expires (or if it’s lifetime).
Results appear here.
Downloads
Panel users: download .rar builds for apps you have access to. Customers without a panel login can use a valid license key for the product they purchased.
Archives: {app_name}.rar (or slug-matching name) in src/downloads/rars. Env AUTH420_DOWNLOADS_RARS_DIR sets the folder.
Sign in to see your downloads.
Same flow as the public landing section: key must be valid for the selected app and a matching archive must exist on the server.
Use key OR username+password. If needed, product above helps resolve account app.
Bot site
Public /home page: invite OAuth, support link, FAQ, and full slash command tables. Step-by-step topics: run /tutorial in Discord. Developers: /api/info for JSON routes; /api/dashboard/assets/api-docs.html for the auth API manual.
Administration
Manage who can sign into this website and how many keys they may generate per app. Customer-facing app accounts and keys are managed in the other sections.
Adds another login for this panel (e.g. a reseller). Admin = full access including this page.
Yes = Admin tab and all apps. No = limited to grants and/or own apps (see Developer).
Yes = can create new applications from Generate keys (stored in SQLite, same as Discord). Can still get grants for reseller-style quotas on other apps.
Grants = which apps this panel user may generate keys for, and how many. Leave balance empty for unlimited generation on that app.
Use the action buttons on each row to add or edit app access without making everyone an admin.
| ID | User | Discord ID | Role | Grants | Actions |
|---|