Credo AI governs your organisation’s AI portfolio. Grecta determines whether a specific product may be placed on the EU market. Credo AI is an enterprise AI governance platform. It builds an AI registry across the organisation, scores each AI system against policy packs, automates regulatory alignment with the EU AI Act, the NIST AI RMF and ISO 42001, and produces risk dashboards, model cards and audit artifacts. It sells to large regulated enterprises and describes itself as the operating system for trustworthy AI. Grecta is product safety compliance infrastructure. It turns EU product law into engineering tickets, release gates and a public verification page your buyers can check. The short answer If you have a portfolio of AI systems and need to show your board and your regulator that you govern them consistently, buy Credo AI. If you place a product on the EU market and need to establish which obligations reach that product across every regime that applies to it, and stop the release that would breach one, buy Grecta. The distinction that matters is the unit. Credo AI’s unit is the AI system in an inventory. Grecta’s unit is the product placed on the market. Those sound close and are not, because a regulated product is rarely only an AI problem. At a glance GrectaCredo AIWhat it governsThe product you place on the EU market.The AI systems your organisation builds, buys and deploys.Unit of valueThe product. Price scales with products and frameworks in scope.The AI system in the registry. Price scales with portfolio size and seats.The core questionMay this product ship, and what has to be true first?What AI do we have, how risky is each one, and does it meet our policies?Main outputA settled classification, tickets in the backlog, a release cleared or blocked, a priced exposure, a live verification page.An AI registry, risk scores, dashboards, model cards and audit artifacts.Primary buyerHead of product, VP engineering, CTO, regulatory affairs.Chief AI officer, chief risk officer, head of AI governance, compliance.Regulatory focus26 EU product frameworks, article by article.AI-specific frameworks: EU AI Act, NIST AI RMF, ISO 42001, plus pre-built policy packs.How answers are reachedDeterministic resolution against a clause map. Same product in, same obligations out, with the clause behind every answer.Policy-as-code. Models are validated against the policies you configure.Where it actsIn the release pipeline. Jira and Linear, pre-flight gates, the verification page.In the ML pipeline and the governance workflow. MLflow, SageMaker, Vertex AI.Who it is built forAny company placing a digital or connected product on the EU market, including SMEs and small mid-caps.Large regulated enterprises and federal agencies. The difference that matters: portfolio governance against product conformity Europe now regulates software the way it regulates machinery. The obligation attaches to the product placed on the market, and it attaches under every regime that covers that product, not only the AI one. An AI registry answers a governance question. It tells you what AI you hold, scores each system against the policies you set, and gives your risk committee a dashboard. That is a real and necessary job in a large enterprise with hundreds of models, and Credo AI does it at that scale. It is a different question from conformity. Conformity asks whether this product, with this intended purpose, in this classification, may lawfully be placed on the market, which assessment route applies, what the technical file must contain, and what has to be true before the next release ships. That question is settled article by article against the law rather than scored against internal policy, and its answer changes when the product changes or the law changes. Why a product is rarely only an AI problem Take an AI-enabled patient monitor. It is a medical device under the MDR, so its AI Act high-risk obligations arrive through Annex I and apply from 2 August 2028, assessed by a notified body inside the existing MDR procedure. It is a product with digital elements, so the Cyber Resilience Act reporting obligations have applied since 11 September 2026 unless the MDR exclusion in Article 2 removes it. It is software, so Directive (EU) 2024/2853 on liability for defective products reaches it. Its clinical data engages the GDPR. An AI governance platform addresses one of those four. The other three are product law, and they are where the market access risk sits. A registry entry scored green against an AI policy pack does not tell you whether the device can be CE marked. Regulatory coverage: Grecta vs Credo AI Based on each vendor’s published framework coverage as at November 2026. RegimeGrectaCredo AIEU AI ActYes, article by article per product, each obligation carrying its application dateYes, regulatory alignment and policy packsNIST AI RMFYesYesISO 42001YesYesEN 18286:2026Yes, clause level, the first harmonised standard cited under the AI ActNot named in published coverageCyber Resilience ActYesNot named in published coverageMDRYesNot named in published coverageIVDRYesNot named in published coverageProduct Liability DirectiveYesNot named in published coverageMachinery RegulationYesNot named in published coverageData ActYesNot named in published coverageGDPRYesMay fall within the pre-built policy packs, not individually namedNIS2 and DORAYesNot named in published coverage Credo AI publishes coverage of the EU AI Act, the NIST AI RMF, ISO 42001 and more than twenty standards in pre-built policy packs. The standards in those packs are not individually listed. Grecta resolves 26 EU frameworks, of which the AI Act is one. How each one handles the EU AI Act GrectaCredo AIBanned practices, Article 5Gated at intake. A product that trips Article 5 is stopped before scoping continues.Assessed as a policy control within the governance workflow.Risk classification, Article 6Settled deterministically per product, with the clause and the application date, including which Annex limb applies and therefore which date governs.Risk assessment and classification against the policy pack.Legal role, Articles 3 and 25Provider, deployer, importer or distributor settled at intake, including where fine-tuning makes you a provider.Captured as registry metadata.Quality management, Article 17 and EN 18286QMS blueprint mapped to EN 18286 clauses, copied into Jira or Linear as tickets against the article that requires them.Governance workflow and policy evidence. EN 18286 not named in published coverage.Technical documentation, Annex IVGenerated from the product record and retained for the period each regime sets.Auto-generated model cards and audit artifacts.Conformity assessment route, Article 43Settled, including whether internal control under Annex VI is available or a notified body under Annex VII is required.Not its purpose.Change managementTwo events force a recompute: you ship, or the law changes. Releases are cleared or blocked before they ship.Lifecycle tracking in the registry, with re-assessment on request. What each platform actually does CapabilityGrectaCredo AIOrganisation-wide AI inventoryNoYes, the AI registryModel risk scoringNoYesFairness and bias metrics in the ML workflowNoYesModel cards and audit artifactsNoYesVendor and third-party AI risk portalNoYesExecutive risk dashboardsNoYesML platform integrationNoYes, MLflow, SageMaker, Vertex AIPer-product obligation resolution across 26 frameworksYes, article by articleNot its purposeObligation compressionYes, the AI Act’s 188 obligations resolve to 68 controls where one piece of evidence discharges severalNoEngineering backlog integrationYes, Jira and Linear, tickets written against the articleNoRelease gatingYes, cleared or blocked before shippingNoPre-code change impactYes, a planned feature tested in under a minute before the code is writtenNoPriced exposure for financeYes, an exposure figure and a CFO one-pagerNoPublic verification page for buyersYes, a live page at a public URL with a 90-day freshness clockNoAuthorised representative, Article 22 of the AI ActYes, through European Compliance Suite in EstoniaNo Pricing GrectaCredo AIModelPer productEnterprise contract, customPublished pricingYesNo, quote onlyEntryFree intake and scoping, no cardSales process and demoPilot1,500 euro per product, two weeksNot publishedPlatformFrom 10,000 euro a yearNot publishedTime to first answerThe same day, from the free intakeImplementation involves technical integration with ML infrastructureWhat the price depends onNumber of products and frameworks in scopeScale, features and professional servicesWho can realistically buy itAny company placing a product on the EU marketOrganisations with ML infrastructure and a data science team Grecta prices per product because the obligation attaches to the product. Adding fifty models to a registry does not change what the Cyber Resilience Act requires of your gateway. Adding a second product does. Which one should you choose? Choose Credo AI if: You hold a large portfolio of AI systems and models Your problem is visibility and consistency across that portfolio You need board-level and regulator-facing risk reporting You govern third-party and vendor AI at scale You have ML infrastructure and a data science team to integrate with Choose Grecta if: You place a digital or connected product on the EU market Your product triggers more than one regime at once, such as the AI Act with the CRA, the MDR or the Machinery Regulation You need the conformity assessment route and the application dates settled, not scored Procurement keeps asking for proof you cannot produce quickly You want the work in the engineering backlog rather than in a dashboard You need an authorised representative established in the Union Use both if You are a large enterprise that both governs an AI portfolio and ships regulated products Credo AI answers to your risk committee, Grecta answers to your notified body and your buyers Portfolio governance and product conformity are separate obligations and neither discharges the other FAQ Is Grecta an alternative to Credo AI? Only if your AI governance requirement is in fact a product conformity requirement, which is often the case for a company that builds and ships one or a few regulated products rather than running a portfolio of internal models. For a large enterprise governing hundreds of AI systems, they are complementary and address different obligations. We already have an AI registry. Is that not enough for the AI Act? A registry tells you what you hold and how it scores against your policies. The AI Act asks a different set of questions about each product placed on the market: which Annex limb applies and therefore which date governs, what the legal role is, whether internal control under Annex VI is available or a notified body under Annex VII is required, and what Annex IV documentation must contain. Those are determinations rather than scores. Credo AI covers the EU AI Act. Why would we need more? Because a regulated product is rarely only an AI problem. An AI-enabled medical device sits under the MDR, the AI Act, the Cyber Resilience Act and the Product Liability Directive at the same time, with four different timetables. The AI Act is one of the 26 frameworks Grecta resolves. What does product level actually mean? Each product has its own record. Obligations are resolved for that product’s intended purpose and classification, the gaps are written into that product’s backlog, releases of that product are gated, and that product gets its own verification page. A company with four products has four records, four sets of obligations and four timetables. Does Grecta do bias and fairness testing? No. Grecta establishes that Article 10 data governance and bias obligations apply to a given product, what evidence each requires and when it is due, and writes that work into the backlog. The testing itself is done in your ML stack or by a specialist tool, and Credo AI is strong at that part. How does Grecta reach its answers? Is it a language model? The resolution is deterministic. A product’s attributes are resolved against a clause map, article by article, and the clause behind every answer is shown. That is why the same input returns the same output, and it is the opposite design choice from policy scoring or generative reasoning. What happens when the law changes? Every product record is recomputed and the affected products are flagged. Earlier determinations are not overwritten, so you can still show what the position was on the date you assessed it. Regulation (EU) 2026/1744, the Digital Omnibus, is the obvious recent example. It entered into force on 27 July 2026 and moved the AI Act high-risk dates to 2 December 2027 for Annex III and 2 August 2028 for Annex I. Can Grecta produce our technical documentation? Yes, generated from the product record, with the retention period each regime sets. The difference from a model card is that it is derived from a dated determination of which obligations fired for that product, so it can be tied back to what the law said when the assessment was made. Does Grecta give legal advice? No. Grecta provides regulatory and conformity analysis. What does it cost to find out? Initial scoping is free and needs no card. Bring one product and we will settle its classification and legal role and show which obligations reach it with their application dates. Pilots are EUR 1,500 per product. Credo AI is a trademark of its respective owner. Grecta is not affiliated with, endorsed by or sponsored by Credo AI. Comparative statements describe each product’s intended purpose and publicly published capabilities as at November 2026 and are liable to change as either product develops. Where this page records that a regime is not named in published coverage, that reflects the vendor’s own published framework list and not a statement that the product cannot address it. This page is regulatory and conformity analysis and is not legal advice.