Start•stable•Updated 2026-09-03

What is Kadryn?

Kadryn connects AI usage and spend to business context, decision workflows, governance controls, and post-change measurement.

Kadryn connects AI usage and spend to business context, decision workflows, governance controls, and post-change measurement.

This factual definition is independent of category, audience, hero, CTA, or homepage treatment experiments.

Is Kadryn an AI Gateway?

No. Gateway is one execution and control path inside the broader Kadryn product; it is not the definition of Kadryn.

Does Kadryn require Gateway?

No. Direct Ingest supports observation and enrichment without routing all production traffic through Kadryn.

Use Gateway-based caps and policies where active runtime enforcement is configured. A plan capability does not by itself mean that a workspace or request path has enabled Gateway enforcement.

See Gateway vs direct ingest for the implementation boundary.

What can Kadryn connect spend to?

Supported business context can include project, team, feature, customer, and environment information where that context is available to the product. Spend association is separate from explicit organizational decision ownership.

See Allocation and ownership for the attribution boundary.

Can budgets or alerts block spend?

A budget is not a hard cap. An alert does not by itself block a request. Configured caps and policies can enforce limits on the relevant Gateway control path.

See Budgets, caps and policies.

What does Kadryn measure after a change?

Kadryn keeps product measurement states distinct: Modeled / Estimated → Applied Change → Observed / Measured Outcome → Workflow Confirmed.

An observed or measured outcome does not establish causal ROI, and workflow confirmation is not an independently audited financial ROI conclusion.

See Savings and post-change measurement.

Where are commercial and trust facts authoritative?

  • Pricing owns public plan and price presentation backed by canonical Product Authority.
  • Integrations documents supported providers and integration paths.
  • Security is the public trust surface for already-authorized security and data-processing facts.