Virtual servers you create as needed and scale up or down with traffic.
Overview
Create a server when you need one, add instances for busy hours and remove them afterwards. Choose a family and a size, and NVMe storage and monthly traffic come with it. Daily automatic backups and basic DDoS protection are included in every plan.
Sizing for the busiest hour leaves that capacity idle the rest of the day. Run what the hour needs and take it back afterwards.
Compute optimized suits servers that take and pass on requests; general purpose suits servers that run the app and its data together.
2–12 TB/mo
Each size comes with a set amount of monthly traffic in the plan.
Instances run on AMD EPYC processors with NVMe storage. Attach more volumes when storage runs short.
Daily automatic backups and basic DDoS protection come with every plan. There is nothing to set up again when you add a server.
Plans
The family you want depends on what the server actually runs. Every family is AMD EPYC based.
Family
Size
Throughput runs out before memory does.
Good for
Size
Cache and sessions take the memory first.
Good for
c1a · Compute optimised
c1a.xlarge
₩44,000/mo
Monthly price per instance, excluding VAT.
Work out the monthly cost of your configuration firstFeatures
01
Backups run every day. They are on for every plan without any setup.
02
Included in every plan. Nothing to configure again when you add servers.
03
Change the size while running, or add and remove instances.
04
Announce your own ASN and IP range and run the BGP session yourself. Addresses stay the same after you move.
Once the configuration is settled, create it straight from the dashboard.
Create in dashboardYes. You scale with traffic: add machines for the busy hours and take them back down once the peak passes.
You can advertise your own ASN and IP range and run BGP sessions directly, so the address your customers see stays the same even after you move.
No. Daily automatic backups and basic DDoS protection are included in every tier, so there is nothing to configure each time you add a server.
Take c1a (2 GB per vCPU) if the server mainly takes and forwards requests, and m1a (4 GB per vCPU) if the application and its data sit on the same machine.
In a Tier 3 data centre, the same facility as our colocation, so bringing in your own hardware later keeps you in the same building and the same account.
Tell us how you run today and the traffic you expect, and we will put the specification and count together.
