Every Conduvia module serves a single clear purpose within the two-layer architecture. Core modules are always deployed; optional modules are loaded where needed.
Governed ingress — intercept, validate, transform, publish. The synchronous policy intercept at the platform boundary.
Explore →Transport-neutral policy engine — validation logic, transform pipeline, idempotency, rate-limit, error shaping.
Explore →Control plane — connector lifecycle, worker task assignment, pause/resume/restart, status aggregation.
Explore →Egress data plane — execute sink tasks, deliver to endpoints, retry with backoff, DLQ routing.
Explore →Optional operations tooling — browse DLQ, filtered dry-run replay, rate-capped execution, audit trail.
Explore →Health, metrics, distributed tracing, structured logs, dashboards. Per-alias, per-tenant, per-connector.
Explore →These modules extend Conduvia for specific deployment needs.
Delivery adapters — Arka (5-channel), HTTP/Webhook (HMAC-signed), S3/Object Storage. Per-tenant credential resolution and quotas.
maskPII · hoistHeaders · coerceTypes · jsonPatch · tenantGuard. Deterministic, side-effect-free transforms.
JSON / Avro / Protobuf serialization — configured per alias or per sink.
Optional schema registry — JSON/Avro/Protobuf subjects, compatibility enforcement, lifecycle governance.
CLI tool — bootstrap Kafka topics with correct replication factor, retention, and compaction settings.