CData Sync

Deploy Sync Where Your Data Lives and Keep Full Control of Your Architecture

Deploy Sync in your cloud, within your virtual private cloud (VPC), inside your on-premises network, or as a managed service, while maintaining complete control over networking, governance, and performance.

Overview

Sync's architecture is built for secure, private-network operation, enabling Change Data Capture (CDC), warehouse replication, and reverse ETL pipelines to run within the network and governance model that your organization already maintains.



Deployment Models

1

Self-hosted in your cloud

Deploy Sync inside your Amazon Web Services (AWS), Azure, or Google Cloud environment so that it operates entirely within your security and networking boundaries. Jobs run inside your VPC with support for private endpoints, firewall controls, and your preferred orchestrator.

Best for:

  • Teams with strict network-isolation requirements
  • Security models that prohibit inbound access
  • Regulated cloud environments in financial services, healthcare, and energy

Capabilities:

  • Runs entirely inside your VPC
  • Supports private endpoints and firewall policies
  • Works with Amazon Elastic Container Service (ECS), Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), and Google Kubernetes Engine (GKE)
  • Uses your cloud's identity and access management (IAM) and governance controls
2

On-premise deployment

Run Sync inside your corporate network for workloads that cannot be made available to external services. Sync captures log-based and journal-based CDC from systems like Oracle, DB2, Informix, and PostgreSQL. Then, it delivers the data to cloud analytics through outbound-only connections.

Best for:

  • Legacy and operational technology (OT) systems that cannot traverse public networks
  • Manufacturing plants, utilities, telecom, and other regulated environments
  • CDC pipelines that require the lowest-latency access to on-premises data

Capabilities:

  • Directs log-based and journal-based CDC from on-premises databases
  • Secures outbound-only delivery to cloud targets
  • Supports isolated network zones and firewall-restricted environments
3

Hybrid Deployment

Many enterprises use Sync across both on-premises and cloud environments. An on-premises instance captures changes from Oracle or DB2, while a cloud instance prepares data for analytics and activates SaaS systems through reverse ETL.

Best for:

  • Modernization paths that span legacy systems and cloud warehouses
  • Teams that cannot alter existing network boundaries
  • Workloads that require both private-network access and cloud-scale processing

Capabilities:

  • Independent on-premises and cloud execution
  • Outbound-only replication from private networks
  • Reverse ETL and analytics orchestration in cloud environments
4

Fully Managed Cloud

Run Sync as a fully managed service with built-in high availability and no infrastructure to maintain. Customers choose when and how to apply upgrades, ensuring full control over change management while still benefiting from an operationally simple deployment.

Best for:

  • SaaS-to-warehouse replication
  • CRM and marketing automation reverse ETL
  • eams that prefer low-operational simplicity without managing servers

Capabilities:

  • Elastic job execution
  • Built-in monitoring, alerts, and retries
  • No infrastructure provisioning or maintenance

Architectural Benefits

Network-localized processing

Sync runs jobs where data resides, allowing pipelines to operate within your existing security and network boundaries. This approach eliminates the need for inbound firewall changes, reduces CDC latency, and supports more predictable cost and performance behavior.

  • Jobs execute inside private networks
  • Inbound firewall access is not required
  • CDC operates at lower latency
  • Throughput is predictable and shaped by your own infrastructure

Scalable job orchestration

Sync coordinates parallel processing and manages concurrency across large deployments. This ensures consistent performance for high-volume workloads without manual tuning.

  • Parallel task execution at scale
  • Concurrency management for large enterprise deployments

Operational insight

All deployment models include a unified operational view for monitoring throughput, latency, and job health. Teams gain clear visibility into CDC activity, pipeline performance, and error handling across environments.

  • Centralized dashboards across all deployments
  • Throughput, latency, and job health visibility
  • Insight into CDC capture and delivery behavior

Use Cases by Industry

icon

Energy and utilities

Sync supports private network deployments in segmented OT and IT environments. On-premises CDC from systems like Oracle or DB2 can be delivered to cloud analytics by using secure outbound-only connections.

  • On-premises CDC from critical OT/IT systems
  • Outbound-only delivery to cloud analytics
  • Compatibility with strict network segmentation
icon

Manufacturing

Plant-level systems often run in isolated networks that cannot make databases accessible externally. Sync captures Manufacturing Execution System (MES) and Supervisory Control and Data Acquisition (SCADA) data on-premises, while a cloud instance supports analytics and reverse ETL for ERP or CRM systems.

  • Local CDC capture from plant-floor systems
  • Cloud processing for analytics and operational reporting
  • Support for tightly controlled network zones
icon

Financial services

Financial institutions rely on VPC isolation and strict governance for data movement. Sync runs inside private cloud environments to meet governance controls, and it delivers CDC data reliably across multi-cloud architectures.

  • VPC-isolated operation for regulated data movement
  • CDC delivery across multi-cloud environments
  • Alignment with governance and compliance requirements

Deploy Sync Your Way

Choose the deployment model that best fits your architecture and security requirements, whether in your cloud, inside your VPC, or within on-premises environments.