VaaS receipts

Give every inference verifiable proof

Audit traces turn inference from logging into verifiable records. Signed receipts, hashes, chain-linked records, and support-reviewed evidence packs combine into an auditable inference system.

TLS 1.3Hash-only audit inputsEd25519 signaturesClean compute evidenceSOC 2 path
Request
SHA-256 Hash
Ed25519
Chain Link
Store
Verify
Open docsBrowser verify

Verifiable output path

Every supported audit record can be hashed, signed, and externally verified. The goal is operational trust, not marketing trust.

Hash only

Input and output content are reduced to hashes for audit records. Raw prompts do not need to live in the verifier layer.

Ed25519 signatures

Each record is signed with an Ed25519 keypair so external verifiers can reproduce the trust check in their own environment.

Compute Node-linked audit metadata

Model id, Compute Node ID, timestamp, and record hashes are bound together in the signed payload.

Optional timestamp proofs

When enabled, audit references can link outward for independent timestamp verification without requiring every record to be stored on-chain.

Security posture

  • Transport · TLS 1.3 in transit, strict security headers, and httpOnly secure session cookies.
  • Storage · Secrets stay server-side. Audit records store hashes and signatures, not plaintext prompts.
  • Access control · Dual-layer auth in middleware and server routes, plus rate limits and per-key policy enforcement.
  • Operational controls · Logging, key rotation support, CORS restrictions in production, and a formal SOC 2 availability path.

Clean compute evidence

Each VaaS record can include signed energy, carbon, power-source, and verification-status fields so teams can review per-request compute impact without treating estimates as a certificate.

Low-carbon grid reference

~60 gCO2e/kWh

Baseline cloud reference

~400 gCO2e/kWh

Audit record fields

Energy, carbon, and power source

How audit traces compare

FeatureBatchIn VaaSStandard LoggingBlockchain Verification
Overhead< 10ms~0ms500ms-30s
Tamper evidenceHash chain + Ed25519NoneImmutable ledger
Client-side verifyYesNoYes, expensive
Cost per record$0$0$0.001-$0.01
PrivacyHash-only, no raw content in auditFull content often loggedHash commitments on-chain

Need a deeper review?

We can walk through the audit model, security headers, cookie strategy, and deployment posture with your team.

Open VaaS guideOpen verification page