## Step 2. Select a region
Choose the region where the server will be deployed.
## Step 3. Select an image
Select the architecture - **x86-64** or **ARM** - then choose an OS image from one of three tabs:
* **Distributions** - prepared OS templates (Ubuntu, CentOS, Debian, Windows, and others).
* **Marketplace** - pre-configured application images.
* **Custom Images** - images previously uploaded to the account. Only images built for Bare Metal servers are compatible; standard VM images do not work. Build requirements are covered in [image upload](/cloud/images/upload-an-image-to-the-storage).
## Step 4. Select a server type
Server types are grouped into three categories:
* **High frequency** - high clock-speed CPUs for latency-sensitive workloads.
* **Infrastructure** - high core count and NVMe storage for compute-intensive tasks.
* **Storage** - large-capacity drives for data-heavy workloads.
All types require a quota. After selecting a type, a **Quota Increase Required** block appears with a **Send quota request** button. The remaining sections of the form unlock once the quota is approved.
## Step 5. Configure network interfaces
After quota approval, configure network interfaces. Up to six networks can be attached. An external network cannot be added after the server is created.
1. Select the **Network type**: **Public**, **Private**, or **Dedicated public**.
2. In the **IP Family** section, select the IP version: **IPv4**, **IPv6**, or **Dual (IPv4 + IPv6)**.
3. (Optional) Enable **Use reserved IP** to assign a [reserved IP address](/cloud/networking/ip-address/create-and-configure-a-reserved-ip-address) to the server.
4. (Optional) Enable **Advanced DDoS Protection** for enhanced security.
For a **private** interface, also configure a network and subnetwork:
```bash theme={null}
$ ip a
1: lo: 
To add a new key, follow the steps in [Connect via SSH](/cloud/bare-metal-servers/connect-to-your-bare-metal-server-via-ssh).
For Windows servers, the password must be 8-16 characters and may contain Latin letters (`a-zA-Z`), digits (`0-9`), and special characters (`!#$%&'()*+,-./:;<=>?@[]^_{|}~`). Connect via [the portal console](/cloud/virtual-instances/connect/connect-to-your-instance-via-control-panel) or RDP.
## Step 7. Configure additional options
In the **Additional options** section, optionally provide a `cloud-init` script in the **User data** field to automate initial configuration - install packages, create users, or run commands on first boot.
## Step 8. Set quantity and name
Specify the number of servers (up to 10, subject to quota) and the name template. Click **Create Server** - the server provisions in the cloud.
## Multi-bond network configuration
Bare Metal servers support multiple network bonds, where each bond is a group of LACP-aggregated physical ports. With a multi-bond setup, traffic for different networks is isolated at the hardware level, which improves availability and throughput. Multi-bond configuration is available on request - contact [Gcore support](https://gcore.com/contact-us) to enable it.
After the server is deployed, open the server details and go to the **Networking** tab. Each bond appears as a separate interface block labeled **Interface N (Trunk Interface N)**.
Each interface block shows the sub-interfaces assigned to that bond - a sub-interface is the logical port that carries traffic for a specific network. The table for each sub-interface includes the IP address, network, subnetwork, MAC address, CIDR, and floating IP assignment.
To add a sub-interface to a bond, click **Add Sub-Interface** in the corresponding interface block and configure the network settings.
## Limitations
* External volumes cannot be attached to Bare Metal servers.
* Volume configuration cannot be changed after provisioning.
* No more than six networks can be attached.
* After deployment, private network interfaces can only be attached or detached manually via the OS.
Each step below explains what the call does, which parameters matter, and what the response looks like. Use this section to understand the flow or to debug a specific step.
GET /cloud/v1/images are not compatible. Each BM image name ends with `-ironic` and contains `"is_baremetal": true` in the response.
GET /cloud/v1/tasks/{task_id} every 30 seconds until `state` is `FINISHED`:
```bash theme={null}
curl "https://api.gcore.com/cloud/v1/tasks/$TASK_ID" \
-H "Authorization: APIKey $GCORE_API_KEY"
```
When complete:
```json theme={null}
{
"state": "FINISHED",
"created_on": "2026-05-29T12:48:58",
"finished_on": "2026-05-29T12:53:46",
"created_resources": {
"instances": ["90ba53c5-def5-4825-83fb-9adc78bd3266"]
}
}
```
```bash theme={null}
export SERVER_ID="90ba53c5-def5-4825-83fb-9adc78bd3266"
```
GET /cloud/v1/bminstances/{project_id}/{region_id}/{server_id} - each trunk appears as a separate interface block in the `addresses` map.
## Clean up
Bare Metal deletion is asynchronous and takes 3-5 minutes - the server must be fully deprovisioned before the hardware is released. Local NVMe storage is wiped during deprovisioning.
GET /cloud/v1/tasks/{task_id} every 30 seconds until `state` is `FINISHED`.
Provision a dedicated Bare Metal server — physical hardware with no virtualization layer — using [`gcore_cloud_baremetal_server`](https://registry.terraform.io/providers/G-Core/gcore/latest/docs/resources/cloud_baremetal_server). Provisioning is asynchronous and may take several minutes to complete.
## Create a Bare Metal serverDeclares a server with a public IPv4 interface and an SSH key. Creation takes 4-6 minutes.
```hcl theme={null} resource "gcore_cloud_baremetal_server" "example" { project_id = var.project_id region_id = var.region_id flavor = var.flavor_id # region-specific; find with the Customer Portal or flavors API name = "my-bare-metal" image_id = var.image_id # region-specific; find with the Customer Portal or images API ssh_key_name = "my-keypair" interfaces = [{ type = "external" ip_family = "ipv4" }] # terraform import gcore_cloud_baremetal_server.example 'After `terraform apply`, `status` is `ACTIVE` and `addresses` contains the assigned public IP. Use the IP to connect over SSH.
## Attach a private networkPrivate networks for Bare Metal require `type = "vlan"` on the network resource — add both interfaces at creation, as interface order determines routing priority.
```hcl theme={null} resource "gcore_cloud_network" "bm_net" { project_id = var.project_id region_id = var.region_id name = "my-bm-network" type = "vlan" # required for Bare Metal } resource "gcore_cloud_network_subnet" "bm_subnet" { project_id = var.project_id region_id = var.region_id name = "my-bm-subnet" network_id = gcore_cloud_network.bm_net.id cidr = "192.168.10.0/24" } resource "gcore_cloud_baremetal_server" "example" { project_id = var.project_id region_id = var.region_id flavor = var.flavor_id name = "my-bare-metal" image_id = var.image_id ssh_key_name = "my-keypair" interfaces = [ { type = "external" ip_family = "ipv4" }, { type = "subnet" network_id = gcore_cloud_network.bm_net.id subnet_id = gcore_cloud_network_subnet.bm_subnet.id }, ] } ```The Terraform provider does not support power state operations (`start`, `stop`, `reboot`, `reboot_hard`) for Bare Metal servers. Use the Customer Portal or the REST API tab to perform these actions.
## Delete a Bare Metal serverRemove the resource block — Terraform deletes the server on the next `terraform apply`. Deprovisioning takes 3-5 minutes and permanently wipes local NVMe storage.
```hcl theme={null} # Remove or comment out this block: # resource "gcore_cloud_baremetal_server" "example" { ... } ``` ```bash theme={null} terraform apply ```