The OMI spec is under heavy development, and every piece of it is subject to change. We are documenting the core primitives for sovereign application lifecycles. Join us in defining the v1.0 draft.
Documentation
Core Services
App Registry

App Registry

The App Registry is a specialized discovery and identity coordination service. Within the OMI ecosystem, it serves as the Single Source of Truth for an application’s cryptographic identity and its operational configuration.

While traditional registries simply store data, the OMI App Registry functions as a Service DNS, mapping a human-readable AppID to the cryptographic keys and service endpoints required to run a decentralized “Swarm” of infrastructure.

Core Responsibilities

  • Namespace & Identity Management: Acts as the registrar for developer namespaces (e.g., dev_agency) and ensures that only the holder of the Master Private Key can claim or modify an identity.
  • Cryptographic Key Distribution: Hosts the Public Master Key (for provisioning authorization) and the Public Auth Key (for user request validation), allowing third-party services to verify requests without pre-shared secrets.
  • Operational Orchestration (The “Service DNS”): Maps abstract AppIDs to physical service locations (URLs). It provides the “Discovery Records” that tell a CMS where to find the Billing Service or tell a Database where to find the Auth Provider.
  • Dependency Binding: Maintains the “links” between an application and its provisioned services, creating an auditable map of an app’s infrastructure.
Auth Provider