Civo NYC1: the New York region.
Last updated By Marcel R. G. Berger
Civo's region in the United States, what runs there, and how to work with it from a Mac.
NYC1 is Civo's New York region and the only one of Civo's four regions in the United States. Civo's API reference lists it with the code NYC1, the name New York 1 and the country us, United States. CPU Kubernetes, CPU Compute, Object Stores, Volumes and Databases are available in NYC1; GPU Kubernetes and GPU Compute are not. CivoCloudManager reads the live region list your API key returns and shows NYC1 with its name, country and code.
Which Civo products are available in NYC1?
Five of the seven products in Civo's region table are available in NYC1. The two GPU products are available in LON1 only.
| Product | NYC1 New York |
|---|---|
| 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/api/regions · civo.com/ai/gpu-compute · civo.com/docs/object-stores
Can you run GPU workloads in NYC1?
Not today, according to Civo's Regions documentation: GPU Kubernetes and GPU Compute are unavailable in NYC1 and available only in LON1 in London. Civo's GPU Compute product page lists the US as coming soon. Until the region table changes, LON1 is the only Civo region with GPU products, and CPU services in NYC1 stay a separate region next to it.
Why does the region matter for NYC1 instances and networks?
Civo's API reference says you choose the region when you create an instance, and that this is necessary if instances should share a private network. Instances that should share a private network are therefore created in the same region, for example all in NYC1. CivoCloudManager counts networks per region in its Regions view and lists NYC1's networks and instances once NYC1 is current.
How do you reach NYC1 object storage from a Mac?
NYC1 object stores answer at https://objectstore.nyc1.civo.com. The authoritative value is the endpoint each store shows in the Civo dashboard and returns in the objectstore_endpoint field of the API. A credential for an NYC1 store is created while NYC1 is selected, because Civo ties object store credentials to the region where they were created. CivoCloudManager opens each store on the endpoint the API returns and signs its S3 requests with the region, so no endpoint has to be typed in. The endpoint https://objectstore.nyc1.civo.com comes from our own DNS and HTTP check on 18 October 2026, not from a Civo documentation page.
Civo NYC1: common questions
Does Civo have a data centre in the US?
Does Civo have GPUs in New York?
How do I switch to the Civo NYC1 region on a Mac?
--region NYC1 to a single command. What is the Civo NYC1 object storage endpoint?
https://objectstore.nyc1.civo.com. The authoritative value is the endpoint each store shows in the dashboard and returns in the API, and the credential has to be created in NYC1 as well. The endpoint https://objectstore.nyc1.civo.com comes from our own DNS and HTTP check on 18 October 2026, not from a Civo documentation page.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 FRA1 Frankfurt Frankfurt, Germany: Civo's EU region with CPU Kubernetes, CPU Compute, Object Stores, Volumes and Databases, without 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.
NYC1 next to your other regions.
CivoCloudManager reads your live region list and shows what runs in New York next to every other region. Free menu-bar tier, one-time purchase for the full dashboard on the Mac App Store.