DRO Cloud is the platform's cloud-computing product line: on-demand compute that you provision, operate, and pay for from inside the same DRO workspace you use for everything else — no external console, no separate bill. Capacity is metered to the second and settled against your Drocoin wallet.

Two ways to run compute

Virtual Machines (IaaS)Containers (PaaS)
WhatFull KVM virtual machines on Proxmox — your own OS, root SSH, persistent disk.Declarative tenant containers actuated on the fleet via the Brood engine.
Control surfaceDRO Cloud app (provision, console, telemetry, billing)./api/v2/compute REST API (script- and CI-friendly).
Best forFull OS control, stateful workloads, lift-and-shift.Stateless apps, microservices, deploy-from-image.
BillingHourly, per plan, from your Drocoin wallet.Quota-governed (count + vCPU/memory caps per tenant).

Key concepts

  • Tenant isolation — every resource is scoped to your tenant. A lookup for a resource you do not own returns not found, never another tenant's data.
  • Regions & placement — compute runs on fleet hosts in the regions allocated to your tenant.
  • Quotas — container count and total reserved vCPU/memory are capped per tenant; over-quota requests are refused before anything is created.
  • Drocoin billing — pre-fund a wallet; VM consumption is debited hourly. A VM whose wallet runs dry is automatically suspended and resumes when you top up.
  • Telemetry & audit — per-VM CPU/memory/disk/network samples plus a full activity log of every lifecycle event.

How it works

DRO Cloud is desired-state: the API node never executes on a host. You declare what you want (a VM record, or a container row); a worker materialises it on the host (Proxmox for VMs, Docker via Brood for containers); and a periodic reconciler keeps live reality matching your declaration. VM entities are stored in SurrealDB; the container CMDB is in Postgres.

Where next

© 2026 DRO Platform