Integrations · Streaming · Projected
Apache Kafka: projected connector
Strategic roadmap: bounded snapshot and replay windows from Kafka topics with schema-registry integration and deterministic transformations.
Projected Streaming
Strategic roadmap; not shipped. No delivery date is committed.
Not available yet. Strategic roadmap; not shipped. No delivery date is committed. The console does not offer it, and asking an agent for a connector it does not ship fails with the error code CONNECTOR_NOT_AVAILABLE; the product never fakes a connection.
What you can do today
There is no interim path through a shipped connector for this kind of source today.
Whatever route you choose, the export and every row-level step stay inside your network. You can evaluate the whole workflow now with the synthetic demo.
Capability matrix
Apache Kafka does not ship yet, so no capability is verified. The column shows what the design plans; plans are not commitments.
| Capability | Design intent |
|---|---|
| Discovery | Planned |
| Classification | Planned |
| Profiling | Planned |
| Masking | Planned |
| Deterministic masking | Planned |
| Entity-aware subsetting | Not planned yet |
| Relationship preservation | Not planned yet |
| Synthetic workflows | Not planned yet |
| Certification | Planned |
| Provisioning | Not planned yet |
| CI/CD | Not planned yet |
| Evidence generation | Planned |
How the connector is designed to prove read-only access
Designed: ACLs limited to READ/DESCRIBE on topics and the consumer group; never WRITE.
Design: bounded offset ranges only (no uncontrolled infinite stream, never in a trial), no offset commits on the customer's groups, schema-registry-aware decoding.
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Request this connector
We prioritise connectors by demand, engineering effort and strategic fit. Telling us that Apache Kafka matters to you is counted; it does not commit a delivery date.
All integrations · Streaming test data management · Guides · Start free