Open protocol. Commercial support when you need it.
Use PEAC free forever. Bring in Originary when another party already asked for proof your logs cannot provide.
Most teams start with one workflow.
A pilot usually means one API, MCP server, gateway, payment flow, or agent handoff; one signed-record profile; one verifier report or bundle; one integration review; and one rollout recommendation.
You should contact us if another party already asked for proof your logs cannot provide.
Apache-2.0
What stays free
PEAC Protocol, self-hosted verification, open-source packages, and conformant implementations remain free and portable.
What Originary adds
Originary Verify, deployment support, enterprise record exports, rollout help, and procurement-friendly trust surfaces for teams that need production readiness.
Originary Verify & Enterprise Support
Managed verification, signing operations, and procurement-ready record exports
For organizations that need managed verification, signing operations, or procurement-ready record exports for audits and reviews. If you are evaluating Originary for a team deployment or need record artifacts for a procurement review, this is the right path.
Best fit: API platforms handling agent traffic, MCP server operators, security and compliance teams, and organizations with procurement requirements.
Architecture review, environment setup, and production rollout guidance
AWS KMS, GCP Cloud KMS, Azure Key Vault, or HashiCorp Vault
Pre-packaged verification artifacts for audits and procurement reviews
Direct channel to the protocol engineering team for troubleshooting and feature requests
Defined response windows and escalation paths for production issues
Best for
Deployment model
Not the right fit yet: If you are still evaluating, start with the open-source packages. They are free and unlimited.
Talk to the teamThree ways to deploy
| OSS only | Supported self-host | Managed verification | |
|---|---|---|---|
| Price | $0 forever | Custom | Custom |
| License | Apache-2.0 | Apache-2.0 + support terms | Apache-2.0 + support terms |
| Signing keys | Self-managed | Self-managed or KMS-backed | KMS-backed attested keys |
| Deployment | Self-hosted | Self-hosted with guidance | Originary operates |
| Verification | Offline, no dependency | Offline, no dependency | Offline, no dependency |
| Support | GitHub issues | Dedicated engineering + SLA | Dedicated engineering + SLA |
| Evidence exports | Self-assembled | Guided | Pre-packaged bundles |
| Architecture review | Community docs | Guided integration | Full review included |
Common questions
Can I self-host everything?+
Yes. PEAC Protocol and all core packages are Apache-2.0 licensed and free to self-host. Verification does not require Originary to be online. No data is sent to any Originary service.
Is the protocol truly open?+
Yes. The protocol specification, all reference implementations, and core tooling are published on GitHub under Apache-2.0. You can build your own conformant implementation without involving Originary.
What payment rails are supported?+
PEAC is rail-neutral. It produces verifiable records of interactions, not payment mandates. HTTP 402 adapters are available for teams that need challenge/response payment flows.
Who should contact you about Originary Verify or commercial support?+
Enterprise AI platform teams, API operators, MCP hosts, and security or procurement review teams that need managed verification, attested signing infrastructure, or procurement-ready evidence.
Open source, no exceptions
The protocol specification, reference implementations, and all core tooling are Apache-2.0 licensed. Originary is the commercial steward — not a gatekeeper.