Certyo/v1
Start a pilotLog in
v1.0 · live on Polygon mainnet

Records that
refuseto lie.

Cryptographic integrity evidence for regulated operations. Anchored to a public blockchain — verifiable by anyone, outliving any vendor.

Request a demo →or read the docs
~500ms
p95 verify
200+ rps
sustained
0
PHI/PII stored
~ certyo · zsh live
$ curl -X POST https://api.certyo.io/v1/verify/record \
-H "Authorization: Bearer $CERTYO_KEY" \
-H "X-Tenant: acme" \
-H "Content-Type: application/json" \
-d '{"record_id":"rec_8f3a91e7"}'
← 200 OK · 483ms
{
"verified": true,
"record_id": "rec_8f3a91e7",
"merkle_root": "0xa9f2…e8b1",
"tx_hash": "0x4e6c…9d77",
"block": 54812307,
"chain": "polygon-mainnet",
"latency_ms": 483
}
idempotent · p95 ~500mscopy →
proof_rec_8f3a91e7.pdf
merkle path · tx · block · IPFS CID
auditor-ready
Our objective

Internal logs prove recoverability.
They do not prove immutability.

Certyo adds a layer of externally anchored cryptographic proof — independent of the system that produced the data. The records never leave your perimeter; the proof is public.

How it works.

Four steps · ingestion → batch → anchor → verify → evidence.
02 · Batch anchor

1,000 records, one Polygon transaction.

Hashes accumulate into a Merkle tree. The root is pinned to IPFS and anchored on-chain in a single tx. Cost-amortized; integrity-uncompromised.

root 0xa9f2…e8b1
01 · Ingest

SHA-256 fingerprint

POST /api/v1/records — payload canonicalized and hashed before entering the pipeline.

0xb47e3c8f…d29a01ab
03 · Verify
~500ms

p95 verification latency for any record on the platform — full proof package returned.

04 · Evidence

Auditor-ready proof packages

PDF + JSON. Tx hash, block number, Merkle path, IPFS CID, anchor timestamp.

curl · /api/v1/verify/record
idempotent
$ curl -X POST https://api.certyo.io/v1/verify/record \
-H "X-Tenant: acme" \
-d '{"record_id":"rec_8f3a91e7"}'
← 200 OK
{ "verified": true,
"latency_ms": 483, "block": 54812307 }
1,000
records / tx
Per Polygon batch anchor
8
roles
RBAC, fail-closed isolation
0
PHI / PII stored at Certyo
∞
Proofs survive Certyo
Compare

The cloud-ledger graveyard.

AWS QLDB shipped in 2019 and shut down in 2025. Azure ACL works only in Azure. Vendor-neutral proof is the only thing that survives a discontinuation notice.

Certyo
Vendor-neutral · public proof
Status
Active
Trust root
Public blockchain
Verifiability
Anyone can verify
Lock-in
No lock-in
Data custody
Hash-only
Survivability
On-chain forever
AWS QLDB
Discontinued July 2025
Status
Discontinued
×
Trust root
Centralized (AWS)
×
Verifiability
Requires AWS access
×
Lock-in
Full AWS lock-in
×
Data custody
Full doc storage
×
Survivability
Service shut down
×
Azure ACL
Active — Azure-only
Status
Active
Trust root
TEE enclaves
Verifiability
Requires Azure access
×
Lock-in
Full Azure lock-in
×
Data custody
Full entry storage
×
Survivability
Single-vendor risk
×
↳ See full comparison: vs AWS QLDB · vs Azure ACL
View full comparison →
Backoffice

Operations portal,
not a CLI dump.

Tenant-scoped record exploration, batch progress, verification history, and audit log access — for non-cryptographers who still own the audit trail.

  • Search by tenant, collection, record ID, time window
  • One-click verification + exportable proof package
  • Lifecycle view per record — ingest → batch → anchor → verify
  • Immutable audit log for every privileged operation
certyo.io/backoffice/records
tenant · acme
Records
Batches
Verifications
API keys
Audit log
Users & roles
tenant:acme · status:verified · since:24h
14,287 results
RecordStatusMerkle rootBlockLatency
rec_8f3a91e7verified0xa9f2…e8b154812307483ms
rec_22aa1f0cverified0xa9f2…e8b154812307512ms
rec_91be4d12verified0x4e6c…9d7754812281474ms
rec_e774920bverified0x4e6c…9d7754812281498ms
rec_5512aa90verified0x2218…11ef54812254465ms
rec_a1f7c022pending———

Built for the people
who get the call.

Fintech
Daniela · SecOps
Settlement records with independent integrity proof.
Healthcare
Omar · Internal Audit
HIPAA-aligned records — admin, billing, EHR non-device.
Audit
Priya · Tenant Admin
Exportable cryptographic evidence for regulators.
SecOps
Marco · Support
Verify a record in a single API call during disputes.
HIPAA aligned·SOC 2 aligned·Merkle proof·Tenant isolation·8 RBAC roles·Immutable audit·Polygon mainnet·IPFS pinning·OIDC auth·X-RateLimit headers·HIPAA aligned·SOC 2 aligned·Merkle proof·Tenant isolation·8 RBAC roles·Immutable audit·Polygon mainnet·IPFS pinning·OIDC auth·X-RateLimit headers·

Pilot in 60
days. Records
verified in minutes.

Self-hosted on your Kubernetes, or managed on dedicated single-tenant infra. We don't ask regulated buyers to put their evidence behind someone else's tenant.

↳ 60-day pilot · up to 10,000 records · MSA required