Pricing
Pricing scoped to the integration cost it removes.
Three ways to adopt Subchain: a platform subscription, a per-agreement fee when a proposal binds, and licensing of the runtime and template library. Each is scoped with you, not from a list.
How adoption is priced.
Pricing is scoped per engagement and anchored to the per-counterparty integration spend the protocol displaces, not to a fixed list.
Platform subscription
Recurring access to the runtime, gating and audit log.
- Deterministic negotiation runtime
- Configurable authority limits and gates
- Inline policy-as-code checks
- Immutable audit record
- Priced against avoided integration spend
Per-agreement fee
Applied when a proposal reaches binding acceptance.
- Charged only on binding acceptance
- Aligned to committed value, not messages
- Full negotiation trail per agreement
- Named approver logged on each commitment
Runtime licensing
Embed the runtime and template library in your platform.
- License the protocol runtime
- Versioned term-template library
- For agent-platform and infrastructure providers
- A distribution channel and a revenue line
What determines the price.
How we price
How we price, and what we do not promise.
Priced against the cost it removes
Every new external counterparty an agent estate transacts with otherwise means another bespoke integration, and that cost recurs for each relationship. Subchain removes the repeated build by letting agents transact against one standard, so we anchor price to the integration spend displaced rather than a fixed list.
Three streams reflect where value lands: a platform subscription for access to the runtime, gating and audit log; a per-agreement fee when a proposal reaches binding acceptance; and licensing of the runtime and term-template library to platforms that embed it. Value is present from the first bilateral relationship and grows as more of a network standardises on the protocol; it does not require universal adoption to work.
What every engagement includes
Whichever streams apply, the governing controls are not an add-on you price separately. The approval gate, the authority limits your governors set, and the immutable record of who authorised what are part of the runtime you subscribe to or license.
We would rather scope terms against your real counterparty load than publish figures we cannot yet stand behind. Design-partner pilots let us agree pricing that reflects the integration and contracting cost you actually carry, and refine the term templates against the transactions you actually run.
Scope pricing against your counterparty load.
Tell us how many external counterparties your agents transact with, and we will scope subscription, per-agreement and licensing terms with you.