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.

Load Data with SingleStore Flow on Helios

On this page

Overview

SingleStore Flow (or, "Flow") is SingleStore's data migration and change data capture (CDC) solution which is comprised of two primary components:

  • SingleStore Ingest, also referred to as "Ingest," transfers the schema for all tables, moves table data for tables up to 10GB in size, and handles ongoing CDC for all tables into SingleStore.

  • SingleStore XL Ingest, also referred to as "XL Ingest," handles the initial transfer of large tables by breaking them into smaller logical partitions. It then copies multiple partitions from the source to the target in parallel. This helps transfer large tables in a reasonable amount of time.

Flow is integrated into the Cloud Portal as a part of the Load Data workflow. This service enables loading and synchronizing data from supported databases into SingleStore, without the need to install or manage any infrastructure.

Flow supports the following source databases for transfer to SingleStore:

  • Oracle

  • Oracle RAC

  • Microsoft SQL Server

  • MySQL

  • PostgreSQL

  • Snowflake

  • Any JDBC-compliant database (non-production preview, available for testing)

  • MongoDB® (private preview)

Why Use SingleStore Flow

Key benefits of using SingleStore Flow:

  • No-code setup: Configure end-to-end migration via the Flow UI.

  • Automatic schema handling: Analyze the source database and automatically create the required schema in the target SingleStore database.

  • Real-time visibility: Monitor progress, view live logs, and troubleshoot quickly.

  • High throughput: Use XL Ingest to parallelize large table loads by chunking source data, significantly reducing migration time.

Choose the Right Flow Deployment

Flow is available in two deployment options:

  • A Self-Managed Flow Application

  • Flow on Helios

Both provide the same data migration and CDC features, but differ in how they are deployed and used.

The following table outlines these two options:

Deployment Option

Self-Managed Flow Application

Flow on Helios

Description

Installed and operated in your own environment.

Self-managed, installation required.

Provides control over where the application runs and how it integrates with your system.

Runs inside the Cloud Portal.

Fully managed by SingleStore, no installation required.

A Flow instance is provisioned directly in the UI, and usage is billed only while the instance is running.

When to Use

When deployment placement or control over environment matters the most, such as replicating large volumes of data from an on-premises source to SingleStore.

When convenience and low operational overhead matter more than placement.

When your data sources and destinations are in the same cloud region, along with your Flow on Helios instance, ensuring excellent performance along with convenience and robustness.

For more details on the Self-Managed Flow application, refer to Load Data with SingleStore Flow.

In this section

Last modified: September 29, 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