SingleStore Helios Region Types

On this page

SingleStore provides flexible deployment options across multiple regions to meet your infrastructure, security, and compliance needs. "Regions" refer to geographical locations and infrastructure zones provided by AWS, Google Cloud (GCP), and Microsoft Azure where SingleStore can be deployed.

SingleStore Helios can be deployed in the following region types:

Managed
Dedicated

Refer to Helios Pricing for a list of features supported by Managed region types. Refer to SingleStore Helios Editions for more information on Editions.

Managed Regions

Managed regions are the most secure, fully managed, and feature-rich way to deploy SingleStore. These regions deliver the best overall TCO (Total Cost of Ownership) and provide full access to all the SingleStore capabilities. Managed regions are available across AWS, Azure, and GCP. Managed regions support Shared, Standard, and Enterprise editions of SingleStore.

Refer to SingleStore Helios Service Level Agreement and Certifications for the SLA and certifications provided by SingleStore for Managed regions.

If a region is not currently available or supported, contact your SingleStore account representative or SingleStore Support.

Dedicated Regions

Dedicated regions support the same feature set and functionality as Managed regions, but they are specifically designed for organizations that require a single-tenant data plane. Dedicated regions offer the same level of security as Managed regions.

Dedicated regions maintain the same Helios availability SLAs and compliance certifications as Managed Regions, but consume compute credits at a faster rate.

Last modified: April 21, 2026

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
Download the signature file from the SingleStore release server.
- Option 1: Click the Download Signature button next to the SingleStore file.
- Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.
- Option 3: Run the following command to download the signature file.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
      --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
      --bundle undefined \
      --new-bundle-format -

Verified OK