Sign inTry Free

Important

New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.

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.

Private Preview

Public Preview

General Availability (GA)

Who Can Use?

Selected design partners or internal users

All customers

All customers

For Production?

Non-production use only

Can be used in production

Feature may have limitations or issues

Fully supported

Interface Stability

Not fully stable

Largely stable

Fully stable

SLA

None

Full SLA applies to the cluster

Best-effort support for the feature

Full SLA applies

Support

Limited / Engineering team

Standard support

Feature may not be fully functional

Standard support

Feature is fully functional

Release State

Invite-only

Feature is in early testing

Broader testing

Known limitations documented

Official production release

Final customer success materials available

Documentation

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

Documentation available on docs.singlestore.com labeled as "Preview"

Final documentation available on docs.singlestore.com

Last modified:

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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In