Gateway vs Direct Ingest
Understand Kadryn observation through Direct Ingest and conditional runtime enforcement through Gateway.
Direct Ingest and Gateway are different product modes. Gateway is not mandatory for using Kadryn.
What is Direct Ingest?
Direct Ingest supports observation and enrichment without routing all production traffic through Kadryn.
Direct Ingest is not inline runtime enforcement. Do not interpret observation, attribution, alerts, or post-change reporting as request blocking.
What is Gateway for?
Use Gateway-based caps and policies where active runtime enforcement is configured.
Configured caps and policies can enforce limits on the relevant Gateway control path. Gateway capability on a plan does not by itself establish that a workspace or request path has enabled enforcement.
Does Kadryn require all AI traffic to pass through Gateway?
No. Direct Ingest can provide observation without routing all production traffic through Kadryn. Gateway becomes relevant when active runtime control is required and configured on the applicable path.
What should not be inferred?
- Direct Ingest does not block requests.
- An alert does not itself block a request.
- A budget is not a hard cap.
- Gateway is not Kadryn’s product definition or a mandatory architecture for all users.
- Plan entitlement is not the same as workspace-level activation.