What does Arkova actually do?

Arkova creates a permanent, independently verifiable proof of any credential or document. It anchors a tamper-evident fingerprint of the file to a public network, so anyone can later confirm the issuer, the timing, and the integrity — without Arkova ever holding the file.

How is this different from DocuSign, a notary, or a timestamp service?

DocuSign proves someone signed; a notary vouches with their seal — both depend on that vendor or person still being reachable years later. Arkova proves the exact document existed, unchanged, at a specific time, anchored to a public network no single company controls, so the proof survives even if Arkova, DocuSign, or the notary is long gone. It complements e-signature and notarization rather than replacing them: sign or notarize as usual, then anchor the result for permanent, independent verifiability.

Do you store my documents?

No. Fingerprinting happens in your browser; only the SHA-256 fingerprint and minimal metadata ever leave your device. Even if we were breached, your documents stay private — because we never had them.

Can my document be reconstructed from the fingerprint?

No. A SHA-256 fingerprint is a one-way function: it maps any file to a fixed 64-character value that cannot be reversed back into the original. It confirms two files are identical without revealing anything about the contents. We can prove your document is authentic; we cannot read, reconstruct, or reproduce it — and neither can anyone who intercepts the fingerprint.

What does "tamper-evident" actually mean?

If a single byte of the original document changes, its fingerprint no longer matches the anchored one and verification fails. Integrity is provable by mathematics, not asserted by us.

What happens if Arkova goes away?

The proof outlives us. Because the fingerprint is anchored to a public network, a record stays independently verifiable even if Arkova's servers are offline or the platform that issued it shuts down.

What is the "public network" you anchor to?

An open, permanent, widely-replicated public network that no single company — including Arkova — owns or can quietly rewrite. Because the fingerprint is committed there rather than to our servers, anyone can independently check a record without trusting us, and the proof keeps working even if Arkova does not.

How does someone verify a record?

Every record has a public ID. Anyone can look it up — on the Verify page or with a single API call — to see the issuer, the anchor time, and the tamper-evident status. No account, and no access to the original file, required.

Can a record be revoked or corrected after it's anchored?

The original proof is permanent by design — that's what makes it trustworthy. But a record also carries a live status (Active, Revoked, Superseded, or Expired), and an issuer can revoke a record or publish a corrected version that points back to the original. Verification always shows the current status alongside the immutable anchor, so you get both an unforgeable history and an up-to-date state.

Can I integrate it with my systems?

Yes. A REST API (single-call and batch), HMAC-signed webhooks, and direct anchoring from sources like DocuSign plug into the SIS, LMS, HRIS, and ATS stacks you already run — with a full audit trail of every call.

The verification layer runs in production today; the full product is in early access. Join the waitlist and we will reach out to scope a pilot.

Arkova Monthly — Product & Security Newsletter

Who we are

Arkova is the trust layer for records — for humans and AI agents alike. We create a cryptographic fingerprint of each document and anchor that proof to a public network, so anything issued once can be verified forever, by anyone, without trusting us or anyone else to hold the original.

As more work moves to autonomous agents, the question is no longer “did a person sign this?” — it’s “can a machine prove this is real?”

This month at Arkova

A strong month across product, security, and pipeline. Our full developer surface is now live and in use by real customers — API, SDK, MCP, and webhooks — so both people and AI agents can issue and verify records inside their own workflows. Early reviews have been strong.

On the security side, veteran CISO Matthew Webster of Cyvergence completed a Business Impact Analysis of Arkova — a foundational step in our SOC 2 Type II readiness program. We also achieved CSA STAR Level 1 for cloud security, and filed a provisional patent to protect our IP.

We’re onboarding pilot partners, presenting at Grand Rapids Tech Week, and speaking at the Midwest Bitcoin Conference in September.

Product update

Full developer surface, live. API, SDK, MCP server, and webhooks are all live and in use. AI agents and external systems can issue, anchor, and verify records directly — no manual step in the loop.
DocuSign integration. Testing is complete: signed documents can now be anchored into Arkova directly.
Verified continuing-education credentials. Accountants and lawyers can display their CE credits right on their Arkova credentials — NASBA CPE details for CPAs, ethics-hour breakdowns for CLE. Anyone can confirm them on our public verification page, and audit-ready PDF/JSON exports are rolling out now.
Built on open standards. Arkova credentials now use decentralized identifiers (DID:web) that pass the official W3C conformance tests — so a credential verified with Arkova is recognized across the wider credentialing ecosystem, not just inside our platform.

Platform stats

2.97M+. records anchored to a public network
5,000+. automated tests passing

Security and trust

Matthew Webster of Cyvergence, a veteran CISO, completed our Business Impact Analysis — a foundational step in our SOC 2 Type II readiness program.

We completed the entry tier of the Cloud Security Alliance’s STAR Level 1, which means our security practices are documented publicly in an industry-standard format. Security and verifiable trust are the product, not a checkbox — so this work is core to the roadmap.

Momentum

Credentialing strategy advancing. We joined an exclusive developer program, with conversations progressing across higher education, AI governance, and legal.
Legal vertical progressing. In negotiations with a prominent law firm to use Arkova.
Developer adoption. API, SDK, MCP, and webhooks in active use, with strong early reviews.

On the calendar

Grand Rapids Tech Week. Carson is hosting an event on September 15.
Midwest Bitcoin Conference. Carson is speaking on September 23–24, 2026.

What we shipped, in one email a month

The full developer surface goes live, DocuSign anchoring ships, and Arkova lands its CSA STAR Level 1 listing.