Multi-party commerce protocol
Knowledgement
Created to uncomplicate delivery of digital products that take more than one organization.
Drop your Spline scene here
The problem
Every partnership,
wired by hand.#
Selling a digital product that depends on more than one organization takes months of bilateral integrations, reconciliation spreadsheets, and credentials that can’t be verified without calling the issuer. Every new partner means another point-to-point build.
N×(N−1)/2
Bilateral wires
1 protocol
With Knowledgement
Spline: N×(N−1) wires → single hub
Today
N×(N−1)/2
Bilateral integrations multiply with every new partner.
Knowledgement
one manifest
Adopt the open workflow once. Settlement, discovery, verification.
The product
Three surfaces,
one protocol.#
Every tenant gets the same three surfaces, branded to their own domain and wired together by the protocol underneath.
Spline: workflow marketplace composition
Sell
A branded storefront
List multi-party products on your own domain. Buyers pay once; every contributing organization is settled automatically.
Build
A marketplace of workflows
Compose a sellable product from any open workflow. Bundle your service with other organizations' work — no bilateral contract needed.
Fulfill
An operator's terminal
Move a credential through its lifecycle from a single command line. Issue, advance, verify, hand off — clean audit trail end to end.
How it works
From workflow to payout,
in four moves.#
One worked example: a professional certification delivered by a training provider, an exam center, and a standards body.
A workflow is published
A standards body publishes an open workflow — the sequence of steps a credential moves through and which kind of organization can fulfill each one. Anyone can adopt it without asking permission.
Participants compose a product
A training provider and an exam center each adopt the workflow and declare the steps they handle. The training provider bundles both services into one sellable product on its storefront. No bilateral contract required.
A buyer purchases — once
A learner checks out through the storefront. The tenant’s connected payment processor handles the charge; Knowledgement never custodies funds. A credential is minted in its starting state and delivered to the buyer.
Spline: credential handoff
The credential moves; everyone settles
Each participant advances the credential through the steps it owns and hands it off. When the workflow completes, settlement transfers each partner’s share automatically. The buyer holds a credential anyone can verify locally — no callback to the issuer.
Why it's different
Three choices that
change the shape.#
Not features layered on top — three architectural decisions that account for most of what makes Knowledgement different.
The credential is the trust layer
Every step is signed and the history is tamper-evident. Anyone can verify a credential locally — without contacting the issuer, and without trusting Knowledgement to be online.
Open protocol, your storage
The specification is open and the storage layer is a defined interface. Run a node on your own infrastructure; interoperate with hosted tenants over a published pull protocol.
The workflow is the contract
Adopting a shared workflow is the integration. Two organizations that fulfill different steps of the same workflow already speak the same language — no bespoke wiring needed.
Use cases
Anywhere a credential
crosses a boundary.#
Anywhere a digital product is delivered by more than one organization and the buyer expects a verifiable result.
Professional certifications
A standards body publishes the workflow. Training providers and exam centers each adopt the steps they fulfill. A learner buys a bundle and ends with a credential anyone can verify locally — no callback to the issuer.
Continuing education
A specialty board issues continuing-education credits. Approved providers deliver accredited courses; each one advances the credential a step. The board audits the full chain on demand, and royalty splits settle on commit.
Coaching and apprenticeship
A coaching organization composes a workflow covering intake, milestone reviews, and a final credential. Reviews are run by a third-party assessor with no direct integration — adopting the same workflow is the integration.
Reseller and white-label
A course author publishes their course as a workflow. Partner schools resell on their own branded storefronts at prices they choose. Each sale records both the partner and the author; revenue splits settle automatically.
Built with leading training-delivery organizations
Open by design
Yours to run.
Never locked in.#
The protocol is open. The SDK is open source. Self-host the storefront and ledger, keep custody of your signing keys, point your DID at your own domain — nothing about leaving is designed to be hard.
Self-hosted nodes interoperate with hosted tenants over a published pull protocol. Knowledgement competes on the quality of the hosted experience, not on lock-in.
Inspect the protocol$ kgmt send --token cred.json --to examhub.kgmt.io
→ Discovering examhub.kgmt.io … inbox found at /.well-known/ddsm/inbox
→ Sending credential f47ac10b (state: training-complete)
✓ AcceptedThe CLI · Open source · Scriptable
Pricing
Three ways to run.
Start free, scale on subscription.#
Run hosted storefronts on a subscription, or self-host your own node at no cost to Knowledgement.
Hosted
Free to start
A branded storefront at your subdomain, provisioned in minutes. Subscription pricing for hosted infrastructure; no per-step fees or marketplace commission at entry.
Most popular
Hosted on your domain
Subscription
Same hosted infrastructure, served from your own custom domain. Branding, identity, and inbox all resolve under your URL.
Self-hosted
Free to run
Run your own node and storefront. No subscription to Knowledgement, full data sovereignty. Self-hosted nodes interoperate with hosted tenants through the published pull protocol.
Payments: Stripe today, with more processors on the roadmap.
Build commerce that
crosses companies.#
Open a tenant or run your own node. Either way, the network is one workflow away.