Skip to content

Site search

Type to search Pages

Pricing

Priced per reliance, not per seat.

Reliance is metered per event and priced below a fresh from-source verification. Issuers pay to publish and manage attestations. Enterprise scope, thresholds and limits are agreed per engagement.

Start a conversationSee what it does

How the exchange is priced.

Price follows the work

Reliance is a usage-metered utility. The primary meter is the reliance event: each time a relying agent queries the exchange, verifies a cryptographic proof and acts on it within its configured limits. That event is deliberately priced below a fresh from-source verification, because the issuer has already done the checking and signed for it — the relying agent pays for verified reliance, not for repeating work someone else already stands behind.

Metering the event rather than the seat ties price to autonomous transaction volume. A fleet that relies on many claims pays in proportion to how much reliance it consumes, and a governor can see exactly what was relied upon for each charge.

Three streams, one exchange

Revenue is drawn from three streams that reflect the work each side does. Relying parties pay per reliance event. Issuers pay an issuance fee to publish a signed, scoped, revocable attestation, plus a management subscription covering lifecycle, revocation propagation and evidence retention. Enterprise agreements are quote-based, with the admissible issuers, value thresholds and expiry limits set by the relying-party governor.

None of these depend on speculative claims about full agent autonomy. Each is tied to something observable: an attestation published, a proof verified, a lifecycle managed.

Ways to engage

Pick the side of the exchange you are on.

Pricing is scoped per engagement. Every conversation starts by modelling the volume you expect against what re-verification costs you today.

Relying agents

Meteredper reliance event

For teams whose agents must act on a counterparty's claim.

  • Query the exchange and verify a signed proof
  • Priced below a fresh from-source verification
  • Freshness and revocation checked at decision time
  • Proceed or escalate under policy-as-code
  • Every reliance event logged as evidence
Talk to us
Both sides welcome

Issuers

Talk to usissuance + management

For organisations that hold facts others need to rely on.

  • Publish signed, scoped, revocable attestations
  • Issuance fee per published attestation
  • Attach explicit liability terms and expiry
  • Revocation propagated to relying parties
  • Management subscription for lifecycle and evidence
Talk to us

Enterprise

Customannual agreement

For regulated relying parties and issuers with governance obligations.

  • Quote-based agreement
  • Configurable scope, value thresholds and expiry
  • Governance console for human approvers
  • Audit-ready evidence retention
  • Named point of contact
Talk to us

There is no public price list yet. Pricing is scoped per engagement while we work with early issuers and relying parties.

Questions

What you are paying for.

What determines the price of a reliance event?

The primary meter is the reliance event: each time a relying agent verifies an attestation and acts on it. It is deliberately priced below a fresh from-source verification, because the checking work has already been done and signed for. Volume scales with inter-agent transaction count, not seat count.

How do we get a quote?

Tell us the facts your agents rely on and the volume you expect, and we will model it against what re-verification currently costs you today. A quote sets the meter for reliance events and, for issuers, the issuance and management terms.

How does pricing work for issuers?

Issuers pay an issuance fee to publish a signed, scoped, revocable attestation, and a management subscription that covers lifecycle, revocation propagation, policy-as-code limits and evidence retention. You decide what you will stand behind before anything is published.

Does paying for reliance just shift liability around?

No. Each attestation names the party standing behind it and states its scope and expiry, so liability sits with the issuer who accepted it — not with the exchange. Signura is neutral: it records what was relied upon and when, and takes neither side's part.

Which budget usually funds this?

Procurement is typically led by security, IAM and compliance functions that value an inspectable evidence trail. Relying parties fund it against the cost of re-verifying counterparty claims; issuers fund it against the staff time spent answering the same requests by hand.

How do enterprise agreements work?

Enterprise agreements are quote-based. A relying-party governor configures which issuers and attestation types are admissible, with value thresholds and expiry, and receives escalation on ambiguous or high-risk reliance. Scope and terms are agreed before anything goes live.

Why meter per reliance rather than per seat?

Because the value lands each time an agent relies on a claim, not each time a person logs in. Metering the reliance event ties price to the work done — verifying a proof and retaining it as evidence — and scales with autonomous transaction volume.

Can we start small?

Yes. A small set of issuers attesting to common facts — licences, policy status, certifications, granted permissions — creates value for relying parties without ecosystem-wide adoption. We begin with the facts your agents already depend on most.

Model reliance pricing against your own agents' claims.

Tell us the facts your agents depend on and the volume you expect, and we will scope it with you.

Read the security postureStart a conversation