Three production patterns that cover the majority of Conduvia deployments. Each one is a blueprint — expand, mix, or compose.
Conduvia enforces schema contracts, PBAC authorization, and tenant isolation across every integration point. Producers think they are talking directly to the platform. Downstream thinks messages arrive from the system. Conduvia is invisible infrastructure in between.
AI agents become a recognized producer type with additional ABAC attributes. Token budgets, PII masking, and bounded prompt injection checks are per-alias extensions — never universal platform primitives. Conduvia governs what enters and leaves the platform; the workflow engine governs how AI agents behave inside.
Conduvia is multi-tenant by design. Tenant context propagates from admission through Kafka through transforms through delivery. The TenantConfigResolver resolves per-tenant credentials at sink runtime — producers know nothing about downstream delivery mechanics.