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.

SingleStore Ingest

On this page

Overview

SingleStore Ingest (“Ingest”) is real-time data replication software that replicates data from various sources to SingleStore. It is one of the primary components of SingleStore Flow. Ingest offers high performance, enabling real-time Change Data Capture from sources with zero load on the source systems. It captures changes and transfers them to the target system. It automates the creation of either an exact copy or a time-series copy of the data source in the target. It first performs a full initial load from the source, then incrementally merges changes to SingleStore. The entire process is fully automated.

Supported Source Databases

Ingest supports the following database sources:

  • Oracle

  • Microsoft SQL Server

  • MySQL

  • PostgreSQL

  • Snowflake

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

  • MongoDB (private preview)

Contact your SingleStore account team or SingleStore Sales if you want to move data from a source not listed above.

Ingest Architecture

Ingest replicates data from any supported source to a SingleStore destination database. It is a fully self-service, automated data replication tool.

SingleStore Flow, of which Ingest is a part, offers several deployment strategies for its customers, including:

  • Standard deployment in an AWS environment

  • High Availability deployment in an AWS environment

  • Hybrid deployment using both on-premises and cloud infrastructure

  • Fully on-premises deployment

Flow components can be deployed in Google Cloud and Microsoft Azure as well. AWS components and services are referenced here as an illustration of a common type of deployment.

Ingest uses log-based Change Data Capture for data replication. The following is the technical architecture diagram that illustrates the standard setup in an AWS environment.

The following diagram serves as the reference for all setup instructions.

Estimated deployment time: Approximately 1 hour

Ingest / AWS Service Integration

The following is the Ingest architecture which showcases integration with various optional AWS services in a standard deployment.

This architecture diagram illustrates a standard deployment that highlights the following features:

  • AWS services running alongside Ingest.

  • Recommended Flow architecture for a VPC in AWS.

  • Data flow between the source database, AWS, and SingleStore destination database, including security and monitoring features.

  • Security, including IAM, organized in a separate group and integrated with Ingest.

Ingest High Availability Architecture

The following High Availability architecture explains how Ingest is deployed in a multi-AZ setup. In the event of an instance or AZ failure, it automatically scales to another AZ without incurring any data loss.

Estimated deployment time: Approximately 1 day

Ingest Hybrid Architecture

Ingest also offers a hybrid deployment model that combines on-premises services with those in the AWS Cloud. Ingest can be easily set up on a Windows server in an on-premises environment. The SingleStore destination endpoint resides in the AWS Cloud that creates a hybrid model. SingleStore recommends secure connectivity between on-premises and AWS services, which can be achieved using a VPN connection or AWS Direct Connect.

Estimated deployment time: Approximately 2 hours to 1 day

In this section

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