Victus Ecosystem
Victus Cloud platform architecture
How Launchpad, Victus Hub, Billing, Victus Panel, the Discord bot and Waiting Proxy divide responsibility.
architecturelaunchpadhubpanelbillingproxy
Victus Cloud is one connected ecosystem, not one monolithic dashboard. Each surface owns a different job, while shared identity and trusted integrations make the hand-offs feel continuous.
| Component | Responsibility |
|---|---|
| Launchpad / main website | Public website, documentation, sign-in entry points, onboarding and the free-server claim workflow. |
| Victus Hub | The signed-in customer home for platform-level navigation, account context, rewards and service discovery. |
| Victus Billing | Paid orders, invoices, credits, payment methods and recurring paid-service lifecycle. |
| Victus Panel | The main and only server operations panel: power, console, files, backups, databases, networking, schedules, users and free-hosting renewal. |
| Official Discord bot | Discord-side account linking, notifications, support and community automation. It does not replace Victus Panel. |
| Waiting Proxy | The managed Minecraft connection layer that wakes sleeping backends and transfers players when ready. |
Victus Panel terminology
Victus Panel is a Victus-maintained fork of Pterodactyl. That describes technical lineage and API compatibility only; customers use Victus Panel, not a separate upstream panel service.
Typical free-hosting request path
- 1A user signs in on Launchpad and submits a free-server claim.
- 2Launchpad and its backend integrations create or link the required account records.
- 3Victus Panel provisions and owns the server record, resources and free-service lifecycle.
- 4The Waiting Proxy maps the managed hostname to that server and requests wake actions through authenticated panel endpoints.
- 5The official Discord bot can deliver best-effort renewal and service notifications when the Discord identity is linked.