Getting started
Create and connect your account
Select Continue with Discord. Discord handles the password step; Infinite Studios receives your stable account ID, username, avatar, server membership, and role IDs. Join the official server if access requires membership.
Order a project
Choose a real package from the storefront or use the quote builder for custom work. Add a clear brief, select an available payment route, and keep the generated order ID.
Track an order
Open Customer Dashboard → Projects. Every order page shows its payment state, current project stage, assigned developer when set, estimated completion when available, customer-visible updates, and delivery link.
Discord bot delivery
Permissions
Invite delivered bots with only the permissions required by their documented features. Administrator access should never be the default unless the complete feature set truly requires it.
Configuration
Keep Discord bot tokens and API keys in server-side environment variables. Never paste them into support chats, screenshots, browser code, or public repositories.
Handoff
A completed bot order should include the agreed source or deployment method, setup instructions, required variables by name, and a clear scope of included support.
Websites, domains, and OAuth
Website delivery
Confirm the production domain, hosting owner, deployment target, and post-launch support scope in writing before delivery.
Domains and DNS
DNS changes can take time to propagate. Preserve unrelated MX and verification records, and change only the records required by the documented host.
Discord OAuth
The exact callback route must match the application code and Discord Developer Portal. Production redirects use HTTPS. Never place the client secret in frontend code.
Infinite Studios Cloud
Prepare a bot ZIP
Upload a ZIP containing one project at the archive root. Node.js bots require package.json and a safe start script. Python projects require a supported entrypoint. Do not include node_modules, virtual environments, tokens, or private keys.
Environment variables
Add secrets through Encrypted Variables. Values are encrypted and are never returned by customer-facing APIs after storage. Variable names may be shown; values are not.
Start, logs, and restart
Start, Stop, Restart, and Redeploy remain locked until the isolated Linux runner is connected. After a real runner accepts Start, the desired state remains RUNNING after the browser closes until you choose Stop or Delete.
Support and disputes
Open a ticket
Use Customer Dashboard → Support and choose the correct department. Order references are requested only for Order Support or Billing when relevant.
Payment or order dispute
Do not share card numbers, passwords, tokens, login codes, or QR codes. Provide the order ID and a safe transaction reference through the protected support route.
Report a problem
Use Report a Problem for abuse, security, or trust issues. Include observable facts and safe evidence links. Do not post private evidence publicly.