Lua authentication + delivery

Control who runs your scripts, and what they receive.

Claudmor handles keys, identity locks, provider flows, script storage, and place/universe routing. Claudium handles the obfuscation.

Railway Claudium backendHWID / Roblox / Discord bindingsLootLabs / Linkvertise / Boostellar
01

One workspace per account.

Every user manages their own services, keys, scripts, providers, and loader routes. Your owner key only skips reward gates.

Access control

HWID and account-bound keys with server-side verification.

Loader routing

Map PlaceId or UniverseId to the script that service should return.

Claudium

Save source per service and send it through the Claudium backend.

02

Route games without shipping multiple loaders.

One service can return different scripts for different Roblox places or universes. Place routes win first, then universe routes, then the default.

Configure loader routes
MatchIDScript
Place155615604prison.lua
Universe286090429main.lua
Default—fallback.lua

Keys stay simple.

Create, bind, expire, revoke, and reset them from the service that owns them.

Scripts stay private.

Source is encrypted at rest and the public loader never needs your service management secret.