Sign inTry Free

SingleStore Release Types

SingleStore systematically releases features to ensure quality, stability, and customer satisfaction.

The following table, which summarizes SingleStore's release types, is intended to provide a clear, at-a-glance reference for what to expect at each stage of a feature's lifecycle.

Release Type

Who Can Use?

For Production?

Interface Stability

SLA

Support

Notes

Private Preview

Selected design partners or internal users

Non-production use only

Not fully stable

None

Limited / Engineering team

Invite-only; feature is early in testing

Documentation may be available on docs.singlestore.com labeled as “Private preview” with a link to request access

Public Preview

All customers

Can be used in production

Feature may have limitations or issues

Largely stable

Full SLA applies to the cluster

Best-effort support for the feature

Standard support

Feature may not be fully functional

Broader testing; known limitations documented

Documentation available on docs.singlestore.com labeled as “Preview.”

General Availability (GA)

All customers

Fully supported

Fully stable

Full SLA applies

Standard support

Feature is fully functional

Official production release; final customer success materials available.

Final documentation available on docs.singlestore.com

Last modified: October 21, 2025

Was this article helpful?

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.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. 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.

      curl -O undefined

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

    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