Technical Documentation

For the CTO, architect, or technical decision-maker evaluating CDC for adoption. These pages judge the platform on its merits: its value, its architecture and integration model, its governance and security, its deployment and operations, its observability, and its compliance alignment, all at evaluative altitude, without descending into implementation detail.

Start here: The data-control value proposition for the why, then Architecture overview for the how. The remaining topics go deep on the dimensions an evaluation scrutinises.

The case and the design

• Value: the case for a data-control layer between source systems and consumers: dependency inversion, and what the layer standardises.
• Architecture: the runtime shape (Master and Engines), the process-driven execution model, the plugin framework, and the governed data catalogue.
• Integration: how CDC sits between ERP/CRM/LOB/SaaS sources and analytics, integration, AI, and new-product consumers, and why what is built on top does not break when sources change.

Control and trust

• Governance: where enforcement sits, the fail-closed stance, the two-phase tamper-evident audit trail, and governed domain models.
• Security: the default-deny posture, identity and authentication, and the write-only secrets store.
• Compliance: how the platform’s mechanisms map onto GDPR, NIS2, and due-diligence obligations.

Running it

• Deployment: the deployment shapes, sharding and tag-based placement, the scaling model, and the production-operations runbook.
• Observability: the OpenTelemetry-based telemetry, health probes, and how a governed operation is traced end to end.