UpCloud Explained: Cloud Servers, MaxIOPS Storage, and Zones
How UpCloud is organised: accounts and sub-accounts, zones, Cloud Servers and MaxIOPS block storage, private networking, managed databases and Kubernetes, and how hourly billing and prepaid credit work.
UpCloud is a Finnish infrastructure provider that sells cloud servers, storage, networking and managed services from its own data centres in Europe, North America and Asia Pacific. It sits in the same category as DigitalOcean, Vultr and Hetzner: straightforward virtual machines with a clean control panel and API, without the sprawl of a hyperscaler. This guide covers how an UpCloud account is organised, how zones work, what the core services are, where MaxIOPS storage fits, and what to check on billing and security before you deploy.
Accounts, sub-accounts and API access
An UpCloud account is a single billing entity. Inside it you create sub-accounts, which are additional logins with their own credentials and a permission set that you control. A sub-account can be limited to specific servers, storage or networks, restricted to the control panel only, or granted API access. This is how teams separate a developer who deploys servers from a finance user who only needs invoices.
The control panel is the web UI where most people start. Everything it does is also available through the UpCloud API, the upctl command-line tool and an official Terraform provider, so an environment can be defined as code from the first server. API access is per login and can be restricted to trusted IP addresses, which is worth turning on as soon as you create credentials for automation.
Two-factor authentication is available in account settings. Enable it on the main account and on any sub-account that can create or delete resources.
Zones: where servers run
UpCloud calls each data centre location a zone and identifies it with a short code such as fi-hel1, de-fra1, uk-lon1, nl-ams1, us-nyc1 or sg-sin1. At the time of writing the zone list covers Helsinki, Amsterdam, Frankfurt, London, Madrid, Warsaw, Chicago, New York, San Jose, Singapore and Sydney, with the current list published on the UpCloud data centres page.
A few practical rules follow from the zone model. Servers and their storage live in one zone; you can clone storage to another zone but you cannot live-migrate a running server between them. Private networks (SDN networks) are zone-scoped, so a two-zone deployment talks over the public internet or over a router with private connectivity between zones. Pick the zone closest to your users, then keep related services together in it.
Cloud Servers and MaxIOPS storage
The main product is the Cloud Server, a KVM-based virtual machine. UpCloud sells fixed plans grouped by purpose (general purpose, high CPU, high memory, and smaller developer plans) and also lets you build a custom configuration by choosing CPU cores and memory independently. Fixed plans bundle storage and a monthly transfer allowance; custom configurations are billed per component. Details are on the Cloud Servers product page.
MaxIOPS is UpCloud’s name for its high-performance block storage tier. It is the default disk type for cloud servers and is the reason the provider tends to show up in discussions about database and I/O-heavy workloads. A lower-cost HDD-backed tier exists for bulk data that does not need the same throughput. Storage devices are separate objects from servers: you can detach a disk, attach it to another server in the same zone, resize it, and take snapshots or scheduled backups of it.
Images and templates
Servers are created from public templates (current Linux distributions and Windows Server), from your own custom templates saved from an existing disk, or from a CD-ROM image you upload. Custom templates are the fastest way to standardise a base image with your SSH keys, packages and firewall rules already applied.
| Resource | What it is | Scope |
|---|---|---|
| Cloud Server | KVM virtual machine, fixed plan or custom configuration | Zone |
| MaxIOPS storage | High-performance block storage attached to servers | Zone |
| Object Storage | S3-compatible buckets for files and backups | Region |
| SDN private network | Isolated layer-2 network between your servers | Zone |
| Floating IP | Public address you can move between servers | Zone |
Networking, managed databases and Kubernetes
Each server gets a public IPv4 address and, if enabled, IPv6, plus a utility network for traffic inside UpCloud. SDN private networks add isolated networks with addressing you choose, and a router object connects those networks to each other or, with a NAT gateway, to the internet. A per-server firewall filters inbound and outbound traffic before it reaches the operating system, which is separate from any firewall you run inside the VM. Floating IPs let you fail a public address over to a standby server.
Beyond raw servers, UpCloud offers Managed Databases (PostgreSQL, MySQL, Redis-compatible caches and OpenSearch), a Managed Load Balancer, S3-compatible Object Storage, and Managed Kubernetes. Managed databases run on UpCloud infrastructure with backups, updates and failover handled by the provider, and they can be placed on a private network so they are never exposed publicly.
Typical workloads are what you would expect for this class of provider: web and application servers, PostgreSQL or MySQL backends, container hosts and Kubernetes clusters, CI runners, and staging environments that mirror production at lower cost. The fast storage tier makes it a reasonable home for self-hosted databases that would otherwise need a larger instance elsewhere.
Billing, credit and account limits
UpCloud bills by the hour with a monthly cap for each resource, so a server that runs all month costs the fixed monthly price and one that runs a day costs a day. Usage is deducted from account credit: you add funds by card or other supported methods, and charges draw from that balance. Prepaid credit is the normal way to run an account, and low-balance notifications are available in the control panel.
New accounts carry resource limits on server count, CPU and memory that rise on request through support once there is a payment history. Trial credit terms are set by UpCloud and change over time, so treat any promotional amount as subject to the provider’s current rules. On the CloudAccountHub product page the UpCloud listing is labelled $500 Credit; the label describes the listed credit amount and nothing further.
Like every provider, UpCloud requires acceptable-use compliance. Outbound mail, port scanning and traffic that generates abuse reports are handled under its terms of service; if you need to send email from a server, use an authenticated relay such as a transactional email service and keep list hygiene in order.
Where to go next
- See the listed variant on the UpCloud account product page.
- Compare it with a close competitor in UpCloud vs Vultr.
- Read SSH keys for cloud servers before you create your first template.
- Understand how promotional balances behave in How cloud credits work.
- Learn how to structure test environments in Building staging and test environments in the cloud.
- Browse every guide in the Cloud Library.