Civo FRA1: the Frankfurt region.
Last updated By Marcel R. G. Berger
Civo's region in the European Union, what it offers, what it does not, and how to run it next to LON1 from a Mac.
FRA1 is Civo's Frankfurt region in Germany and the only one of Civo's four regions in the European Union. CPU Kubernetes, CPU Compute, Object Stores, Volumes and Databases are available in FRA1. GPU Kubernetes and GPU Compute are not, according to Civo's Regions documentation; LON1 is the only region that offers them.
Which Civo products are available in FRA1?
Five of the seven products in Civo's region table are available in FRA1. The two GPU products are not.
| Product | FRA1 Frankfurt |
|---|---|
| CPU Kubernetes | Available |
| GPU Kubernetes | Not available |
| CPU Compute | Available |
| GPU Compute | Not available |
| Object Stores | Available |
| Volumes | Available |
| Databases | Available |
Source: Civo documentation, Regions (last updated 24 September 2026). civo.com/docs/overview/regions · civo.com/ai/gpu-compute · civo.com/docs/object-stores · civo.com/docs/object-stores/adding-files-to-object-stores
What runs in FRA1, and what does not?
FRA1 runs Civo's CPU products: Kubernetes clusters on CPU nodes, compute instances, object stores, volumes and managed databases. GPU Kubernetes and GPU Compute are marked unavailable in FRA1 in Civo's Regions documentation, last updated on 24 September 2026, and are available only in LON1. Civo's GPU Compute product page lists the EU as coming soon, so the region table is the place to check before you plan a GPU workload in Frankfurt.
How do you run FRA1 and LON1 side by side?
You run them as two separate regions, because Civo resources are region-specific: a cluster deployed in FRA1 is listed only in FRA1, and a GPU cluster in LON1 only in LON1. CivoCloudManager's Regions view counts instances, Kubernetes clusters, databases, networks and volumes for both regions at once, so a split between CPU work in Frankfurt and GPU work in London stays visible without switching back and forth. The selected region is the default for requests that need one, and a request that names a region explicitly keeps that region.
How do you connect to FRA1 object storage from a Mac?
FRA1 object stores are reached at https://objectstore.fra1.civo.com with a credential created while FRA1 is selected. Civo ties object store credentials to the region they were created in, so a key made in FRA1 does not authenticate against the LON1 endpoint, even in the same account. Our guide to Civo Object Storage with s3cmd, rclone and the AWS CLI uses FRA1 as its worked example; CivoCloudManager reads the endpoint each store returns from the API and signs requests with the store's region.
Civo FRA1: common questions
Does Civo have GPUs in Frankfurt?
How do I switch to the Civo FRA1 region on a Mac?
--region FRA1 to a single command. What is the Civo FRA1 object storage endpoint?
https://objectstore.fra1.civo.com. For s3cmd, set host_base and host_bucket to objectstore.fra1.civo.com; for rclone and the AWS CLI, use the full URL as the endpoint and fra1 as the region. Civo's documentation on adding files to object stores uses https://objectstore.fra1.civo.com in its s3cmd example. Why does my FRA1 object store key fail on LON1?
Civo regions
The four Civo regions
- 01 LON1 London London, United Kingdom: the only Civo region with GPU Kubernetes and GPU Compute, next to the full CPU product set.
- 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.
Frankfurt and London in one window.
CivoCloudManager shows your FRA1 resources next to every other region and switches with one click. Free menu-bar tier, one-time purchase for the full dashboard on the Mac App Store.