# SingleStore Ingest ## 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](https://www.singlestore.com/contact/) 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 ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt3208fa2b1092e81e/6a2c439d56043cd8810ac1a0/singlestore_flow_ingest_architecture-jYcveh.png) ## Ingest / AWS Service Integration The following is the Ingest architecture which showcases integration with various optional AWS services in a standard deployment. ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt9341d4dac76d1021/6a2c4214984050354da5c55d/singlestore_flow_ingest_aws_service_integration-VjcVyi.png) 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 ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt9313e76f226c7dff/6a2c4215ce0ebe56e2fe7c32/singlestore_flow_ingest_ha_architecture-DqcHOt.png) ## 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 ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt84486e87b38a6464/6a2c43a903b3730777908176/singlestore_flow_ingest_hybrid_architecture-H4LnW0.png) ## In this section * [Source Database Setup](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/source-database-setup.md) * [Destination Database Setup](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/destination-database-setup.md) * [Configure Ingest](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/configure-ingest.md) * [Dashboard](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/dashboard.md) * [Configure Source Database](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/configure-source-database.md) * [Configure Destination Database](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/configure-destination-database.md) * [Tables](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/tables.md) * [Operations](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/operations.md) * [Settings](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/settings.md) * [Reports](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/reports.md) * [Logs](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/logs.md) * [Appendix](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/appendix.md) *** Modified at: February 26, 2026 Source: [/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest/) (An index of the documentation is available at /llms.txt)