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

# Overview

> Run virtual instances and bare metal servers with disks, file shares, and private networks.

[Edge Cloud](https://gcore.com/cloud) runs workloads on infrastructure that Gcore operates. Those workloads run as Virtual Instances or Bare Metal servers, or on managed platforms for containers and databases, with storage and networking around them.

## Run a server

Place the workload on shared hardware or on a physical machine reserved for one account.

> [card] [Virtual Instances](https://docs.gcore.com/cloud/virtual-instances/create-an-instance.md)
>
> Run a virtual server on shared physical hardware, with control over its operating system and installed software. Choose the instance type to match the workload's CPU, memory, and performance requirements.

> [card] [Bare Metal](https://docs.gcore.com/cloud/bare-metal-servers/create-a-bare-metal-server.md)
>
> Run workloads on a dedicated physical server without sharing its hardware with other accounts. Connect the server to private networks alongside Virtual Instances and other Cloud resources.

A [GPU](https://docs.gcore.com/cloud/virtual-instances/types-of-virtual-machines.md#gpu) type is one Virtual Instance with a graphics accelerator. [GPU Cloud](https://docs.gcore.com/edge-ai/ai-infrastructure/about-gpu-cloud.md) is a dedicated cluster of servers, with multiple GPUs on each server.

## Run an application

Each service leaves a different share of the work with the account.

> [card] [Managed Kubernetes](https://docs.gcore.com/cloud/kubernetes/about-gcore-kubernetes.md)
>
> Run containerized workloads on Kubernetes clusters backed by Virtual Instances or Bare Metal servers. Gcore manages the control plane, while the account controls node pools and workloads.

> [card] [Container](https://docs.gcore.com/cloud/caas.md)
>
> Deploy a container image without setting up a Kubernetes cluster or managing Virtual Machines. Gcore handles the underlying infrastructure and scales the container as needed.

Container images for Managed Kubernetes, Container as a Service, and Everywhere Inference are stored in [Container Registry](https://docs.gcore.com/cloud/container-registry.md). A disk image for a Virtual Instance is a separate object.

## Store data

Decide where the workload's files live.

> [card] [Volumes](https://docs.gcore.com/cloud/virtual-instances/volumes/about-volumes.md)
>
> Use volumes to store a Virtual Instance's operating system and application data.

> [card] [Images](https://docs.gcore.com/cloud/images/about-images.md)
>
> An image is a copy of a disk. Creating a Virtual Instance copies that image onto the boot volume.

> [card] [File shares](https://docs.gcore.com/cloud/file-shares/about-file-shares.md)
>
> Share files between Virtual Instances, Bare Metal servers, and Kubernetes pods.

## Connect servers

Give servers a path to each other and a path from the internet.

> [card] [Networks](https://docs.gcore.com/cloud/networking/create-and-manage-a-network.md)
>
> Use private networks for internal communication, public interfaces for internet access, or dedicated networks to assign Bare Metal servers a separate pool of public IP addresses.

> [card] [Load Balancers](https://docs.gcore.com/cloud/networking/create-and-configure-a-load-balancer.md)
>
> Distribute incoming requests across multiple backend servers instead of sending all traffic to one. Configure listeners, backend pools, and health checks to control how requests are routed.

After connecting Cloud resources, configure how they can be reached and which traffic they accept:

* **[Control network access](https://docs.gcore.com/cloud/networking/add-and-configure-a-firewall.md):** Configure security groups to allow or restrict traffic to Virtual Instances.
* **[Choose IP addresses](https://docs.gcore.com/cloud/networking/ip-address/difference-between-virtual-floating-and-reserved-ip-addresses.md):** Compare floating, reserved, and virtual IP addresses to find the right addressing option.
* **[Enable HTTPS](https://docs.gcore.com/cloud/secrets-manager/upload-a-pkcs12-file.md):** Upload a TLS certificate to Secrets Manager for use with an HTTPS load balancer.

## Databases

Keep relational data on a server that Gcore operates.

> [card] [Managed PostgreSQL](https://docs.gcore.com/cloud/managed-database-postgresql.md)
>
> Run PostgreSQL databases without maintaining the database server. Gcore handles the underlying infrastructure, with optional replicas to improve availability if the primary server fails.

## Monitoring

Monitor Cloud resources and investigate performance issues using metrics and logs.

* [Monitoring](https://docs.gcore.com/cloud/virtual-instances/monitor-load-and-performance-of-your-instance.md) shows CPU, memory, network, and disk usage to help identify performance problems with Virtual Instances.
* [Managed Logging](https://docs.gcore.com/cloud/logging-as-a-service/about-logging-as-a-service.md) collects logs from multiple servers in one place for troubleshooting and incident investigation.

## Access and cost

Organize Cloud resources, manage access permissions, and keep track of resource limits and costs.

* [Create and manage projects](https://docs.gcore.com/cloud/getting-started/projects/create-a-project.md) to separate workloads and environments.
* [Use tags](https://docs.gcore.com/cloud/tags.md) to identify and organize resources.
* [Configure user roles](https://docs.gcore.com/cloud/getting-started/projects/users/user-roles-and-rights.md) to control who can access and manage resources.
* [Check quotas and request increases](https://docs.gcore.com/cloud/getting-started/request-a-quota-increase.md) when more capacity is needed.
* [Review billing](https://docs.gcore.com/cloud/billing.md) to understand how Cloud resources are charged.
