This guide covers operating a DRO Cloud Virtual Machine end to end. For programmatic container compute, see the Developer Guide.
Provisioning a VM
- Open DRO Cloud and pick a plan from the catalogue (vCPU, RAM, disk, bandwidth, hourly/monthly price).
- Name the VM and choose an OS image.
- Submit. The VM is created in Provisioning while Proxmox clones and boots it, then moves to Active with an allocated IP — typically under 60 seconds.
Lifecycle
A VM moves through these states:
- Provisioning — being cloned/started on the host.
- Active — running and billable.
- Suspended — paused (manually, or automatically on insufficient wallet balance). Resumes on top-up.
- Failed — provisioning error; see the activity log for the reason.
Lifecycle actions (reboot, resize, snapshot, destroy) are available from the VM surface. Every action is written to the activity log with actor and timestamp, giving you a complete audit trail.
Networking & firewall
Each VM has per-VM firewall rules: direction (inbound/outbound), protocol, port range, source CIDR, action (allow/deny), and priority. Rules are evaluated by priority; default-deny inbound is recommended, opening only the ports your service needs.
Access & console
Connect over SSH using your registered keys, or use the in-browser console (SSH / noVNC) for break-glass access. Console sessions are tracked (who connected, when) for audit.
Telemetry & monitoring
DRO Cloud samples each VM's CPU %, memory %, disk read/write, and network in/out, charted on the VM surface so you can spot saturation and right-size.
Billing
- Consumption is hourly at the plan's rate, debited from your personal Drocoin wallet.
- Each cycle produces a consumption report (hours, cost, period) and rolls into an invoice.
- If the wallet cannot cover a cycle, the VM is suspended automatically — no surprise overage. Top up to resume.
Support
Open a support ticket from the VM and it is automatically enriched with the VM's recent activity log, so the first responder has context without a back-and-forth.