---
title: "Server prerequisites"
slug: "server-spec-vpc"
updated: 2026-10-08T06:53:40Z
published: 2026-10-08T06:53:40Z
canonical: "guide.ncloud-docs.com/server-spec-vpc"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Server prerequisites

Available in VPC

Review supported specifications, service limits, and pricing information before using Server.

## Cloud specifications

Server supports the following cloud environment specifications:

| Item | Specification |
| --- | --- |
| Region | Korea, Singapore, and Japan |
| Platform | VPC |
| Language | Korean, English, and Japanese |

              Note

              

For more information about the VPC environment, see [VPC overview](https://www.ncloud.com/product/networking/vpc) on the NAVER Cloud Platform portal. To verify VPC support for specific services, see [Ncloud user environment guide](/docs/en/environment-environment-1-1).

## Server specifications

Check the server type and image provided by NAVER Cloud Platform before creating a server. NAVER Cloud Platform provides servers from g1 to g3.

- g1 server: Versions developed when the service was initially provided. They are the XEN hypervisor-based servers where you can use HDD and SSD-based storage.
- g2 server: A more advanced server than the g1 when it comes to the CPU and network, thus making its performance better and more stable. They are the XEN hypervisor-based servers where you can use HDD and SSD-based storage.
- g3 server: A server based on KVM hypervisor introduced for higher performance compared to the current servers. Unlike g1/g2 servers, g3 servers have distinct compatibility for servers, storage, snapshots, and server images. Available storage volume types include FB1/2 (Fixed Block Storage) and CB1/2 (Common Block Storage).

              Note

              

- Resources with different hypervisors are not compatible with each other.
- Currently, g3 servers are supported only in the Korea, Singapore, and Japan Regions.

## Overview by hypervisor

Hypervisor is a concept added to categorize the compatibility of resources (services) provided by NAVER Cloud Platform. NAVER Cloud Platform provides XEN and KVM hypervisors, and the following resources (services) are classified by hypervisor compatibility:

| Hypervisor | Server generation | Server type | Server image (OS) | Storage volume type | Snapshot | My server image |
| --- | --- | --- | --- | --- | --- | --- |
| XEN | g1, g2 | Mirco, Standard, High-Memory, High-CPU, CPU-Intensive, GPU | XEN-based server image | HDD, SSD | XEN-based snapshot | XEN-based My server image |
| KVM | g3 | Mirco, Standard, High-Memory, High-CPU, CPU-Intensive, GPU, SFC | KVM-based server image | FB1, FB2 CB1, CB2 | KVM-based snapshot | KVM-based My server image |

- Server
- Storage (Block Storage)
- Snapshot
- My server image (Server Image)

              Caution

              

Resources (services) with different hypervisors are not compatible with each other. For example, you cannot create a server based on KVM from My server image created with a server based on XEN.

### Characteristics of KVM-based servers

Unlike XEN-based g1 and g2 servers, KVM-based g3 servers have the following characteristics:

- g3 server spec codes do not include storage information (e.g., B50, B100).
- g3 server names exclude disk information. Example: 2 vCPUs, 4 GB memory.
- As for g3 servers, the storage information is excluded from the existing OS SW code.

The following is the performance QoS by specification for KVM-based g3 servers:

              Note

              

The maximum possible performance values are displayed for the network, storage IOPS, and storage throughput.

#### Standard

| CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
| --- | --- | --- | --- | --- |
| 2 | 8 | 1 | 81 | 4,725 |
| 4 | 16 | 1 | 144 | 7,875 |
| 8 | 32 | 2 | 288 | 15,000 |
| 16 | 64 | 2 | 594 | 25,000 |
| 32 | 128 | 5 | 850 | 40,000 |
| 48 | 192 | 5 | 1,188 | 70,000 |
| 64 | 256 | 10 | 1,188 | 100,000 |

#### High Memory

| CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
| --- | --- | --- | --- | --- |
| 2 | 16 | 1 | 81 | 4,725 |
| 4 | 32 | 2 | 144 | 7,875 |
| 8 | 64 | 5 | 288 | 15,000 |
| 16 | 128 | 5 | 594 | 25,000 |
| 32 | 256 | 10 | 850 | 40,000 |
| 48 | 384 | 10 | 1,188 | 70,000 |
| - | - | - | - | - |

#### High CPU/CPU Intensive

| CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
| --- | --- | --- | --- | --- |
| 2 | 4 | 1 | 81 | 5,250 |
| 4 | 8 | 1 | 144 | 7,875 |
| 8 | 16 | 1 | 288 | 15,000 |
| 16 | 32 | 2 | 594 | 25,000 |
| 32 | 64 | 2 | 850 | 40,000 |
| 48 | 96 | 2 | 1,188 | 70,000 |
| 64 | 128 | 5 | 1,188 | 100,000 |

#### GPU - A100

| GPU (EA) | GPU Memory(GB) | CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
| --- | --- | --- | --- | --- | --- | --- |
| 8 | 640 | 56 | 1,960 | 10 | 1,188 | 100,000 |

#### GPU - H100

| GPU (EA) | GPU Memory(GB) | CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
| --- | --- | --- | --- | --- | --- | --- |
| 8 | 640 | 120 | 1,960 | 10 | 1,188 | 100,000 |

#### GPU - L4

| GPU (EA) | GPU Memory(GB) | CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | 24 | 4 | 48 | 2 | 144 | 7,875 |
| 1 | 24 | 8 | 48 | 2 | 288 | 15,000 |
| 2 | 48 | 8 | 96 | 2 | 288 | 15,000 |
| 2 | 48 | 16 | 96 | 2 | 594 | 25,000 |
| 4 | 96 | 16 | 192 | 5 | 594 | 25,000 |
| 4 | 96 | 32 | 192 | 5 | 850 | 40,000 |

#### GPU - L40S

| GPU (EA) | GPU Memory(GB) | CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | 48 | 16 | 96 | 2 | 594 | 25,000 |
| 1 | 48 | 32 | 96 | 2 | 850 | 40,000 |
| 2 | 96 | 32 | 192 | 5 | 850 | 40,000 |
| 2 | 96 | 64 | 192 | 5 | 1,188 | 100,000 |
| 4 | 192 | 64 | 384 | 10 | 1,188 | 100,000 |
| 4 | 192 | 128 | 384 | 10 | 1,188 | 100,000 |

### Server spec code

Server spec code is a code developed for viewing the specifications of a server at a glance. You can find it when creating servers or checking the information of a created server. The indication rules of the code are as follows:

| mi | 1 | - | g3 | a | (-h50) |
| --- | --- | --- | --- | --- | --- |
| Server type | Number of vCPUs | - | Server generation | CPU type | Storage volume type/capacity |

| Item | Description |
| --- | --- |
| Server type | - mi: Micro server - cp: Compact server - s: Standard server - m: High Memory server - c: High CPU server - ci: CPU Intensive server |
| Number of vCPUs | Number of CPU cores (number of Hyperthread on criteria for Bare Metal Server) |
| Server generation | - g1: 1st generation server - g2: 2nd generation server - g3: 3rd generation server |
| CPU type | - Blank: Intel - a: AMD |
| Storage volume type/capacity | Default storage information for g1/g2 servers only - h: HDD storage - s: SSD storage - GB as the capacity unit |

              Note

              

The number of vCPUs and the memory ratio are fixed in accordance with the server type, so you can know the server specifications.

| Server type | vCPU (count): Memory (GB) ratio | Example |
| --- | --- | --- |
| Standard | 1:4 | s2: 2 vCPUs, 8 GB memory |
| High Memory | 1:8 | m4: 4 vCPUs, 32 GB memory |
| High CPU, CPU Intensive | 1:2 | c16 or ci16: 16 vCPUs, 32 GB memory |

### Server types provided

The server types provided by NAVER Cloud Platform are as follows:

              Note

              

Currently, g3 servers are supported only in the Korea, Singapore, and Japan Regions.

| Type | Supported Regions | Characteristics | Recommended use cases |
| --- | --- | --- | --- |
| Standard | Korea, Singapore, and Japan | Balanced memory-to-vCPU allocation ratio to provide services suitable for a wide variety of workloads in order to provide highly versatile performance. | A general web service or database server. |
| High Memory | Korea, Singapore, and Japan | Provides services suitable for memory-intensive workloads such as large data processing. | High performance database server. |
| High CPU | Korea, Singapore, and Japan | Provides a higher vCPU-to-memory ratio for computing-intensive workloads. | Scientific modeling. |
| Micro | Korea | - Only 1 server available per account. - For trial use only. Availability and performance are not guaranteed. - 1 year of free service starting on the month when registering the initial payment method upon new subscription. - For more information about the month of initial payment registration, see [**My Account** > **Manage billing information and expense** > **Manage billing and payment** > **Manage payment information**](https://console.ncloud.com/billing/paymentInformationManagement) in the console. | Trial server. |
| CPU Intensive | Korea | Equipped with a high-performance CPU, optimized for tasks that require a lot of computation. | - Machine/deep learning processing server. - High-performance web server. - Video encoding. |
| GPU | Korea, Singapore, and Japan | Servers equipped with GPUs, suitable for parallel processing like big data analysis and machine learning. | - Image processing. - Rendering. - Scientific computing. - Machine learning. |
| Bare Metal Server (general) | Korea, Singapore, and Japan | Provides high-performance physical server that can be independently used in a cloud format. | - Large scale game service. - AI task servers including deep learning and natural language processing. - Suitable for processing/analyzing large-scale data. |
| Bare Metal Server (A100) | Korea | Provides high-performance physical server that can be independently used and specialized for AI, data analysis, and HPC in a cloud format. | - Large scale game service. - AI task servers including deep learning and natural language processing. - Suitable for processing/analyzing large-scale data. |

### Available services by server type

The services available for each server type are as follows:

| Server type | Add storage | Change storage size | Use SSD storage | Use Auto Scaling | Use network interface |
| --- | --- | --- | --- | --- | --- |
| Server | Micro, GPU | O | O | O | X | X |
| Bare Metal Server | X | X | O | X | O |

              Note

              

SSD storage provided in Bare Metal Servers refers not to Block Storage SSD but to Local SSD Storage.

              Caution

              

- Some GPU Servers come with high-performance local storage by default, which cannot be changed (added or deleted).
- High-performance local storage is non-persistent, so data is deleted (by cryptographic erasure) when the instance is stopped or fails.
- Local storage is not backed up and cannot be recovered. Make sure to store important data separately in external storage that supports permanent retention, such as Block Storage or Object Storage.

### Storage available by server type

The storages available for each server type are as follows:

| Server | Storage |
| --- | --- |
| Server | Standard-g3 | FB1, FB2, CB1, CB2 |
| High Memory-g3 |
| High CPU-g3 |
| Micro-g3 |
| High Memory-g2 |
| High CPU-g2 |
| CPU Intensive-g2 |
| GPU |
| Bare Metal Server | - |

### Server-related resource limits

Server-related resources can be used within the following limits:

| Resources | Default | Description |
| --- | --- | --- |
| Number of servers | It differs depending on the server type. For more information, see [Server creation limit by server type](/docs/en/server-spec-vpc#%EC%84%9C%EB%B2%84%ED%83%80%EC%9E%85%EB%B3%84%EC%84%9C%EB%B2%84%EC%83%9D%EC%84%B1%EC%88%98%EC%A0%9C%ED%95%9C). | If the limit needs to be increased, see [FAQs](https://www.ncloud.com/support/faq/all/3178) and contact [Customer Support](https://www.ncloud.com/support/question/service?parentCode=O2O_SVR&code=O2O_SVR_001_005). |
| Maximum number of public IPs per server | 1 per server. | Can't increase limit. |
| Maximum number of ACGs per VPC | 500 | Can't increase limit. |
| Maximum number of ACGs per server | 3 | Can't increase limit. |
| Maximum number of rules per ACG | 50 | Can't increase limit. |
| Maximum number of network interfaces | 3 (However, 1 for Micro-g3) | Can't increase limit. |
| Available days to stop server | Up to 90 days per 1 stop and 180 cumulative days in a 12-month period. | The limit can't be increased. (While the server is stopped, only the basic disk fee to install the operating system will be incurred.) |

### Server creation limit by server type

The server creation limit differs according to the country and member type (individual, corporate) selected upon signing up. If you want to change the limit, request it through [Customer Support > Contact Support](https://www.ncloud.com/support/question/service?parentCode=O2O_SVR&code=O2O_SVR_001_005).

              Note

              

If you need more servers than the server creation limits, check the [FAQs](https://www.ncloud.com/support/faq/all/3178) and contact [Customer Support](https://www.ncloud.com/support/question/service?parentCode=O2O_SVR&code=O2O_SVR_001_005) to increase the limit.

## Server image specifications

For more information about server images provided by NAVER Cloud Platform, see [Various server images](https://www.ncloud.com/product/compute/server).

## Storage specifications

Additional Block Storage specifications are as follows:

### KVM-based storage

The types of available storages in KVM-based g3 servers are classified depending on the purpose of use and usage. The storage specifications by type are as follows:

| Item | FB1, FB2 (Fixed Block Storage) | CB1, CB2 (Common Block Storage) |
| --- | --- | --- |
| Description | - Provides performance with fixed IOPS regardless of the storage size. - Cannot be used as primary storage. - Used to save and archive large amounts of data requiring high throughput. | - Provides the basic performance and provides variable performance based on the size. - Separate purchase or provisioning of performance not available. - Used as the primary storage. |
| Media type | HDD | SSD |
| Minimum size | 100 GB | 10 GB |
| Maximum size | 16 TB | 16 TB (for primary storage, maximum size of 2 TB). |
| Maximum number of additional storages | 20 | 20 |
| IOPS | 500 (fixed) | 100–16,000 (It may vary depending on the size.) |
| IOPS Burst | - | 3,000 (applied when the basic performance is equal to or less than 3,000) |
| Throughput | 4–500 MB/s (it may vary depending on the size.) | 100–250 MB/s (It may vary depending on the size.) |
| Throughput burst | 25–500 MB/s (It may vary depending on the size.) | - |

              Note

              

- The maximum number of additional storages does not include the primary storage. 1 primary storage is provided when you create a server, and you can add 20 additional storages.
- In the case of Micro server, no fee is charged up to 10 GB for the primary storage CB1/2, and fees are charged for additional storages regardless of the storage volume type.
- As for the CB1/2 storage's IOPS, 100 IOPS is provided between 10 GB and 30 GB if you change the storage size. Afterwards, it increases by 3 IOPS per 1 GB. Up to 16,000 IOPS (4 KiB I/O) is provided.
- The throughput of CB1/2 storage is provided as 100 MB/s up to 150 GB. Afterwards, it increases by 1 MB/s per 1 GB. Up to 250 MB/s is provided.
- Specification changes between FB1/2 and CB1/2 storage types are not possible.

### XEN-based storage

The available storage specifications in the XEN-based g1 and g2 servers are as follows:

| Item | HDD | SSD |
| --- | --- | --- |
| Minimum size | 10 GB | 10 GB |
| Maximum size | 2 TB | 2 TB |
| Maximum number of additional storages | 15 (it may differ depending on the operating system.) | 15 (it may differ depending on the operating system.) |

              Note

              

- The maximum number of additional storages does not include the primary storage. 1 primary storage is provided when you create a server, and you can add 15 additional storages.
- When it comes to SSD block storage, 4,000 IOPS is provided between 10 GB and 100 GB. Afterward, it increases by 40 IOPS per 1 GB. Up to 20,000 IOPS (4 KiB I/O) is provided.

## ACG specifications

Each account of NAVER Cloud Platform has a default ACG created. The default ACG follows these default rules:

## ACG specifications

Each account of NAVER Cloud Platform has a default ACG created. The default ACG follows these default rules:

- Block all inbound traffic.
- Allow all outbound traffic (specified as a rule).
- Allow bidirectional network communication between servers in Default ACG (added as rule, can be deleted).  

:::

## Pricing information

Server is serviced on a pay-as-you-go pricing plan. For more information on Server's pricing, see the following pages:

- [Portal > Services > Server page](https://www.ncloud.com/product/compute/server)
- [Portal > Services > SSD Server page](https://www.ncloud.com/product/compute/ssdServer)
- [Portal > Services > Bare Metal Server page](https://www.ncloud.com/product/compute/baremetal)
- [Portal > Services > GPU Server page](https://www.ncloud.com/product/compute/gpuServer)