OASP
Spec ↗ Schemas ↗ GitHub ↗
Home / Implementations
// implementations

An ecosystem, not one vendor.

Loom will be the reference server, but OASP is a standard precisely so it isn’t the only one. Anything that passes the conformance kit belongs here — Clients, Servers, and Adapters alike.

// reference implementation
Loom reference server · in progress

Loom is the gateway OASP was written for. It was partway built when the durable-conversation layer proved to be protocol rather than product — so the standard shipped first, and Loom now builds against it.

Its job: host Conversations and their Session lineage, implement migrate and drain, and emit a normative audit trail. Apache-2.0.

Server (L2) · reference implementation
conformance runnot yet published
licenseApache-2.0
roleserver
statusin development

“Reference implementation” describes Loom’s role, not a kit-verified conformance result — see Conformance for what the kit checks today.

// the registry

Who implements OASP

1 listed · open for more
Loom server

Reference server, in progress. The gateway OASP was written for.

reference · targets L2
Your Client client

An app or SDK that speaks OASP to any conformant server.

run the kit to list →
Your Server server

A host for Conversations, Sessions, and their audit trail.

run the kit to list →
Your Adapter adapter

A bridge that brings an existing runtime into OASP.

run the kit to list →
// implement OASP

Three steps to a listing

01
Build

Pick the level that fits — Client, Server, or Adapter — and implement it against the spec and schemas.

02
Run the kit

Point the conformance kit at your implementation and fix until every MUST for your level is green.

03
Get listed

Submit your passing result. Your implementation appears in the registry above, with its level and kit version.

Everything you need to start is in the spec and the conformance kit. Read the spec ↗ Conformance →