Română Cloud servers
Virtual machines on shared hardware, billed by the hour. This page covers how to start one and, in as much detail as we can give, what it will not let you do.
What it is
A cloud server is a virtual machine with its own vCPU, RAM and NVMe-backed disk, running an operating system image you choose. You get full root access over SSH. Billing is hourly, charged against your prepaid balance, and you can resize, snapshot, rebuild or destroy the machine yourself from the panel or the API.
Getting started
- Create an account and confirm your email address.
- Add funds. A deposit of at least €10 is required before any server can be provisioned, including a free-tier one.
- Open Cloud in the panel, choose a package, a region and an operating system image, and add an SSH key.
- Create the server. Provisioning normally completes in under a minute, and the panel shows the IP address when it is ready.
- Connect over SSH as root using the key you selected. Password login is disabled on the images by default.
The same steps are available through the REST API and the CLI; the API quickstart walks through creating a server in one call.
Limits
These apply per account. Where a limit can be raised, it is raised by support on request, not from the panel.
| Limit | Value | Can support lift it? |
|---|---|---|
| Servers per account | 5 | Yes, on request |
| Public IPv4 addresses | 5 | Yes, on request |
| Private networks | 5 | Yes, on request |
| Attached volumes | 5 | Yes, on request |
| Local disk per server | 30 GB | Yes, on request |
| Network storage per server | 100 GB | Yes, on request |
| Outgoing SMTP | Blocked by default, on every account | Yes, tell us what you plan to send |
Outgoing mail
Outgoing SMTP (sending mail from the server) is blocked by default on every new account, free and paid. Contact support with what you plan to send and we open it.
This is not a free-tier restriction. It applies to paid accounts too, and it is separate from the free-tier port rules below. Lifting one does not lift the other.
The free tier
Free tier limits: inbound traffic is allowed only on TCP 22, 53, 80, 443 and UDP 53, plus ICMP. All other inbound ports are closed and the firewall cannot be changed on a free server. One free server per customer, no High Availability, no extra firewall rule sets. Paid plans have none of these restrictions: every port is yours and the firewall is fully editable.
Concretely: a free server accepts inbound connections only on TCP 22, 53, 80, 443 and UDP 53, plus ICMP. Everything else is dropped, and the rule set that does the dropping is read-only, so you cannot open a port yourself while the server is on the free tier.
Support can unlock firewall control for your account. Note what that does and does not do: unlocking hands the firewall back to you, it does not open anything. The server keeps its existing rules and its default-deny policy, and you then create your own rule set and apply it. We do not open ports on your behalf, because a server that was working while closed must not suddenly become reachable.
What happens if your balance runs out
- Servers are suspended 2 days after the balance goes negative. A suspended server keeps its disk and its IP address but does not run.
- They are destroyed 7 days after that point if the balance has not been topped up.
- A final warning email goes out 2 days before anything is destroyed.
- Destruction is not recoverable. The disk is deleted with the server.
What needs support
- Raising any of the quotas in the table above.
- Unblocking outgoing SMTP.
- Unlocking firewall control on a free-tier server.
- Restoring a server after destruction. This is not possible, which is why the warning email matters.
Where to go next
Something here still not clear?
If a limit on this page surprised you, tell us. That is a documentation bug and we fix it.