Independent Roblox developer infrastructure
One command center for keys, storage, bans, logs, webhooks, and Studio-ready API tests.
Built as a premium control-plane preview for studios that run multiple Roblox experiences and need shared moderation, player intelligence, vault storage, and operational visibility.
- 6
- API modules
- 4
- pricing tiers
- 750 GB
- network vault
Developer dashboard
A live-feeling product
cockpit for the API platform.
The console uses browser-local state for the preview. Keys, selected plans, usage bars, and simulated events persist on this device until cleared.
Traffic
Request velocity
Risk queue
Moderation load
Exploit reports
47
Ban syncs
312
Economy alerts
19
Event stream
Latest API activity
Key inventory
Access scopes and vault usage
Audit logs
Moderation and API timeline
Filters
Vault usage
0 GB stored
No keys have claimed storage yet.
Buckets
Storage by product
Current plan
Studio
100 GB storage, 1M requests, 10 active keys.
API workbench
Preview modules for moderation, storage, identity, and live ops.
Each API includes a route, storage model, Lua request snippet, and mock response that matches the hosted preview endpoint.
Preview API
Requires storage
Cross-Game Ban API
Create one ban decision and enforce it across every place, universe, or group you connect to the key.
POST
/api/preview/cross-ban/check
Storage model
Ban records, appeal notes, evidence hashes
Best for
Studios with linked games
Rate profile
Burst-safe joins and checks
Pricing tiers
Preview packaging for tiny teams through full studio networks.
Prices are placeholder launch packaging. Selecting a tier updates the dashboard, key form limits, and storage math.
Roblox Studio SDK
ServerScriptService-ready preview module and endpoint tester.
The hosted mock API returns JSON from `/api/preview/...`, so Roblox Studio can hit HTTPS and validate the flow before a real backend exists.
ModuleScript
RobloxApisClient.lua
HTTP test
Preview response simulator
Key registry
Register preview keys with per-key storage allocations.
Generated keys are local placeholders. A production build would hash keys server-side, enforce scopes, and store usage in a database.
Local registry
Registered keys
Architecture track
Backend roadmap for turning the preview into a real API company.
Scoped bearer keys
Hash keys with a server secret, attach product scopes, enforce per-tier request budgets, and expose one-time key reveal on creation.
Per-key vaults
Store ban records, evidence pointers, signal batches, webhook attempts, and audit events against each registered key quota.
Server-only SDK
Use HttpService from trusted server scripts, never expose private keys in LocalScripts, and keep game-specific rules in server-owned config.
Metered upgrades
Plans can combine monthly request limits, storage quotas, retained logs, active keys, webhook routes, and support response windows.
Launch track
DNS, HTTPS, visual shell, pricing, dashboard, and mock endpoints are now staged.
- 1 Site served from the Hetzner VPS with HTTPS.
- 2 Namecheap DNS points apex and www to the VPS.
- 3 Preview `/api/preview/...` routes return JSON for Studio tests.
- 4 Next production step is real auth, database storage, and billing.