Your stack. Your perimeter.

A server you can make your own

Root access gives you control over the guest operating system, packages, firewall and application stack. Run a single quiet service or several isolated containers. Keep your deployment reproducible so moving between hosts remains a practical option.

• SSH keys for Linux access
• A clean operating system rather than a forced application bundle
• IPv4 and IPv6 configuration documented with the order

Choose around the workload

CPU count alone does not tell the whole story. A database may need memory and predictable storage latency; a game server may care more about single-thread performance; a web application may spend most of its time waiting on a remote API. Start with the smallest sensible configuration and measure.

• Scout: lightweight services and development
• Warden: small applications and several containers
• Guardian: production applications and databases
• Vanguard: busy services and larger builds
• Apex: larger application stacks and memory-heavy jobs

Privacy starts at signup

The KoalaVPS account model is designed around an email address and a password, without routine identity-document collection. Payment and operational records still exist. No-KYC hosting reduces identity collection; it does not make a server, a blockchain payment or an internet connection untraceable.

Know what you are ordering

Check the selected resources, region, activation time, backup coverage and service terms in your order. An advertised network port is a link speed, not a promise that every destination can sustain that rate.

Monthly or annual, without a setup charge

All five VPS tiers offer monthly USD billing or an upfront payment for one 12-month period with a 30% discount compared with 12 separate monthly payments. The annual total is 12 times the listed monthly price multiplied by 0.70, rounded once to cents, with no setup fee. Check the billing start, renewal rules, cancellation cutoff and treatment of an incomplete period in your order.

Resize at a planned restart

Allow for an interruption when moving between VPS resource allocations. Verify the new allocation and check disk or image constraints before reducing a configuration. A resize is not a substitute for a backup or a tested migration plan.

A snapshot before the risky step

Check snapshot availability, retention, consistency, location and restore limitations for your order. Capture a suitable recovery point before a major change and verify the restoration procedure. Keep an independent backup because a host-dependent snapshot can share the original failure domain.

Allocation, snapshots and a recovery plan

The VPS catalogue describes pinned virtual CPU, reserved memory and local NVMe. A snapshot records a point in the virtual machine’s storage state; it does not automatically produce an application-consistent database backup or an independent copy in another failure domain. Before relying on snapshots, establish whether they are crash-consistent, how long they are retained and what happens when the host itself is unavailable.

The initial order choices

Choose one of five tiers, one of four Nordic catalogue regions and an initial Linux image. The current configurator offers Ubuntu 24.04 or 22.04 LTS, Debian 13 or 12, AlmaLinux 9 and Rocky Linux 9. Set a hostname of up to 64 characters. Administrator credentials should be generated privately or enrolled through an authenticated account process. Never include a root password in an ordinary support message.

Resizing is a change to plan

Measure memory, CPU saturation and disk usage before moving tiers. Confirm whether a resize requires a restart, whether a filesystem must be expanded and whether shrinking storage is supported. Keep a rollback or migration path for an application that cannot tolerate the interruption. The published catalogue does not imply every resource can be adjusted independently.