Regulator-trusted infrastructure for the agent era.

A foundation-governed registry of authority-anchored rule bundles.

An open SDK that fetches the bundle for each market your agent operates in, classifies the agent's risk tier, and enforces the obligations attached to that tier as runtime invariants.

A regulatory channel — separate from your engineering observability — that produces attestable evidence for operator and regulator, per-recipient encrypted and anchored to a public transparency log.

Regulators verify directly, without touching customer infrastructure.

Where we sit

The regulatory-perimeter layer of your AI stack.

Your engineers already have observability. Your compliance team already has documentation tooling. What no one has is the layer in between — the one that takes a regulator's published rules, enforces them inside your agent at runtime, and produces evidence the regulator can verify directly.

That layer is what Iqrar is. One wrapper around your agent. Every jurisdiction you ship in. Obligations enforced where the LLM call actually happens, not in a quarterly PDF.

If you already run LangSmith, Galileo, or a governance dashboard like Credo AI — keep them. Iqrar sits at a different boundary and the composition is explicit.

Three audiences, three paths

For regulators

Distribute rules at the speed of code, with foundation-governed neutrality.

For enterprises

Operational visibility for AI agents. Audit-ready by default.

For developers

Open SDK. Documented protocol. Cryptographic audit trails by default.

Etymology

Iqrar (إقرار) is the Arabic word for binding voluntary self-declaration — the legal doctrine, established across 1,400 years of jurisprudence in the region we are starting in, that a person's voluntary public formal acknowledgment of a fact is binding evidence. The venture is named after the legal principle our engineering implements, in the language of that tradition.

Architecture

Three layers, one chain of custody.

Three-layer architecture: foundation registry signs rules, SDK fetches and verifies them, observability platform routes telemetry to operator and regulator. Foundation registry Regulators author rules Foundation signs bundles Open SDK Agents declare themselves Verify signatures locally Observability Hash-chained telemetry Routed to operator + regulator Regulators verify directly — no access to customer infrastructure required
The foundation governs the rules; the SDK consumes them; the observability platform routes the resulting telemetry. Each layer's output is cryptographically signed by the layer below it, so a regulator can verify what an agent did under which rule without needing access to the operator's systems.

The foundation

The Iqrar Foundation is in formation. It will govern the rules repository and the protocol specifications under a board that includes regulators, regulated firms, and independent technical stewards. The for-profit Iqrar operates the SDK and observability platform under contract with the foundation — one of multiple potential infrastructure operators authorised to do so.

iqrar.foundation →

The foundation governs the rules. Iqrar operates the infrastructure under contract.

Iqrar

Platform

Audiences

Company

© 2026 Cortex Innovations (Pty) Ltd.Iqrar is a working name pending trademark clearance.Powered by Stratafy