Data Control Tower (DCT) is a unified data management platform used to enable API-driven DevOps workflows with continuous data and centrally manage the entire data estate for all Delphix customers. The core of DCT focuses on a centralized, container-based deployment architecture with a robust API library that enables automation and management across multiple Delphix Continuous Data engines. The DCT container form factor allows customers to self-host on their preferred public or private cloud environment.

The latest, 2.1 release of DCT features foundational UI elements that will culminate in a robust administrative and reporting UI delivered in the upcoming 3.0 release. The 2.1 UI focuses on login and “getting started” pages as well as an infrastructure overview for inventory management along with a storage capacity report.

Supported APIs

  • Engines - List engines connected to DCT
  • Environments - List environments across Engines
  • Datasets - List sources, dsources and vdbs across Engines
  • Snapshots - List Timeflow Snapshots for a dataset
  • Bookmarks - Bookmark a point in time in a VDB to ease the process of restoring the VDB later to that point in time
  • VDB Provisioning - Provision Oracle single instance, MSSql or Sybase ASE databases
  • VDB operations - Enable, Disable, Start, Stop, Delete, Refresh, Rewind VDBs
  • VDB Groups - A new grouping mechanism used in conjunction with bookmarks that was previously supported by VDB Templates in the Self Service module
  • Jobs - Monitor progress of aynschronous tasks
  • Reporting - Query across multiple engines to list storage capability, VDB inventory and dsource inventory
  • Connectivity - Checks connectivity between an engine and a remote host machine


  • Automation APIs to enable automating complaint data within DevOps pipelines (DCT

  • Reporting APIs to provide central reporting across many Delphix engines (DCT

  • Terraform Provider for Delphix support for data infrastructure automation (DCT
  • Engines versions supported (Virtualization only - masking support will be a future addition)
  • Connections to engine over HTTPs (self-provided certificate authority when necessary)
  • Username/password to authenticate with engines stored in the API Gateway or provided via password vault
  • Hashicorp vault supported
  • Audit logging via Nginx access log, self-configured Docker logging to go to fluentd, splunk, etc.
  • Native APIs keys supported for MCAPIGW authentication, OAuth2.0 provided via nginx module
  • OpenAPI 3.0 spec (self-generated client libraries with open source tooling)