Skip to main content

Run a compute market on your terms

Deploy registry infrastructure with the access model, machine-readable discovery vocabulary, topology, and compatible market components your community requires.

Configuration first · HTTP registry · independently operated

Sovereign means the market infrastructure and governance can be independently operated. It does not mean the operator takes over seller pricing, buyer choice, or fulfillment.

Why operate with Arkhai

SCM lets a network, institution, or community operate the market surface without becoming the universal counterparty for every deal.

Operate sovereign infrastructure

Run registry and related market services on infrastructure controlled by the operator or community.

Choose the discovery shape

Support public, curated, private, or federated discovery without changing participant roles.

Define the market vocabulary

Select the machine-readable listing schema and filter specification buyers use to discover compatible supply.

Preserve participant authority

Shape access and composition without taking over seller policy, buyer aggregation, agreement, or delivery.

One market core. Different market boundaries.

Registry access can change without pretending that the operator owns every listing, negotiation, or physical resource.

Public

Open publication and discovery

Curated supply

Vetted publication with open discovery

Private

Authenticated publication and querying

Federated

Buyer clients query independent registries

Configure the market—not every deal

The clearest operator advantage is a precise control boundary.

Operator configures

Registry deployment, read/write access, listing and filter schema, curation, compatible domains, identity, settlement connections, arbitration integrations, reachability, and service topology.

Participants retain

Seller offers and policies, buyer requirements and aggregation, bilateral acceptance or exit, seller-owned delivery, and the resulting resource relationship.

One market core for many compute domains

Discovery, negotiation, settlement, and arbitration stay recognizable while machine-readable domain vocabulary, contracts, and delivery adapters change.

Discovery · Negotiation · Settlement · Arbitration

Listing vocabulary changes by domain

Query vocabulary changes by domain

Provision terms changes by domain

Result and service state changes by domain

Explore the modular market core →

Operate the market from configuration and APIs

The registry quickstart covers image build, access-gate configuration, runtime deployment, filter vocabulary, and health checks.

make build-registry
docker compose -f compose/registry.yml up -d
curl -sf http://<REGISTRY_HOST>:8080/health
Read the operator quickstart ↗

Configure query and publication gates independently

Serve a filter specification as the market discovery vocabulary

Keep the registry distinct from storefront negotiation and fulfillment

Compose compatible identity, settlement, and domain services around it

Run the infrastructure behind the market