[Yandex Cloud documentation](../../index.md) > [Yandex BareMetal](../index.md) > Concepts > Overview

# Yandex BareMetal overview

In Yandex BareMetal, you can [rent](../operations/servers/server-lease.md) a physical server with all its hardware resources provisioned for your individual use. 

To create and conveniently operate an infrastructure relying on leased physical servers, BareMetal provides users with all the required tools to manage the servers and their network’s settings.

There is a system of flexible [quotas](limits.md) and resource limits which decides the amount of servers, networks, and disk space for custom OS images available to each user.

## Servers {#servers}

You can order servers of the following configurations:

* Stock configuration: Get a ready-to-use server with or without an OS in minutes. Choose a server from dozens of configurations for typical tasks and workloads.

   [Leasing a stock configuration server](server-configurations.md)
* Custom configuration: Use our builder to create a server optimized for your load profile from available server components and get your new server in 4 days' time. 

  [Building a custom server configuration](server-custom-configurations.md)
* On-request configuration: If looking for a server for a variety of scenarios and workloads, apply for an on-request configuration.

  [Learn more about on-request configuration](server-individual-configurations.md).

You can rent [servers](servers.md) for a period from one day to one year. When ordering a server, you can install an OS from ready-made Marketplace [images](images.md) or use your own distribution for installation by [uploading](../operations/image-upload.md) it to [Yandex Object Storage](../../storage/index.md). You can also configure public and private IP addressing, SSH access, and server backup policies using [Yandex Cloud Backup](../../backup/index.md).

## Network {#network}

All servers have several physical [network interfaces](servers.md#network-interfaces) that you can connect to the [public internet](public-network.md) and to a [private network](private-network.md) through different, independent switches assembled into a single IP fabric with the `spine-leaf` topology.

In the public network, each server is allocated one public IPv4 address free of charge. You can also lease blocks of [dedicated public subnets](public-network.md#public-subnet) of varying sizes and use them to assign addresses to servers. For servers with 10 and 25 Gbps network cards, you can select a daily internet traffic package.

In a private network, you can group servers at different levels through [private subnets](private-network.md#private-subnet) (L2, VLAN 802.1Q) and use routing to join them into a [VRF](private-network.md#vrf-segment) (L3). If you need to, you can assign several private subnets to a single server port (L2, trunk-port 802.1Q) or add [static routes](private-network.md#static-routes) to a VRF.

To ensure stable operation of all networks, BareMetal has a number of [limits](network-restrictions.md).

BareMetal servers can use a private network to access your cloud infrastructure or other Yandex Cloud services with the help of [Cloud Interconnect](../../interconnect/index.md), which allows you to combine your physical servers and cloud infrastructure into a single L3 network. This way, you can implement different scenarios for your infrastructure, e.g., use physical servers as [Managed Service for Kubernetes](../tutorials/k8s-connect-bms-as-node.md) nodes or as dedicated data storage.

## Setup and management {#control}

You can access the server using a [KVM console](../operations/servers/server-kvm.md) or over SSH. You can also manage servers using the [CLI](../cli-ref/index.md) and [API](../api-ref/index.md).

To configure, manage, and audit actions with objects, BareMetal provides the following interfaces: the Yandex Cloud management console, [CLI](../cli-ref/index.md), and [API](../api-ref/index.md). You can get audit logs of your operations using [Audit Trails](../../audit-trails/index.md), and manage roles and accesses via [Identity and Access Management](../../iam/index.md).

## Quotas and limits {#quotas-and-limits}

[Quotas](limits.md) restrict the number of available servers, networks, and images. Also, certain [limits](network-restrictions.md) apply to networks.

#### See also {#see-also}

* [Servers](servers.md)
* [Stock server configurations](server-configurations.md)
* [Analysis of Yandex BareMetal server disk status](smart-disk-analysis.md)
* [Network](network.md)
* [DHCP in a Yandex BareMetal network](dhcp.md)
* [Restrictions in BareMetal networks](network-restrictions.md)