Public Documentation
Build verifiable AI evidence with Attesto.
This hub is three things at once: a user manual for evidence operators, a developer portal for SDK/API/connectors, and a trust center for parties that need to verify Attesto output without trusting the Attesto backend.
Internal control-plane procedures, infrastructure runbooks, private diagnostics, and credential operations are intentionally not published on this domain.
Find the right guide
Search by task, surface, or integration. Results stay local to this static site.
Getting Started
What is Attesto?
Evidence streams, verifier-first compliance, trust boundaries, and what Attesto does not claim.
Why Attesto exists
Learn why AI and compliance teams need evidence streams that are independently verifiable.
Attesto in 10 minutes
Move from tenant login to a server-side event and a verified receipt.
Get started
Register a system, reveal the system key once, log an event, and verify the first receipt.
Glossary
Evidence stream, receipt, window, checkpoint, witness, quorum, fork evidence, anchor, and bundle.
Attesto 1.0: Evidence Primitives
Events, receipts, anchors
Use the stable control plane for event capture, receipts, verification, anchoring, exports, and auditors.
Events
What to log, how idempotency works, and how event payloads should be shaped.
Receipts
Signed event acknowledgements and the first verification layer.
Verification
How v1 proofs are checked and where v1 verification differs from Proofstream.
Anchoring
How batch commitments are externally anchored and exposed in evidence exports.
Attesto 2.0: Proofstream
Proofstream lifecycle
Understand event -> receipt -> window -> checkpoint -> witness -> anchor -> bundle -> offline verify.
Windows
Closed event ranges, inclusion proofs, and window commitments.
Checkpoints
Stream-head commitments, consistency, and checkpoint history.
Consistency
Why inclusion alone is not enough and how stale or rewritten history is rejected.
Bundles
Portable verifier packs with receipts, windows, checkpoints, witness statements, and anchors.
Witness Plane
Witness Plane
Independent checkpoint witnesses, signed statements, policy, and fork detection.
Witnesses
Attesto-operated, customer-operated, assurance, and partner witness roles.
Quorum
How 1-of-1 and 2-of-3 policies change what a verifier can rely on.
Fork evidence
How conflicting histories become machine-readable evidence instead of hidden disagreement.
Verifier System
Verifier-first evidence
How external parties verify receipts, bundles, witnesses, anchors, and fork evidence independently.
Offline verifier
Run local checks without backend access and inspect deterministic verification reports.
Verifier matrix
What changes are detected: payload, sequence, deletion, insertion, stale checkpoint, signature, anchor.
Trust boundaries
What Attesto proves, what remains the customer responsibility, and where external review applies.
Failure modes
What to do when verification fails, quorum is missing, fork evidence appears, or a bundle is incomplete.
Local Vault, APIs, SDKs, and Connectors
Python and TypeScript SDKs
Use production defaults, idempotency, retries, and server-side key handling.
Public API
Authentication, idempotency, v1 event ingest, v2 Proofstream endpoints, and verifier responses.
Relay, spool, witness
Outbound-only relay, encrypted spooling, online/offline behavior, and customer witness mode.
Production connectors
Signed webhook, repository webhook, and S3/R2 object commitment connector contracts.
Tenant webhooks
Signed lifecycle delivery, retry behavior, and dedupe guidance for your endpoint.
Tenant operator UI
Use dashboard.attesto.eu for systems, streams, exports, billing, and evidence review.
Proof of Evolution
Nova, IVC, state roots
Understand the async lifecycle proof lane, evolution chain, and review-gated claim boundaries.
Nova and IVC
How lifecycle proofing is designed on top of committed checkpoint metadata.
State roots
Previous root, checkpoint root, policy digest, incident state, and next root.
Claim boundaries
What is proven today, what is production evidence, and what stays review-gated.
Regulatory Evidence
AI Act, NIS2, CRA, SOC 2
Map Attesto evidence packs to compliance-support areas without claiming legal certification.
Control mapping method
How evidence packs support control work while legal compliance remains the customer responsibility.
EU AI Act support
Logging, traceability, technical documentation, monitoring, and incident evidence.
NIS2 and CRA support
Cybersecurity evidence, supply-chain assurance, vulnerability handling, and secure update support.
ISO 27001, SOC 2, eIDAS
Logging, access control, processing integrity, timestamps, ledger integrity, and non-repudiation support.
Operators and Production
Readiness and assurance
Lifecycle readiness, assurance reports, production evidence health, and what green means.
Canaries
Lifecycle, fork defense, quorum, connector, Local Vault, multi-tenant witness, and Nova evidence canaries.
Readiness
How to read production readiness, assurance, and release evidence reports.
Public operator runbooks
Tenant-facing response guidance without exposing internal control-plane operations.
Changelog
Track user-facing documentation, SDK, API, connector, verifier, and Proofstream changes.
Languages
Public documentation is maintained in English, Dutch, German, French, Spanish, Polish, and Italian. English is the canonical developer contract; translated guides keep the same API names and production endpoints so code stays unambiguous.