Sign inTry Free

Important

The SingleStore 9.0 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

Use Flow on Helios

On this page

Flow on Helios is a fully managed data migration and Change Data Capture (CDC) service within SingleStore Helios. It supports loading and synchronizing data from supported databases into SingleStore, without the need to install or manage any infrastructure. Flow is integrated into the Cloud Portal as a part of the Load Data workflow.

It includes two components: 

  • Ingest: Transfers schema and data for tables up to 10GB, and supports ongoing CDC.

  • XL Ingest: Handles larger tables by partitioning them and transferring partitions in parallel.

Supported Source Databases

The following databases are supported as sources:

  • MySQL

  • PostgreSQL

  • Oracle

  • Microsoft SQL Server

  • Snowflake

These can be self-hosted, or hosted on:

  • AWS RDS

  • AWS Aurora

  • Google CloudSQL

  • Azure SQL

Note: On-premise and self-hosted sources must be accessible over the internet and allow inbound connections from Helios IPs.

For prerequisites and setup, refer to Source Configuration.

Destination Database

  • SingleStore database hosted in Helios.

    To configure, refer to Destination Configuration.

Use SingleStore Flow

  1. Go to the Cloud Portal

    Navigate to the Load Data section.

  2. Select the Source Database

    Choose from:

    • MySQL by Flow

    • PostgreSQL by Flow

    • Oracle by Flow

    • SQL Server by Flow

    • Snowflake by Flow

  3. Select the Destination Database

    On the Select Destination page:

    • Choose the workspace and the destination database. 

      Note: The workspace should be of the Standard type.

    • Under Connection details, choose an existing connection or create a new one, and enter the Connection name.

      Note: The Connection name must not start with a number, and cannot contain special characters, except for underscores. Spaces are allowed.

  4. Open the Flow Dashboard

    The Dashboard provides a central interface to configure, manage, and monitor the overall status of an Ingest or XL Ingest instance. It displays information about the source, destination, tables, replication schedule, and a checklist.

    Click Open Dashboard to launch the dashboard.

  5. Select Ingestion Type

    Choose Ingest or XL Ingest from the Programs panel on the right.

  6. Complete the Checklist

    Begin the data pipeline by following the steps in the Checklist:

    • Setup Source - Configure the source database. Refer to Source Configuration.

    • Setup Destination - Configure the destination database. Refer to Destination Configuration.

    • Setup Tables - Configure the tables to be ingested. Refer to Tables.

    • Setup Schedule - Define the replication schedule. Refer to Schedule.

  7. Start the Pipeline

    After completing the Checklist, start the pipeline from the Operations tab. The job begins based on the defined schedule.

    Refer to Operations for detailed information.

  8. Monitor and Manage the Pipeline

    Use the following tabs to track performance, troubleshoot issues, and adjust settings.

    • Operations - Provides options to manage and troubleshoot the data pipeline, and handle schema changes.

    • Settings - Contains configuration options for the Flow environment. Refer to Settings.

    • Reports - Used to generate reports and view table performance data, organized by day and month. Refer to Reports.

    • Logs - Monitors the progress of extract and load operations. Refer to Logs.

Remarks

For additional information and reference, refer to:

  • SingleStore Ingest

  • SingleStore XL Ingest

  • Appendix

  • SingleStore Operational FAQ

Last modified: September 25, 2025

Was this article helpful?

On this page

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