Sovereign protocol • Managed vault service

Truth storage for operators
shipping in public

Provara turns decisions, simulations, and market calls into signed evidence. Every consequential move gets a receipt you can verify without trusting us.

bash — provara-demo
$ pip install provara-protocol Collecting provara-protocol... Successfully installed provara-protocol-1.4.0   $ psmc --vault ~/.provara/my-agent append \ --type decision \ --data '{"model":"claude-3","output":"approved","confidence":0.94}' \ --tags production compliance Appended event #143 — sha256:a3f8c2...e91b   $ psmc --vault ~/.provara/my-agent verify Chain integrity: CLEAN (143 events, 0 gaps)

No trust required. Just math.

Three operations. Cryptographically linked. Independently verifiable.

🔐

Sign

Every event is signed with Ed25519. The private key never leaves your system. The signature is stored alongside the event payload in the vault.

⛓️

Chain

Each event includes a SHA-256 hash of the previous event. Modify a single event and the chain breaks — every subsequent hash becomes invalid.

Verify

Anyone with the public key can independently verify the entire chain. No central authority. No Provara servers required for verification.

Built for what regulators and auditors actually ask for.

Regulatory

EU AI Act compliance

Article 12 requires automatic logging for high-risk AI systems — records that are accurate, traceable, and durable. Provara produces exactly what the regulation requires. Not a workaround. The actual thing.

Audit

SOC 2 evidence

Auditors want logs they can verify. Not screenshots. Not JSON you could have edited after the fact. Cryptographic receipts with provable integrity — signed at write time, verifiable at any time.

Engineering

AI agent accountability

Multi-agent workflows, LLM pipelines, autonomous decision systems. Every decision logged, signed, and replayable. Know exactly what ran, when, and what it decided.

Proof beats hindsight.

The first live record is the Wolfpack’s LTC long: signal, simulation, timestamp, and post-move outcome anchored under one verifiable chain.

LTC LONG • VERIFIED HUNT

Wolfpack LTC long, signed before the move.

Kestrel generated the entry signal, Fenrir rehearsed the path, and Provara sealed the chain before the market validated the thesis. This is the standard: publish evidence first, commentary second.

Signal
LTC Long
R-Factor
+2.4R
Vault status
VALID
Evidence
Signal + sim + receipt
Read the record
  • Signal issued before the market move, not reconstructed after it.
  • Simulation attached so readers can inspect the pre-trade thesis, not just the outcome.
  • Vault verification badge exposes current status for the evidence chain.
  • Exact timestamps, receipts, and narrative can be published without handing over private keys.

Start sovereign. Scale when the stakes do.

The protocol stays open. Managed vaults charge for uptime, persistence, and truth storage in production.

Free
$0 / month

Everything you need to get started and evaluate the protocol.

  • 1 vault
  • 100 events / month
  • CLI access
  • Open source protocol
  • Local key management
Get started
Team
$99 / month

For teams shipping compliance-critical AI with shared access and SLA requirements.

  • Unlimited vaults
  • Team access & permissions
  • API key management
  • 99.9% uptime SLA
  • Priority support
Get started

The protocol is open.
The hosted vault is a service.

The full Provara protocol — key management, event signing, chain verification, NDJSON vault format — is Apache 2.0 licensed. Run it yourself, fork it, audit it. The managed hosted vault is a paid product layered on top.

Self-hosting is a first-class use case. Provara the protocol will always be free.

github.com/provara-protocol/provara

Install

$ pip install provara-protocol

Verify any vault

$ psmc --vault ~/.provara/my-agent verify

Quick start

# Initialize a new vault $ psmc --vault ~/.provara/my-agent init Vault initialized. Public key written to ~/.provara/my-agent.pub # Log a decision $ psmc --vault ~/.provara/my-agent append \ --type decision \ --data '{"result":"approved"}' Appended event #1 — sha256:8f2a1c...d43e