Skip to main content
Archil disks are available in multiple regions across AWS and Google Cloud Platform (GCP). When creating a disk, you can select the region that best suits your needs. For optimal performance, we recommend choosing a region closest to where your compute resources are located.

​
AWS regions

Archil disks are available in the following AWS regions:
  • US East (N. Virginia) - aws-us-east-1
  • US West (Oregon) - aws-us-west-2
  • EU West (Ireland) - aws-eu-west-1

​
Google Cloud Platform regions

Archil disks are available in the following GCP regions:
  • US Central (Iowa) - gcp-us-central1
We are continuously expanding our regional presence. If you need Archil in a region not listed here, please contact us.

​
Preview regions

aws-us-east-2 (Ohio), gcp-us-west1 (Oregon), and gcp-europe-west4 (Netherlands) are available in preview. Other preview regions may also be available; contact us to confirm access and supported features before choosing one for a workload.

​
Compute availability

In Archil’s public regions, serverless execution (disk.exec and disk.grep) and persistent sandboxes are available in the AWS regions. BYOC deployments support both on every cloud and on bare metal. A disk created in a public region without serverless execution works for storage, but calling exec returns Exec is not enabled (and grep returns Grep is not enabled). If you plan to run commands on a disk in a public region, create it in one of the AWS regions above.

​
Private deployments (BYOC)

Bring Your Own Cloud deployments run on any cloud, including AWS, Google Cloud, and Azure, as well as on bare metal. A BYOC deployment can include the full Archil platform: disks, persistent sandboxes, and serverless execution. The public-region limits above don’t apply to BYOC. Archil fully manages each BYOC deployment, and the telemetry it sends to Archil is scrubbed of PII and PHI before it leaves your cluster. There are no public Azure regions, so Azure is available only through BYOC. Archil’s public regions run sandboxes and serverless execution in AWS because that’s where Archil hosts its own compute, not because of a limit in the software. See Why public regions differ.