Continuous runtime design
Once started on the isolated runner, bots stay active after logout and browser close.
Host and manage Discord bots through a secure control plane designed for continuous operation, automatic recovery, encrypted configuration, and real infrastructure visibility—with no browser dependency or renewal countdown.
No hourly renewals. No keep-alive browser tab. Once the isolated runner accepts Start, the desired state stays RUNNING until you stop or delete the deployment. Runtime activation still requires the Infinite isolated container network.Infinite Studios Cloud separates the public website, control API, archives, secrets, and customer workloads into deliberate security boundaries.
Once started on the isolated runner, bots stay active after logout and browser close.
There is no time lease to refresh. The RUNNING state persists until the owner stops or deletes it.
Desired state, bounded restart attempts, and backoff are built into the runner contract.
Environment values are AES-GCM encrypted and never returned to the browser after storage.
Bounded, redacted runtime events with retention and ownership checks.
Upload, configure, start, stop, restart, redeploy, and delete from one workspace.
Access is tied to a stable Discord ID and verified Infinite Studios membership.
CPU, memory, restart count, status, and uptime flow from the isolated runner.
Strict archive size, path, file-count, type, and extraction limits run server-side.
Every Discord account receives a backend-enforced maximum of two bots.
The Infinite Studios website handles identity and control. A separately deployed runner pulls validated archives into restricted, non-root containers with CPU, memory, disk, process, log, and restart limits.
Open your workspace ↗Connect Discord, upload a validated ZIP, configure encrypted variables, and keep the deployment registered until you choose to remove it.
Start hosting ↗