Tamper-evident records
Inspect public records and their Network Receipts. Track versions and changes in an audit trail, link records to the versions that replaced them, and organize them with tags and folders. Files you upload directly never leave your device.
Sample public record
Verification snapshot
Captured Oct 1, 2026 · status may change
Anchored document
PDF · 5,228 bytes
This is a dated snapshot of public record details. Use the verifier to request a status update; cached results may lag recent changes.
Verify this recordConnect DocuSign and give selected completed documents a fingerprint, a public ID, and a Network Receipt. Signing shows who agreed. A fingerprint comparison shows whether a copy still matches what was signed.
How the connector worksConnect a Drive source and choose the documents to record. Each selected file is fingerprinted in server memory, discarded, and given a public record with an Observed Time. Nothing is copied out of your Drive.
How the connector worksAs reported in Arkova Monthly, June 2026. The live count has moved on since.
Check any one yourselfAudit trail and version history
When a document is updated, the earlier record is retired, not erased. The new version links back to the one it replaced, each keeps its own proof, and every action in between lands in an audit trail you can export.
Who did what, when, to which version. Export the report for your GRC platform or hand it straight to the auditor.
Link, tag, organize
A proof on its own is a fact. A proof with its versions, its attestations, its folder and its tags is evidence you can actually use.
Use case · Vendor contract, draft to audit
A legal operations team keeps vendor contracts in Google Drive and signs through DocuSign. Here is what Arkova adds, step by step, without changing where the files live.
The connected Drive folder picks up the draft MSA. It is fingerprinted, filed under Vendors / Acme and secured as version 1. Legal ops tags it acme, msa, fy26.
anchor.created · anchor.securedA new fingerprint is detected for the same file. Nothing is anchored yet: the change waits in the review queue until an admin approves it. Then version 2 is secured and version 1 is marked superseded, with links both ways.
version.detected · anchor.supersededThe completed DocuSign envelope is anchored as version 3 and linked to the draft chain. Counsel adds a signed attestation. The record is now the current version and the earlier drafts are retired but still provable.
signature.verified · attestation.createdOpen the Acme folder, export the audit report as PDF or CSV, and send the public IDs. The auditor checks every version on the Verify page with no account and no copy of the contract.
report.created · credential.verifiedWhat the auditor sees: three linked records, each with its own fingerprint, Network Receipt and Observed Time, plus the signed attestation. What they never see: the contract, your tags, your folders, or anything else in your account.
More use casesSee yourself using it
Pick the one that looks like your week. Each is three steps in the product as it ships today.
Everything a record can do
A timestamp service gives you a date. Arkova gives the record a life: secured, organized, attested, proven, audited and automated.
How it works
Three steps from a file to a checkable public record. Direct uploads stay on your device. No account is needed to check a record.
A SHA-256 fingerprint of the document is computed in your browser for direct uploads, so the file stays on your device. Documents selected from a connected source are fingerprinted in server memory and discarded.
The fingerprint is linked to an anchor on a public, permanent ledger that no single company controls, Arkova included. The public record shows a Network Receipt, a Network Checkpoint, and an Observed Time.
Anyone with the public ID can look the record up on this page, through the API, or with their own tooling. With a copy of the file, compare fingerprints to check whether it matches. No account required.
Why Arkova
Arkova fits the document workflows you already run and gives each record a reference that holds up later, in front of an auditor, a court, or a counterparty.
Case studies and partners
HakiChain has announced Arkova for document-integrity checks in its HakiDocs workflow, so the integrity of a filing can be checked later with neither HakiChain nor Arkova holding the original file.
Visit HakiChainVerify a real record
Every record has a public ID. Look one up here or with a single API call to see the reported issuer, status, Observed Time, and Network Receipt. No account, and no copy of the original file, required. The lookup reports record details; it does not compare a file you hold.
Pre-filled with a real record — hit Verify to check it live, or see it on search.arkova.ai. Paste any Arkova public ID — no account needed.
Developers
Look up a public ID over REST, receive record events through signed webhooks, or let an agent call Arkova over MCP. Scales from one filing to millions of records.
Run the same lookup the verifier makes, through the marketing-site proxy, and see the selected fields that come back.
Press “Run it” to request this public ID through the marketing-site proxy.These are selected fields from the response, not the complete API payload. A successful request is not a verdict about the document.
This page uses a same-origin proxy to request a public record. Responses may be cached, and requests may be logged.
Webhooks can notify your endpoint about supported record events. The illustration below shows the handoff; it does not send an event or check a signature.
Webhook flow illustration
Example record details, not an exact webhook payload or API schema.
In an integration, a webhook can notify your service about a record event. This example only illustrates the handoff.
Explore the handoff without sending a request.
Research
Agent identity and document integrity are separate checks. A public record and file fingerprint can help a reviewer trace a version without certifying its contents or issuer.
Read more →
Product, security, and partnership updates in Arkova Monthly. One email a month. The July 2026 issue is a dated archive of what the team was building then.
Create your first records in minutes. Looking up a public record stays free and needs no account.
Investor or partner? View the pitch deck or write to founders@arkova.ai.
Contact
Talk to the team about adding Arkova to your document workflow, your compliance program, or your product.
Founder & CEO
Founder & COO
Founder & Advisor
What skeptics ask
Arkova gives a document a fingerprint, public record ID, and network anchor reference. Anyone can look up the record. Someone with a copy of the file can compare fingerprints to check whether it matches. That comparison does not establish whether the document’s contents are true or who was authorized to issue it.
Electronic signatures, notarization, and timestamp services each address different parts of a document workflow. Arkova adds a public record and fingerprint reference for later file comparison. It can complement those services; a fingerprint match alone does not establish a signature’s validity, a signer’s identity, or a legal conclusion.
We do not retain original documents. Files you upload directly are fingerprinted in your browser and stay on your device. If you select a document from a connected source such as DocuSign or Google Drive, Arkova fingerprints it in server memory and discards the file immediately. We retain the fingerprint and limited metadata. See our Privacy Policy for the full processing details.
SHA-256 is designed to be one-way; the fingerprint is not a copy of the file. Someone with a candidate document can compute its fingerprint and compare it with a recorded value when available. A match alone does not establish whether the document’s contents are true or who issued it.
Compare a copy of the file with its recorded fingerprint when that value is available. A different fingerprint indicates different content. A public record lookup alone does not compare a file or establish that its contents are true.
A public-network anchor is recorded outside Arkova. Checking a particular file without Arkova also requires the file and enough record details to connect its fingerprint to that anchor. The sample record does not offer a self-contained offline proof bundle, and current status is provided by the verification service.
Arkova connects a public record to an anchor on a network outside Arkova’s infrastructure. The public record shows a network checkpoint and receipt. Those details help locate the anchor; they do not by themselves confirm a document’s contents or issuer.
Enter its public ID to review the reported status, issuer label, network observed time, checkpoint, and receipt. With a copy of the file, compare its fingerprint against the recorded one to check integrity. A lookup alone does not prove the contents are true or the issuer was authorized.
The network anchor remains, while a record’s reported status can change. A verification lookup returns the status available from the service; cached results may lag recent changes. Ask the issuer about a revocation or replacement record.
Arkova offers a REST API and webhook events for supported workflows. Use the public ID to look up record details, or contact us to discuss connectors and how an integration would fit your systems.
Yes. Arkova is live. Get started in the app, or talk with us about an integration or pilot.
Last updated: October 2026