Platform / Multiple Data Planes. Single Control Plane.
The Control Plane Is in the Cloud. The Data Plane Stays Where Your Data Lives.
Manage your entire data integration operation from a single Control Plane while running Data Planes wherever your data lives - cloud, on-premises, or both.
Many Data Planes. One Control Plane.
One Control Plane can orchestrate multiple Data Plane deployments simultaneously - centralized governance without sacrificing architectural flexibility.
Control Plane - The management layer - cloud-hosted UI and scheduler. It owns orchestration, configuration, credentials, and governance: it decides what runs and when. It only controls; it never sees or stores your records.
Data Plane - The execution layer. It performs the actual extraction, transformation, and loading inside your own perimeter, where your data already lives. Your records never leave it.
- Credentials in your vault - never synced up
- Scales independently per deployment
Control Plane
runs in Dataddo Cloud
Never touches your payload data
UI
Visual workspace for teams to build, run and monitor pipelines
API
Programmatic interface to embed Dataddo in your own stack and workflows
MCP
Dedicated interface for AI & agents to access governed data in context
Orchestration
schedules, retries, dependencies
Governance & access
roles, policies, audit trail
Metadata & lineage
schemas, catalog, column lineage
Observability
run status, latency, alerting
Data Plane
Your data never leaves it
Isolated deployment
Hyperscalers
AWS
Azure
Google Cloud
Isolated deployment
EU Cloud Providers
Isolated deployment
On-Prem
Kubernetes
OpenShift
B
Bare metal
Data path stays local — inside your perimeter
Sources — inside your network
PostgreSQL
MySQL
Oracle
SAP HANA
Salesforce
A
Apache Kafka
+ 300 more
Destinations — your storage & consumers
Snowflake
Databricks
BigQuery
Redshift
A
Apache Kafka
+ any other
Sensitive Data Stays Private
Sensitive data can be processed exclusively within a private, on-premises Data Plane, while less sensitive workloads run in the cloud - all under a single management interface.
| Data Plane location | Typical data sensitivity | Why this setup |
|---|---|---|
|
Public cloud
AWS
Microsoft Azure
Google Cloud
|
Low to moderate - general business, marketing, and product data; sources that are already cloud-native. | Fastest to stand up and scales elastically. Best when the data has no residency restriction and often already lives in the same public cloud. |
|
Regional & EU sovereign clouds
EU sovereign clouds
Regional providers
Private cloud
|
Regulated / residency-bound - PII, financial, and health data governed by GDPR or local law. | Keeps processing inside a specific jurisdiction to meet data-residency and sovereignty rules, while still running as managed infrastructure. |
|
On-premises
Kubernetes
Red Hat OpenShift
VMware Tanzu
|
Highly sensitive / restricted - data that contractually or legally cannot leave the corporate perimeter. | Data never leaves your network. Required for air-gapped, classified, or locked-down environments; the Control Plane still manages it via metadata only. |
Talk to a Hybrid Deployment Specialist
Architecture review for on-prem and regulated-environment deployments. Get tailored guidance from one of our solutions engineers.