How does Arkova verify documents without seeing them?

Arkova uses cryptographic fingerprinting (SHA-256) that runs entirely in your browser. We only store the fingerprint, a one-way mathematical proof, never the document itself. This fingerprint is then anchored to a permanent public record.

Can anyone verify a credential?

Yes. Verification is completely open. Anyone with a verification link or QR code can confirm a document's authenticity and timestamp independently. No account or software required.

What types of documents can I anchor?

Any digital file: PDFs, images, spreadsheets, presentations, contracts, certificates, transcripts. If it has a file, it can be fingerprinted and anchored.

How is this different from DocuSign or other e-signature tools?

E-signature tools prove who signed a document. Arkova proves that a specific document existed at a specific time and has not been altered since. These are complementary. You can anchor a signed document to prove it hasn't changed after signing.

Can I integrate Arkova into my existing systems?

Absolutely. Our Verification API lets you verify credentials programmatically with a single API call. Batch endpoints support up to 100 verifications per request. Webhook notifications provide real-time events.

Your documents never leave your device. That's our foundational privacy guarantee, not just a feature. Fingerprints are anchored to a public, independently verifiable network. Even if our servers were compromised, your documents remain private because we never had them.

How does Arkova work with our existing ATS or background check workflow?

Arkova's Verification API integrates with any system that can make an HTTP call. Your ATS, HRIS, or background screening platform calls our endpoint and receives a structured, verified response. We also support webhooks for real-time status updates and batch endpoints for bulk verification.

System Status

1. Current Status

Tip

All systems operational. For real-time status updates, monitor the endpoints below.

Service	Status	Endpoint
Frontend (app.arkova.ai)	Operational	Vercel CDN
Worker API	Operational	Google Cloud Run
Database	Operational	Supabase (managed Postgres)
Network Anchoring	Operational	Production network
Search (search.arkova.ai)	Operational	Vercel
MCP Server (edge.arkova.ai)	Operational	Cloudflare Workers

Health check endpoint: GET /api/v1/health — always available regardless of feature flags.

2. Infrastructure

Component	Provider	Region
Frontend	Vercel CDN	Global edge
Worker	Google Cloud Run	us-central1
Database	Supabase	us-east-1
Edge compute	Cloudflare Workers	Global edge
Network RPC	Mempool.space + Blockstream (fallback)	Global
Payments	Stripe	Global

3. SLA

Arkova targets 99.9% uptime for the Verification API and frontend services.

Worker services auto-scale on Cloud Run (1GB, max 3 instances)
Database circuit breakers protect against cascading failures

Note

Enterprise customers can negotiate custom SLAs. Contact sales@arkova.ai.

4. Incident Response

Documented incident response procedures in compliance with SOC 2 CC7.2.

Severity levels: P1 (service down), P2 (degraded), P3 (non-critical)
Response times: P1 < 15 minutes, P2 < 1 hour, P3 < 24 hours
Post-incident reviews published for P1/P2 incidents
Contact for urgent issues: support@arkova.ai