The protocol is free.
Always.
PEAC Protocol is Apache-2.0 licensed. Self-host on your own infrastructure with no limits, no fees, and no sign-up required. Verification does not require Originary to be online.
Get started on GitHub28 packages on npm · 6443 tests · Apache-2.0
Enterprise support
Terms scoped to your deployment
For organizations that need production deployment support, managed key infrastructure, or compliance evidence for audits and procurement. If you are evaluating Originary for a team deployment or need evidence 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 teamOpen source vs enterprise
| Open source | Enterprise | |
|---|---|---|
| Price | $0 forever | Custom |
| License | Apache-2.0 | Apache-2.0 + support terms |
| Signing keys | Self-managed | KMS-backed attested keys |
| Deployment | Self-hosted | Self-hosted, managed, or hybrid |
| Verification | Offline, no dependency | Offline, no dependency |
| Support | GitHub issues | Dedicated engineering access + SLA |
| Compliance evidence | Self-assembled | Pre-packaged bundles |
| Architecture review | Community docs | Guided integration |
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 commercial support?+
API providers, agent platforms, and security or compliance teams that need managed deployments, attested signing infrastructure, or dedicated integration support.
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.