qodiqa
SpecificationRun a simulation

About · Investors

The control and evidence layer for AI execution.

AI systems are starting to act on their own: they call tools, move data and trigger payments. qodiqa is the open layer that decides before they act, and proves afterwards what was allowed.

Most controls around AI sit beside the model and report after the fact. qodiqa sits on the path itself. A request carries signed, time-limited consent, a policy decides, and only then is the provider called. Every outcome, allowed or refused, becomes a signed receipt that anyone can check offline, without an account and without trusting us.

It is built, not promised. The standard is published as 32 open documents, the reference gateway and verifiers are public, and 797 documented functions run behind one execution path. Independent verifiers in JavaScript and Python check the same public test vectors.

Whoever runs AI in regulated or high-stakes settings will need evidence they can hand to a customer, an auditor or a regulator. The open standard earns that trust. The business is the commercial layer on top: enterprise identity, data-loss prevention, integration and support.

We are opening conversations with investors who back open infrastructure.

Read the specification

The thesis

Control has to exist where AI acts.

  • AI is starting to act

    Models now call tools, move data and trigger actions on their own, so approval given once is not enough.

    How a request is checked
  • Policy on paper is not control

    Promises and after-the-fact logs do not stop an action; control has to exist where execution happens.

    See the reference gateway
  • Regulation asks for evidence

    The EU AI Act asks for record-keeping and human oversight of high-risk systems, and ISO/IEC 42001 sets out an AI management system.

    See how qodiqa maps to them

What exists today

Built in public. Checkable in minutes.

  • An open specification

    A corpus of documents, from the core standard to conformance, with a CC BY 4.0 licence as stated by the repository.

    Read the specification
  • A reference gateway and an offline verifier

    Open code under Apache-2.0. What is built and what is not yet is stated on the gateway page.

    The gatewayThe verifier
  • Public test vectors

    Signed receipt cases made with published test keys, so any implementation can be checked against them. They are test data, not production receipts.

    Open the test vectors

How it becomes a business

Open standard, commercial services.

The standard and the reference code stay open. The business is built around them.

Open and free to adopt

  • The specification
  • The reference gateway
  • The verifier
  • The test vectors

Where a company is built

Direction
  • Managed and hosted deployments (planned)
  • Enterprise integrations and support (planned)
  • Conformance assessment and training (intended)
  • A trusted brand around the standard (intended)

Related documents

Cover of the one-page document What is qodiqa: Authorize first. Execute second.

What is qodiqa

An enforcement layer between applications and AI providers: authorize first, execute second.

PDF · 1 page · 92 KB · QODIQA-OP-1.0 · one page · v1.0 · 2026-10-29

Download PDF
Cover of the Global Industry Atlas, Edition 2026: 450 industry applications, one execution control principle.

Global Industry Atlas

A strategic atlas of pre-execution authorization across industries: 450 potential applications, not implementation status.

PDF · 52 pages · 3.3 MB · Edition 2026

Download PDF

All documents

Materials and contact

Start a conversation.

Write to usUse the contact form