Support matrix
Supported means the mode and its prerequisites are named.
Every source mode declares maturity, mechanism, record behavior, environment requirements, and evidence across multiple test tiers.
10
Supported capture paths
Production readers across five families.
11
Shipped destinations
Product connectors only.
Tiers
Evidence by mode
Keep residual limits visible.
Reader evidence
Test the exact engine and mode.
Goldens, reconciliation, transactions, type matrices, stress, end-to-end delivery, cross-mode parity, and versions cover different failure classes.
✓ Conformance and source-truth reconciliation
✓ Commit, rollback, savepoint, and restart
✓ Type and physical-layout coverage
✓ Cross-mode and multi-version evidence
Deployment evidence
Carry conditions into the production plan.
Managed APIs, log access, source versions, layouts, recovery, keys, and target behavior remain part of the supported contract.
✓ Prerequisites and unsupported combinations
✓ Before-image and schema-event behavior
✓ Live environment and benchmark boundaries
✓ Fail-closed identity and timeline checks
Keep exploring
See the connected parts of the platform.
Certify the path you will deploy.
Bring exact versions, hosting, tables, types, and workload. We will create an acceptance plan.