Open source

Open-source infrastructure for sovereign AI discovery.

An open specification and a generic platform any country, city, telco or public-infrastructure operator can deploy to create a sovereign registry of locally relevant AI resources - it points to them, never hosts, executes or intermediates them.

What it is

The trusted discovery layer for sovereign AI

An AI Registry tells people, developers and AI systems what sovereign AI resources exist, who provides them, why they're locally relevant, and where to find them. It exposes structured metadata and stable identifiers.

publish expose consume consume Providers publish resources AI Registry exposes resources air:// AI agents Developers People
What gets listed

Three resource types.
Composable by AI.

A registry covers three kinds of sovereign AI resource - models, agents and skills. Each has its own listing template and stable AIR-ID, so consumers and AI systems can find and combine them programmatically. Each resource must meet a published sovereignty test.

airegistry · /registry
Registry resources listing
Listing criteria

The sovereignty test.

A submission must cite at least one sovereignty basis and provide concrete evidence - a referenced law, dataset, institution, language asset or cultural artefact. Reviewers apply a published checklist before elevating a resource's status.

01

Local law

Encodes local legislation, regulation, official process or professional obligation.

02

Local data

Uses local datasets, records or locally collected knowledge.

03

Local systems

Integrates with or describes local institutional systems and workflows.

04

Local language & culture

Supports local language, culture, norms or context.

How It Works

From submission to use.
Six transparent steps.

1

Submit

Provider submits the resource with metadata and sovereignty evidence.

2

Review

Reviewer applies the sovereignty rubric and records reviewer notes.

3

Publish

Operator publishes the listing and issues the stable AIR-ID.

4

Discover

Consumer finds the resource through the portal or discovery API.

5

Use

Consumer calls the provider directly - runtime never touches the registry.

off-registry · direct to provider
6

Maintain

Provider keeps metadata accurate; status reflects any changes over time.

Admin portal

Govern the registry end to end.

Review submissions against the sovereignty rubric, publish listings and issue stable AIR-IDs, manage providers and branding, and track every change through a complete audit trail.

  • Submission review & sovereignty checklist
  • Publishing & AIR-ID issuance
  • Provider & branding management
  • Full audit log
admin · airegistry
Admin dashboard Audit log Providers management Resources management
provider · airegistry
Provider dashboard Submit a resource Submissions list Manage resources
Provider portal

Submit and manage your resources.

Onboard as a verified provider, submit models, agents and skills with sovereignty evidence, and keep listing metadata current.

  • Guided submission workflow
  • Sovereignty evidence upload
  • Listing status & updates
Deploy your own

Set up a sovereign registry
in minutes.

Node 20+, pnpm 9+ and PostgreSQL 14+ (a bundled compose file provisions one). Clone the reference implementation, set your jurisdiction, and run.

quickstart · bashCopy
# clone the open-source reference implementation$ git clone github.com/MauritiusTelecom/ai-registry$ pnpm install$ cp .env.example .env # set DATABASE_URL + jurisdiction$ docker compose up -d postgres$ pnpm db:push && pnpm db:seed$ pnpm --filter @airegistry/portal dev# → http://localhost:3000
Reference deployment

Spearheaded by Mauritius Telecom.

airegistry.mu is the live reference deployment - the first instance, and the proof the platform works in production.

air://airegistry.mu
airegistry.mu home
Home · sovereign discovery
air:///providers
airegistry.mu providers
Providers · verified operators
air:///registry
airegistry.mu resources
Resources · models, agents, skills
Who it's for

Built to be forked.

Contributions are welcome from across the digital public infrastructure community.

Telcos
Government digital agencies
Sovereign cloud operators
Public-interest tech foundations
Regional standards bodies
Individual developers
FAQ

Frequently asked questions.

No. It lists, identifies, describes and helps discover resources - it does not host, execute, authorise or intermediate them. Providers operate their own resources; hosting environments run the workloads. The registry is never on the runtime path.
Yes - that's the point. AI Registry is a generic open-source platform under Apache-2.0. Any country, city, telco or public-infrastructure operator can deploy it with a configurable jurisdiction. Customisation is layered, so most operators deploy without forking.
A stable identifier under the dedicated air:// URI scheme - air://{domain}/{type}/{provider}/{resource}. It is a unique identifier for each resource published in the registry.
A submission must cite at least one of: local law, local data, local systems, or local language and culture - with concrete evidence such as a referenced statute, dataset, or institutional integration.
A TypeScript pnpm + Turborepo monorepo: a stable @airegistry/core (Prisma + PostgreSQL), a forkable Next.js @airegistry/portal exposing REST and MCP endpoints, plus public, ui-kit, plugin-host and a forthcoming sdk package.
Provider verification binds a listing to its rightful operator via DNS and email proofs. It does not imply endorsement of the resource itself - listing ≠ endorsement.
It's at v1.0 stable enough to deploy a reference implementation and stress-test with partners.
Open source · Apache-2.0

Deploy a sovereign registry.

Deploy the open-source reference implementation, configure it for your jurisdiction or ecosystem, and publish trusted AI resources in one discoverable place.