Your first $5 top-up doubles to $10 — one-time, for every new account. Get Started
Krova CloudKrova Cloud

Cubes

Create, size, connect to, and manage Cubes — and understand how running and sleep billing works.

A Cube is a lightweight virtual machine running on dedicated cloud infrastructure. You get full root access and a real Linux environment — run Docker, databases, web apps, build agents, anything you would on a VPS.

Creating a Cube

Create a Cube from your space dashboard. You choose:

  • vCPUs, RAM, and disk — the resources allocated to the Cube. RAM and disk are dedicated (not oversold).
  • Image — the operating system to boot.
  • SSH key — your public key, written to the Cube at boot.

The Cube provisions and boots in seconds. Available sizes and the per-hour cost are shown in the create form so you always know what you'll pay.

Connecting

Every Cube has an SSH endpoint shown on its page. Connect with the key you added at creation:

ssh -p <port> root@<cube-host>

To expose other services, add TCP port mappingsfrom the Cube's networking tab — each maps a public host port to a port inside the Cube, with an optional IP allow-list. For HTTP/HTTPS apps, a custom domain is usually the better fit.

Resizing

You can change a Cube's vCPU and RAM, and grow its disk, after creation. Resizing applies the new resources to the running Cube; metered billing simply continues at the new size.

Sleep & wake

Cubes have two main states beyond running:

  • Sleeping — the Cube is stopped but its disk is preserved. You can put a Cube to sleep manually, and a space whose balance reaches zero has its Cubes auto-slept (no data loss).
  • Running — wake a sleeping Cube any time (top up first if the balance is zero) and it resumes from its saved disk.

How billing works

Billing is prepaid, charged against your space's credit. Rates are quoted per hour, but usage is metered and billed by the minute — no rounding up to the hour:

  • A running Cube is billed for its compute (vCPU + RAM) and its disk.
  • A sleeping Cube is billed only for its disk storage — much cheaper than running, so sleeping is the right way to pause a workload you want to keep.
  • Unexpected shutdowns (a crash, an in-guest shutdown, a host reboot) are never charged compute for the partial hour — you only pay for time the Cube actually ran.

Snapshots & backups

Cubes can be snapshotted and backed up to off-host object storage, and restored, cloned, or redeployed from those copies. Automatic snapshot cadence and retention depend on your tier; you can also take manual snapshots and pin the ones you want to keep.

Next steps