Regional hosting and data residency
Feature availability
Regional hosting and data residency are available only for Enterprise plans. For more information, see Plans and pricing.
Data residency allows you to control the region in which Snyk hosts a selected subset of your data. For information about GDPR, see How Snyk maintains GDPR compliance.
Data residency is available for Snyk Open Source, Snyk Code, Snyk Container, and Snyk IaC. Snyk can host your data in a number of regions.
This page provides information on:
A list of regional URLs is also provided.
Regional and global data
Snyk uses subprocessors to provide a high-quality service. Thus, not all data types can be stored within your region of choice. The list of subprocessors is available on the Snyk website.
See How Snyk handles your data for product-specific examples of how data is handled.
Regionally stored data types
Vulnerability data
Vulnerability source
Audit logs
Integration-related data
Customer source code
Globally stored data types
Billing data
Customer relationship management data
Operational logs and metrics
Product analytics
Support Tickets
User authentication data
Available Snyk Regions
After you select a region, the data in that region cannot be migrated to another region. Moving to a new region requires a complete re-onboarding.
During the initial onboarding of your system, you can work with your account team to select a multi-tenant hosting region. For single-tenant availability (Snyk Private Cloud), reach out to your account team in advance of onboarding. When using Snyk features, you will use specific URLs that differ from the SNYK-US-01 URL. See Regional URLs for the list of URLs.
You must configure your environment to set your region before you authenticate. This does not apply when you are using the SNYK-US-01 URL. For details, see the snyk config environment CLI help.
Snyk offers data residency for the following regions:
| Region | URL |
|---|---|
SNYK-US-01 (US) | https://app.snyk.io |
SNYK-US-02 (US) | https://app.us.snyk.io |
SNYK-EU-01 (Germany, Frankfurt) | https://app.eu.snyk.io |
SNYK-AU-01 (Australia) | https://app.au.snyk.io |
SNYK-GOV-01 (Snyk for Government (US)) | https://app.snykgov.io |
Single-tenant deployments may support more regions than the ones listed here, subject to validation of architectural service supportability by Snyk engineering.
Snyk AppRisk works across all regions. There is no need to set your region and use a specific URL.
Regional multi- and single-tenant hosting
The SNYK-US-01 region is available to customers who joined before September 2024 and to Free plan users.
For Free or Team plan users in the SNYK-US-01 region, no configuration is required for URLs. For hosting in other regions, you must configure your environment for that region.
SNYK-US-02, EU, and AU data center Snyk accounts are available only with the purchase of an Enterprise plan.
Snyk offers almost all the same features, support, and performance in the regional multi- and single-tenant regions as in SNYK-US-01. For an up-to-date overview of feature parity across regions, contact your account team.
All Snyk AppRisk features are supported in all multi-tenant environments, while for the single-tenant environment you need to check the availability with your account team.
Integration considerations
There are special considerations when you set up specific integrations in your Snyk ecosystem.
If you choose to install the Snyk Runtime Sensor using a Helm chart, you must provide the Snyk API base URL. You can find all the necessary details under step 5 of the Using a Helm chart section of the Snyk Runtime Sensor documentation page.
If you choose to set up third-party integrations, verify whether you need to specify the base API URL of the third-party
Regional URLs
Login and Web UI URLs
SNYK-US-01: https://app.snyk.io/
SNYK-US-02: https://app.us.snyk.io/
SNYK-EU-01: https://app.eu.snyk.io/
SNYK-AU-01: https://app.au.snyk.io/
Support portal links
To view and submit tickets, use the link for your regoin.
SNYK-US-01: https://support.snyk.io/
SNYK-US-02: To be provided
SNYK-EU -01:https://snyk-mt-eu-prod-1.eu.auth0.com/samlp/xU6rUSC7zvEco2ndKemfJNT6oKtc13Qw
SNYK-AU-01:https://snyk-mt-au-prod-1.au.auth0.com/samlp/HnGYPWKxM9JegYL2aq0OAdBAwGJDz0vQ
API URLs
Use the reference documentation with the following base URLs:
SNYK-US-01: API v1 : https://api.snyk.io/v1/ and REST API: https://api.snyk.io/rest/
SNYK-US-02: API v1: https://api.us.snyk.io/v1/ and REST API: https://api.us.snyk.io/rest/
SNYK-EU-01: API v1: https://api.eu.snyk.io/v1/ and REST API: https://api.eu.snyk.io/rest/
SNYK-AU-01: API v1: https://api.au.snyk.io/v1/ and REST API: https://api.au.snyk.io/rest/
CLI and CI pipeline URLs
Both the CLI and CI running CLI must be configured to run against your instance.
To do this, for CLI v1.1293.0 and later versions, use the snyk config environment command, for example:
The Supported environment URL mappings are listed in the snyk config environment help.
IDEs URLs
Ensure you are using the latest version of the IDE plugins. The following specifies the minimum versions required: VSCode - 1.2.18 Visual Studio - 1.1.21 IntelliJ - 2.4.32
Snyk IDE extensions have modifiable options similar to the CLI and must be configured to use the appropriate endpoint. In the extension settings for Snyk in your IDE, set Custom Endpoint to the appropriate value for SNYK-US-02, SNYK-EU-01, and SNYK-AU-01 as follows.
SNYK-US-01: https://api.snyk.io (no configuration required)
SNYK-US-02: https://api.us.snyk.io
SNYK-EU-01: https://api.eu.snyk.io
SNYK-AU-01 : https://api.au.snyk.io
Broker URLs
Use github.com/snyk/broker and add an extra environment variable in the container:
SNYK-US-01: https://broker.snyk.io (no configuration required)
SNYK-US-02: -e BROKER_SERVER_URL=https://broker.us.snyk.io
SNYK-EU-01: -e BROKER_SERVER_URL=https://broker.eu.snyk.io
SNYK-AU-01: -e BROKER_SERVER_URL=https://broker.au.snyk.io
For Broker deployed by Helm chart, use https://github.com/snyk/snyk-broker-helm and add the following variable:
SNYK-US-02: --set brokerServerUrl=https://broker.us.snyk.io
SNYK-EU-01: --set brokerServerUrl=https://broker.eu.snyk.io
SNYK-AU-01: --set brokerServerUrl=https://broker.au.snyk.io
Broker with high availability (HA) mode URLs
Follow the High availability mode instructions BUT use the following details for BROKER_DISPATCHER_BASE_URL:
SNYK-US-02: -e BROKER_DISPATCHER_BASE_URL=https://api.us.snyk.io
SNYK-EU-01: -e BROKER_DISPATCHER_BASE_URL=https://api.eu.snyk.io
SNYK-AU-01 : -e BROKER_DISPATCHER_BASE_URL=https://api.au.snyk.io
For Broker deployed by Helm chart, edit the values.yaml file to include the relevant details in brokerDispatcherUrl.
Broker with Code Agent URLs
Follow the Snyk Broker - Code Agent instructions BUT add an extra environment variable in the Code Agent container:
SNYK-US-02 :-e UPSTREAM_URL=https://deeproxy.us.snyk.io
SNYK-EU-01 :-e UPSTREAM_URL=https://deeproxy.eu.snyk.io
SNYK-AU-01 :-e UPSTREAM_URL=https://deeproxy.au.snyk.io
For Broker with Code Agent deployed by Helm chart, use https://github.com/snyk/snyk-broker-helm and add the following variable in the Code Agent chart:
SNYK-US-02: --set upstreamUrlCodeAgent=https://deeproxy.us.snyk.io
SNYK-EU-01: --set upstreamUrlCodeAgent=https://deeproxy.eu.snyk.io
SNYK-AU-01:--set upstreamUrlCodeAgent=https://deeproxy.au.snyk.io
Broker with Snyk Code Local Engine (SCLE)
Set up your values-customer-settings.yml with the correct Broker Server URL for your region based on the values found in the Broker URLs section.
Then add an extra variable to the values-customer-settings.yml:
SNYK-US-02
deeproxy:
verificationEndpoint: "https://api.us.snyk.io/v1/validate/token/snyk-to-deepcode-proxy-validation"
SNYK-EU-01
deeproxy:
verificationEndpoint: "https://api.eu.snyk.io/v1/validate/token/snyk-to-deepcode-proxy-validation"
SNYK-AU-01
deeproxy:
verificationEndpoint: "https://api.au.snyk.io/v1/validate/token/snyk-to-deepcode-proxy-validation"
Last updated