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
The OMI Provisioning Protocol

The OMI Provisioning Protocol

Standardized Workflows for Identity, Authority, and Infrastructure

The OMI Provisioning Protocol defines the cryptographic lifecycle of an application. It moves beyond traditional “API Key” management, replacing centralized control with a Sovereign Handshake that ensures developers own their identity and services own their logic.

This sequence is broken into three distinct architectural phases:

  1. The Birth (Provisioning)

    • Developer Identity & Namespace
    • Application Registration
    • Provisioning the Trust Anchor (Auth)
    • Provisioning Domain Services (The Swarm)

  2. The Life (Maintenance)

    • Cryptographic Key Rotation
    • Global Configuration Updates
    • Health Checks & Status Heartbeats

  3. The Exit (Sovereignty)

    • Service Decommissioning
    • Registry Migration
    • Identity Recovery (Guardian Keys)

Key Benefits of this Protocol

  • Zero-Config Security: Services automatically fetch the keys they need to trust each other based solely on the AppID.
  • Provider Agnostic: Swap an Auth provider or a Database without re-coding the entire application.
  • Cryptographic Sovereignty: The Developer holds the only key capable of authorizing infrastructure changes.