A real Linux server. No public IP to scan.

Your Cube reaches the internet completely normally — apt and npm installs, Docker pulls, outbound API calls and webhooks all work — and your sites and APIs are reachable worldwide over HTTPS. What it deliberately does not have is an inbound address of its own, and that is a security feature rather than a missing one. Unlike a typical VPS, where every instance is handed a public IP the whole internet can scan and probe, a Cube lives on a private network: nothing reaches it from outside unless you explicitly map a port, and every port mapping can be locked to an IP allowlist. Web traffic on your custom domains enters through Krova Cloud's own managed ingress tier, which terminates HTTPS and forwards to your Cube over an internal, mutually authenticated connection — so the machine running your app is never addressed directly from the internet.

Bandwidth is unmetered: Krova Cloud does not bill per gigabyte and does not set a monthly transfer allowance, so a traffic spike cannot produce a surprise invoice the way per-GB egress does at the hyperscalers. Provider-grade DDoS mitigation is included, and there is no bandwidth penalty if you are attacked. The honest caveat, which is in our Acceptable Use Policy rather than buried: the network is shared, so we reserve the right to rate-limit an individual Cube where sustained traffic would threaten host stability or other customers, and workloads whose whole purpose is consuming bandwidth — public file mirrors, torrent seedboxes, large-scale media relays — need prior written approval. Normal, well-behaved use of a web app, API, database or game server is simply not something we meter.

Yes, and you can have it preinstalled. Cubes are full virtual machines with their own kernel, so Docker, Podman, or anything else you would run on a regular Linux server works normally. Two of the four images — Ubuntu 24.04 + Docker and Debian 13 + Docker — ship with Docker Engine and the Compose plugin already installed from Docker's official repository and enabled at boot, with your login user in the docker group so you do not need sudo. Pick a plain image instead if you would rather install it yourself.

Cube shuts down gracefully and its disk is kept exactly as you left it — nothing on it is lost. Compute charges (vCPU + RAM) stop immediately; only the disk component of the Cube's hourly rate continues, since the rootfs still occupies host disk. Starting it again works just like powering on any server.

No. Krova Cloud is prepaid pay-as-you-go — there's nothing to subscribe to. You load credit whenever you like and it's drawn down by the minute while your Cubes run, and stopped Cubes and backups pay only for the disk they keep. Add a card to enable one-click top-ups and optional auto-recharge (we top you back up when your balance gets low). Tiers (which set how many Cubes you can run at once, how many backups you keep, and how often snapshots are taken) unlock automatically as you spend — they're limits, not bills, and cost nothing. Cube size is never gated: every tier can run up to 16 vCPU, 32 GB RAM and 100 GB disk. Need more headroom? Email support and we'll review your use case and lift your limits where it makes sense.