Turn documents into
checkable records.
Arkova links a document fingerprint to a public-network anchor and gives it a public ID anyone can look up. Someone with the file can compare fingerprints to check whether it matches.
Sample public record
Verification snapshot
Captured Oct 1, 2026 · status may change
Anchored document
PDF · 5,228 bytes
- Public ID
- ARK-DOC-HKUK9N
- Status at snapshot
- ACTIVE
- Issuer
- Arkova
- Network checkpoint
- 946,305
- Network observed time
- Network receipt
- aa3c65ca38adc01789399c11c53afdbb632832e2041cc49e4d7482e2757e692f
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 recordThe mechanism
Fingerprint. Anchor. Verify.
Three steps from a document to a checkable public record. Direct uploads stay on your device; selected connected-source files are fingerprinted in server memory.
Fingerprint
Direct uploads are fingerprinted in your browser, so the file stays on your device. Selected documents from connected sources are fingerprinted in server memory.
Anchor
Arkova links the fingerprint to a public-network anchor. The public record shows a network checkpoint, receipt, and observed time.
Check
Look up a public ID to review record details. With a copy of the file, compare fingerprints to check whether the document matches.
Privacy is the architecture, not a feature. Files you upload directly are fingerprinted in your browser with the Web Crypto API and stay on your device. Selected documents from connected sources are fingerprinted in server memory and discarded immediately. Arkova retains the resulting fingerprint and limited metadata; account and billing details are handled under our Privacy Policy.
Inspect a public record
Look up a real record.
Enter a public ID to review its reported status, issuer label, network observed time, and receipt. The lookup does not check a file you hold or prove the issuer's authority. No account required.
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.
One public ID, structured response
Record lookup in one call
Use Arkova's REST API to look up a public ID and retrieve reported status and anchor details. Talk with us about the connectors and workflow your systems need.
- Single-call & batch verification (REST)
- MCP integration — confirm available tools with your account
- DocuSign & document-source anchoring
- HMAC-signed webhooks & API keys
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.
Or get the event pushed to you
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.
- Public ID
- ARK-DOC-HKUK9N
- Status at snapshot
- ACTIVE
- Network observed
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.
Watch it run
From document to public record lookup
Watch a record being created in Arkova and looked up by public ID. The lookup reports record details; comparing a document requires a copy of the file.
For the whole chain
One shared record, every side of the handoff
From the person sharing a credential to the reviewer checking it, a public ID gives both sides the same record to inspect.
Legal Departments
Keep a checkable reference for important contracts and evidence as files move between systems.
Students & Learners
Share a public record ID for a credential issued through Arkova, so a recipient has a clear place to look it up.
Registrars & Institutions
Give recipients public record IDs they can use to review status and anchor details.
Compliance & Audit Teams
Add a document-integrity check to evidence review. A matching file and its record details help reviewers trace a version.
The trust shift
When a record changes hands,
keep a way to check it.
A convincing file is not enough
Documents can be copied or altered without an obvious visual clue. A fingerprint comparison checks whether a file matches the recorded version.
Evidence moves between systems
Exports, handoffs, and migrations make versions harder to track. A public record ID gives reviewers a consistent reference point.
Status and integrity are different checks
An anchor helps check a file against a recorded fingerprint. Current record status is a separate service lookup and may lag recent changes.
Published details
Security details you can inspect
Read our published self-assessment and inspect a real public record. Each shows a different part of the system.
CSA STAR Level 1
Self-Assessment · Listed since Jun 2026
Our security controls are documented publicly in the Cloud Security Alliance STAR Registry, mapped to the CAIQ v4.1.0 Cloud Controls Matrix. STAR Level 1 is a published self-assessment — an industry-standard disclosure of our controls, not a third-party audit or certification.
View our STAR Registry listingDirect uploads stay local
Files you upload are fingerprinted in your browser. Selected connected-source files are fingerprinted in server memory and discarded, as described in our Privacy Policy.
Public anchor details
The sample record exposes a network checkpoint and receipt. Use its public ID to request updated status.
Document match check
With a copy of a document, a recipient can compare fingerprints to see whether it matches the recorded version.
Collaborations
Who we build with
Publicly announced work with legal technology, agent identity, and digital-finance teams — each at a different integration stage.
Legal technology collaboration
HakiChain
HakiChain has announced Arkova for document-integrity checks in its HakiDocs workflow.
Agent identity · Staging integration
ComputeID
ComputeID says its credential-revocation webhook integration with Arkova is moving into staging.
Digital finance · Planned integration
Certen Protocol
Certen has announced plans to connect Arkova document checks to its authorization workflow.
Arkova Monthly
Keep up with what we're shipping
Product, security, and partnership updates in Arkova Monthly. Browse the July 2026 issue as a dated archive of what the team was building and discussing then.
Articles
From the team
The Missing Gap in the Agentic IAM Discussion
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.
The State of Compliance in 2026: Why More Frameworks Won't Fix the Evidence Problem
Audit fees vary sharply by filer size and year. AI, cybersecurity, and operational-resilience rules add different obligations in different sectors; none is satisfied by a network receipt alone.
The Rise of the Agentic Economy: How AI Agents Are Becoming Economic Participants
AI agents are beginning to initiate transactions and use enterprise tools. Payments, delegated authority, identity, and document integrity each need a different control.
Why we built this
We built this because verification is broken at every level
Carson Seeger
Founder & CEO
10+ years in technical product and program management across regulated industries. Built Arkova to help organizations check document integrity as records move between systems.
LinkedIn
Sarah Rushton
Founder & COO
Over 20 years launching products through compliance-heavy supply chains taught Sarah one thing: documentation verification is broken at every level.
LinkedIn
Dr. Yaacov Petscher
Founder & Advisor
20 years Research & Data Science experience. Senior Member of the National Academy of Inventors.
Google ScholarAdvisors & team
Jenny Parks
Higher Education Advisor
Over 30 years in higher education and digital credentials, guiding Arkova’s credentialing and professional-licensing work.
LinkedInUyiosa Israel
Business Development Lead, Africa
Leads sales, partnerships and regulatory insight across the continent, starting with the Kenya pilot.
LinkedInWhat skeptics ask
Common questions
What does Arkova actually do?
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.
How is this different from DocuSign, a notary, or a timestamp service?
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.
Do you store my documents?
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.
Can my document be reconstructed from the fingerprint?
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.
What does “tamper-evident” actually mean?
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.
What happens if Arkova goes away?
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.
What is the “public network” you anchor to?
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.
How does someone verify a record?
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.
Can a record be revoked or corrected after it’s anchored?
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.
Can I integrate it with my systems?
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.
Is it available now?
Yes. Arkova is live. Get started in the app, or talk with us about an integration or pilot.
Give the next person a record they can check
Arkova is available now. Start in the app, or talk with our team about an integration or organizational use.
Investor or partner? View the pitch deck or write to founders@arkova.ai.
Last updated: September 2026