Skip to main content
Edge 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.

Virtual Instances

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.

Bare Metal

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 type is one Virtual Instance with a graphics accelerator. GPU Cloud 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.

Managed Kubernetes

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.

Container

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. A disk image for a Virtual Instance is a separate object.

​
Store data

Decide where the workload’s files live.

Volumes

Use volumes to store a Virtual Instance’s operating system and application data.

Images

An image is a copy of a disk. Creating a Virtual Instance copies that image onto the boot volume.

File shares

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.

Networks

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.

Load Balancers

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:

​
Databases

Keep relational data on a server that Gcore operates.

Managed PostgreSQL

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 shows CPU, memory, network, and disk usage to help identify performance problems with Virtual Instances.
  • Managed Logging 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.