Governance workspace where an enterprise records AI use cases, models, agents and third-party AI vendors, runs questionnaire-driven reviews, and tracks control and risk libraries with task assignment. A Python/TypeScript SDK writes the same objects programmatically. Evidence reviewed covers workflow structure, not independent verification of governance outcomes.
commercial · generally available · Research snapshot 2026-09-06
Show me how a new agent use case moves from intake questionnaire through control review to a governance status a regulator-facing auditor could read.
Capabilities and evidence
Support labels reflect the supplied research. Documentation and vendor claims are not independent product tests. “Not established” means the researcher did not find support; it does not prove a capability is absent.
Documented by provider
Product documentation describes reviews, questionnaires, governance plans, governance status, a control library and a risk scenario library, plus triggers/actions and a beta vendor registry.
Limit: Documentation index confirms these modules exist; it does not show coverage depth of the control library or any assessment of control effectiveness.
A documented SDK (Python and TypeScript) lets teams create and update use cases, register models and track vendors against the Credo AI API, with cookbooks referencing Jira and ServiceNow.
Limit: SDK docs show API surface and example cookbooks; they do not establish supported production integrations or rate/scale limits.
Vendor product page states the platform discovers and catalogs AI systems, agents, vendors and models, offers agent cards, shadow AI detection and prebuilt policy packs for frameworks including the EU AI Act and NIST AI RMF.
Limit: Marketing page only. It does not evidence detection method, coverage, or that using policy packs makes an organisation EU AI Act compliant.