Civo LON1: the London region with GPUs.
Last updated By Marcel R. G. Berger
The only Civo region with GPU Kubernetes and GPU Compute, and how to work with it from a Mac.
LON1 is Civo's London region and the only one of Civo's four regions with GPU Kubernetes and GPU Compute. Civo's API reference lists it as London 1 with the country United Kingdom, and it is the only region in Civo's region table located in the UK. Every product in that table, CPU and GPU alike, is available in LON1, which makes it the one region where a GPU workload and its Kubernetes clusters, volumes, databases and object stores can sit side by side.
Which Civo products are available in LON1?
All seven products in Civo's region table are available in LON1. No other Civo region has all seven, because GPU Kubernetes and GPU Compute are available in LON1 only.
| Product | LON1 London |
|---|---|
| CPU Kubernetes | Available |
| GPU Kubernetes | Available |
| CPU Compute | Available |
| GPU Compute | Available |
| Object Stores | Available |
| Volumes | Available |
| Databases | Available |
Source: Civo documentation, Regions (last updated 24 September 2026). civo.com/docs/overview/regions · civo.com/uk-sovereign-cloud · civo.com/ai/gpu-compute · civo.com/docs/object-stores · civo.com/learn/object-store-as-terraform-backend
Why is LON1 Civo's GPU region?
LON1 is Civo's GPU region because Civo's Regions documentation marks GPU Kubernetes and GPU Compute as available in LON1 and unavailable in FRA1, NYC1 and MUM1. A GPU cluster or GPU instance is therefore created with LON1 selected. Since Civo resources are region-specific, the volumes, databases and object stores that should live in the same region as that GPU workload are created in LON1 as well, and they appear only in LON1's listings.
What does Civo say about its UK Sovereign Cloud?
Civo describes its UK Sovereign Cloud as a suite of public cloud, private cloud and AI services hosted and operated exclusively within the United Kingdom. In the FAQ on that page Civo names the UK GDPR and the Data Protection Act 2018 as part of the UK law its UK operation follows. The page does not name a region code; LON1 is the only region in Civo's region table located in the United Kingdom. Which offering and which terms apply to your account is a question for Civo, and this page is not a legal assessment.
How do you create GPU resources in LON1 with CivoCloudManager?
Select LON1 in the Regions view of CivoCloudManager and the size picker for new Kubernetes clusters and instances lists the sizes the Civo API returns for that region, grouped by type. GPU is one of the size groups the picker recognises. Once a cluster runs, the Kubernetes dashboard shows live CPU and memory gauges and real-time pod logs over client-certificate mTLS, without kubectl.
Civo LON1: common questions
Does Civo have GPUs in London?
How do I switch to the Civo LON1 region on a Mac?
--region LON1 to a single command. What is the object storage endpoint for Civo LON1?
https://objectstore.lon1.civo.com. The authoritative value is the endpoint each store shows in the dashboard and returns in the API. The credential must be created in LON1 too, because Civo ties object store credentials to the region where they were created. Civo's own tutorial on using an object store as a Terraform backend uses https://objectstore.lon1.civo.com with the region LON1. Is LON1 part of Civo's UK Sovereign Cloud?
Civo regions
The four Civo regions
- 01 FRA1 Frankfurt Frankfurt, Germany: Civo's EU region with CPU Kubernetes, CPU Compute, Object Stores, Volumes and Databases, without GPU products.
- 02 NYC1 New York New York, United States: Civo's only US region, with the CPU product set and no GPU products.
- 03 MUM1 Mumbai Mumbai, India: Civo's India region with the CPU product set. Civo says its India Sovereign Cloud is hosted in Mumbai.
- 04 Civo regions Which Civo products run in which region, where the GPUs are, and how CivoCloudManager keeps four regions in one window.
Deep dives
Targeted reads for each Civo product.
Every Civo surface CivoCloudManager touches has its own page with the specifics, the trade-offs, and the architecture details. Pick the one closest to what you do today.
- 01 Civo CLI alternative for Mac Where the GUI beats the CLI, where it does not, and how the two coexist.
- 02 Civo Kubernetes GUI for Mac Live cluster dashboard, real-time pod logs, no kubectl required.
- 03 Civo Object Storage browser for Mac Native S3-compatible browser. Pause idle buckets to a central vault.
- 04 Civo firewall from the Mac menu bar One-click open/close per firewall, auto-IP detection, auto-close timer.
- 05 Civo cost dashboard for Mac Real charges from the Civo charges API. Period picker and month-end projection.
- 06 Civo regions Which Civo products run in which region, where the GPUs are, and how CivoCloudManager keeps four regions in one window.
Guides
Step by step, and honest comparisons.
- 01 Connect your Civo API key Generate the key in the Civo dashboard, paste it once, and let the macOS Keychain hold it from then on.
- 02 Open a firewall for your IP The manual procedure, the dynamic-IP trap it leaves behind, and a free menu-bar path that closes the rule on a deadline.
- 03 vs Lens, OpenLens and k9s Three cluster agnostic tools, one Civo specific one. The difference decides which you want open.
- 04 Civo Object Storage over S3 The regional endpoint, working configuration for s3cmd, rclone and the AWS CLI, and what a native client does differently.
- 05 Civo DNS on Mac Point a domain at Civo's nameservers, then keep the zone in a native app instead of a browser tab.
- 06 Changelog Every shipped release, newest first, with the detail a store release note is too short to carry.
Manage LON1 from your menu bar.
CivoCloudManager lists the sizes Civo offers in LON1, creates clusters there and shows them next to your other regions. Free menu-bar tier, one-time purchase for the full dashboard on the Mac App Store.