# Vereef

*/Startups/Vereef*

## Startup Overview

This digital identity verification engine allows individuals to prove specific credentials without exposing their underlying raw data. By deploying zero-knowledge proofs, the system mathematically authenticates identity claims directly between the user and the relying party.

Regulated platforms face compounding liabilities when collecting and storing personally identifiable information. Standard verification requires users to hand over sensitive documents, creating centralized data honeypots and forcing companies to manage toxic data assets simply to establish user trust.

Legacy identity brokers like Jumio and Socure rely on probabilistic biometric matching and vast data repositories, while traditional OAuth providers track user behavior across the web. This engine bypasses centralized data collection entirely. The validation process is fully deterministic, delivering absolute certainty of an identity claim while remaining completely privacy-preserving.

## Startup Founding Hypothesis

**Approach**: that validates digital identity claims via zero-knowledge proofs
**Competitors**:
- [Jumio](/Competitors/Jumio)
- [Socure](/Competitors/Socure)
- [traditional OAuth providers](/Competitors/traditional_OAuth_providers)
**Differentiator2x2**: fully deterministic in its validation and completely privacy-preserving

## Startup Solution Coordinate

**Solution**: [Zero Knowledge Identity Engine](/Software/Zero_Knowledge_Identity_Engine)

## Startup Position2x2

```mermaid
quadrantChart
title Digital Identity Validation Landscape
x-axis "Probabilistic Heuristics" --> "Deterministic Validation"
y-axis "High Data Exposure" --> "Zero-Knowledge Privacy"
quadrant-1 "Cryptographic Proofs"
quadrant-2 "Private Heuristics"
quadrant-3 "Legacy Identity"
quadrant-4 "Opaque Centralized Auth"
Jumio: [0.25, 0.20]
Socure: [0.15, 0.15]
Traditional OAuth Providers: [0.80, 0.35]
Vereef: [0.90, 0.90]
```

## Startup Offer

**Proof**:
- Targeting sub-100 millisecond server-side proof verification for high-frequency application onboarding.
- Aiming to deliver zero plaintext PII exposure during regulated age-gating flows.
- Designed to eliminate manual human-in-the-loop fallback reviews by relying on 100% deterministic logic.
**Tiers**:
- Name: Developer API · Price: ~$0.15–$0.25 per verification · Inclusions: Access to standard zero-knowledge proof verification endpoints, intended for up to 10,000 monthly identity claims with standard rate limits.
- Name: Volume Verification · Price: ~$0.08–$0.12 per verification · Inclusions: Higher throughput endpoints designed for >10,000 monthly claims, including batch processing capabilities and dedicated webhook support.
- Name: Custom Circuit · Price: Custom rate (~$0.02–$0.05 per verification at scale) · Inclusions: Engineering support to design bespoke validation circuits for highly specific compliance rules, with intended SLA uptime guarantees.
**Guarantee**: If a cryptographically validated identity claim produces a false positive that bypasses the deterministic circuit, the verification fee for that billing cycle is refunded and a cryptographic root-cause analysis is delivered within 48 hours.
**Business Function**: ProvideService
**Objection Handlers**:
- ZKP generation is too slow for real-time mobile onboarding: Vereef is designed to offload proof generation to the client device, requiring the server only to verify the cryptographic proof in milliseconds.
- Regulators require us to hold user data, so privacy-preserving tech violates compliance: You store the verifiable credential and the mathematical proof of validation, which is intended to satisfy audit requirements without holding raw, breachable PII.
- Consumers do not have digital wallets to hold identity credentials: The system is built to support temporary, session-based credentials that execute in the browser, requiring no wallet installation by the end user.
- OAuth is easier to implement: While OAuth relies on centralized third parties logging user activity, Vereef is designed to provide the same one-click developer experience while stripping out the tracking architecture.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Authoritative and precise, driven by uncompromising cryptographic certainty.
**Tagline**: Deterministic identity verification without exposing private user data.
**Icon Concept**: seal
**Palette Intent**: electric-signal
**Visual Identity**: A stark palette of deep obsidian and cryptographic neon green pairs with monospaced typography to evoke secure mathematical environments.
**Archetype Reference**: the-sage

## Startup Buyer Chain

**Chain**: Vereef → IAM Engineering Team → Application End User
**Gtm Motion**: Acquisition centers on developer-led integrations where engineering teams test the zero-knowledge proof SDKs in a free sandbox environment. Expansion occurs by converting successful proofs-of-concept into enterprise contracts based on the monthly volume of deterministic validation queries.
**Agent Channel**: Designed to target the LangChain tool catalog and OpenAI schema directories as a credential module, enabling autonomous compliance agents to programmatically request and validate zero-knowledge identity proofs.
**Primary Channel**: Developer search queries for privacy-preserving KYC API and ZKP identity verification that direct identity engineers to the interactive API documentation and open-source GitHub repositories.

## Startup Customer Journey

```mermaid
flowchart LR; A[Developer Search] --> B[API Documentation]; B --> C[Sandbox Environment]; C --> D[SDK Integration]; D --> E[Production Endpoint]; E --> F[Volume Contract]; F --> G[Custom Validation Circuit];
```

## Startup Proof Points

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Pilot Goals**:
- A 14-day parallel deployment alongside an existing onboarding flow to confirm sub-100 millisecond server-side processing without impacting user conversion.
- A batch-processing trial aiming to process 10,000 identity claims to validate that the deterministic circuit handles high throughput with zero plaintext data exposure.
**Target Metrics**:
- Target: Sub-100 millisecond server-side proof verification time.
- Aim: 100 percent reduction in plaintext PII storage for compliant age-gating flows.
- Target: Zero manual human-in-the-loop fallback reviews required for standard identity claims.
- Aim: 0 percent false positive rate bypassing deterministic circuits in production.
**Target Case Studies**:
- A high-growth fintech application aiming to replace manual KYC fallback reviews with deterministic cryptographic circuits to accelerate user onboarding.
- An age-restricted e-commerce platform targeting a shift from storing raw user IDs to holding verifiable credentials to eliminate PII liability.
- A decentralized application seeking to validate user jurisdictions without forcing end-users to install third-party identity wallets.
**Testimonial Targets**:
- A Chief Compliance Officer expressing confidence that audit requirements are fully satisfied by storing mathematical proofs instead of breachable user data.
- A Lead Mobile Engineer noting that integrating the verification endpoint is as frictionless as standard OAuth without the centralized tracking.
- A VP of Product confirming that session-based credentials execute seamlessly in the browser without forcing users to download a digital wallet.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Financial regulators reject zero-knowledge proof attestations as non-compliant for strict KYC and AML reporting requirements. · Mitigation Status: unmitigated
- Severity: high · Description: Major credential issuers refuse to adopt the required cryptographic standards necessary to generate the underlying identity proofs. · Mitigation Status: unmitigated
- Severity: high · Description: Client-side generation of zero-knowledge proofs causes unacceptable verification latency or battery drain on standard mobile devices. · Mitigation Status: in-progress
- Severity: moderate · Description: Users abandon the onboarding flow due to the complexity of managing local cryptographic keys instead of familiar OAuth logins. · Mitigation Status: in-progress

## Startup Competitors

- [Jumio](/Competitors/Jumio) — Incumbent
- [Socure](/Competitors/Socure) — Incumbent
- [Traditional OAuth Providers](/Competitors/Traditional_OAuth_Providers) — Status Quo
- [Polygon ID](/Competitors/Polygon_ID) — Web3 Identity
- [Manual KYC](/Competitors/Manual_KYC) — Status Quo

## Startup Solution Stack

- [Identity Validation Service](/Services/Identity_Validation_Service) — Service-as-Software
- [Zero Knowledge Proving Agent](/Agents/Zero_Knowledge_Proving_Agent) — Agent
- [Claim Resolution Worker](/Agents/Claim_Resolution_Worker) — Agent
- [Identity Claim API](/Software/Identity_Claim_API) — Software
- [ZKP Generation SDK](/Software/ZKP_Generation_SDK) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be an architect of trust who eliminates data breach liability by design
- **Want**: to verify user identities instantly without the risk of holding raw sensitive data
- **Identity**: the engineering lead at a high-growth fintech startup
**Plan**:
- Step: Select claims · Detail: Define the specific compliance rules or identity attributes your application needs to verify.
- Step: Audit logic · Detail: Review the deterministic circuit that validates user credentials without exposing the underlying PII.
- Step: Deploy verification · Detail: Embed the developer API to trigger sub-second, privacy-preserving identity checks on every new signup.
**Guide**:
- **Empathy**: You shouldn't still be babysitting manual document reviews. Jumio wasn't built to verify claims without seeing the underlying data.
**Problem**:
- **Villain**: PII liability
- **External**: Onboarding users via Jumio or Socure requires storing plaintext PII that creates a massive attack surface for data breaches
- **Internal**: You feel like you are sitting on a ticking time bomb every time you collect a user's ID
- **Philosophical**: Why should users accept the exposure of their private life when mathematical proof of age or residency is possible?
**Success**: Users onboard in milliseconds with total privacy, while your database stores only cryptographic proofs instead of risky personal documents.
**One Liner**: Storing raw PII costs fintechs millions in breach liability and manual review time. Vereef validates digital identity claims via zero-knowledge proofs so users stay private and companies stay compliant without the risk.
**Positioning**:
- **So That**: verify compliance without the liability of holding sensitive user data
- **Unlike**: traditional PII-storage providers like Jumio
- **For Whom**: engineering leads at high-growth fintech startups
- **Category**: Zero-Knowledge Identity Verification
**Call To Action**:
- **Direct**: Integrate Developer API
- **Transitional**: Review Cryptographic Schema
**Failure Stakes**:
- Exposure to catastrophic data breaches
- High costs of manual human-in-the-loop reviews
- User drop-off from slow onboarding
**Transformation**:
- **To**: one of the few engineering leads who eliminates data liability entirely
- **From**: a developer managing massive PII honeypots in databases
**Controlling Idea**: Mathematical proof should replace the storage of sensitive personal data.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Storing raw PII costs fintechs millions in breach liability and manual review time. Vereef validates digital identity claims via zero-knowledge proofs so users stay private and companies stay compliant without the risk.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: d269c579e870cb85

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Zero-Knowledge Identity Verification for engineering leads at high-growth fintech startups. Unlike traditional PII-storage providers like Jumio — verify compliance without the liability of holding sensitive user data.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 4692f83f6989f73c

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Onboarding users via Jumio or Socure requires storing plaintext PII that creates a massive attack surface for data breaches
Solution: Storing raw PII costs fintechs millions in breach liability and manual review time. Vereef validates digital identity claims via zero-knowledge proofs so users stay private and companies stay compliant without the risk.
Customer: engineering leads at high-growth fintech startups
Unlike: traditional PII-storage providers like Jumio
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 391c74383a642f25

## Startup Token M E D D P I C C

**Pain**: Onboarding users via Jumio or Socure requires storing plaintext PII that creates a massive attack surface for data breaches
**Metrics**: Target: Users onboard in milliseconds with total privacy, while your database stores only cryptographic proofs instead of risky personal documents.
**Rendered**: Pain: Onboarding users via Jumio or Socure requires storing plaintext PII that creates a massive attack surface for data breaches
Economic buyer: IAM Engineering Team
Metrics: Target: Users onboard in milliseconds with total privacy, while your database stores only cryptographic proofs instead of risky personal documents.
Competition: traditional PII-storage providers like Jumio
**Mechanism**: spine-derived-v1
**Competition**: traditional PII-storage providers like Jumio
**Economic Buyer**: IAM Engineering Team
**Vocab Fingerprint**: 8e601c75ceed17ce

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Zero-Knowledge Identity Verification for engineering leads at high-growth fintech startups

engineering leads at high-growth fintech startups — Onboarding users via Jumio or Socure requires storing plaintext PII that creates a massive attack surface for data breaches Storing raw PII costs fintechs millions in breach liability and manual review time. Vereef validates digital identity claims via zero-knowledge proofs so users stay private and companies stay compliant without the risk.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 721e417cdbd57286

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Zero-Knowledge Identity Verification. Storing raw PII costs fintechs millions in breach liability and manual review time. Vereef validates digital identity claims via zero-knowledge proofs so users stay private and companies stay compliant without the risk. Serves engineering leads at high-growth fintech startups.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 2dce1c8f9fc97ef8

## Neighborhood

### Candidate solutions

- [Procure Specialty Foam Materials](/Problems/Procure_Specialty_Foam_Materials) — candidate solution for · Problems

### Composed of

- [Identity Validation Service](/Services/Identity_Validation_Service) — composes · Services
- [ZKP Generation SDK](/Software/ZKP_Generation_SDK) — composes · Software
- [Identity Claim API](/Software/Identity_Claim_API) — composes · Software
- [Claim Resolution Worker](/Agents/Claim_Resolution_Worker) — composes · Agents
- [Zero Knowledge Proving Agent](/Agents/Zero_Knowledge_Proving_Agent) — composes · Agents

### What it offers

- [Zero Knowledge Identity Engine](/Software/Zero_Knowledge_Identity_Engine) — offers · Software

### Embodies

- [Software](/Theses/Software) — embodies · Theses

### Competitors

- [Socure](/Competitors/Socure) — competes with · Competitors
- [Manual KYC](/Competitors/Manual_KYC) — competes with · Competitors
- [Polygon ID](/Competitors/Polygon_ID) — competes with · Competitors
- [Traditional OAuth Providers](/Competitors/Traditional_OAuth_Providers) — competes with · Competitors
- [Jumio](/Competitors/Jumio) — competes with · Competitors

### Similar Startups

- [Creedoblem](/Startups/Creedoblem) — similar · Startups
- [Verification](/Startups/Verification) — similar · Startups
- [Ines](/Startups/Ines) — similar · Startups
- [Eonen](/Startups/Eonen) — similar · Startups
- [Medale](/Startups/Medale) — similar · Startups
- [Forgide](/Startups/Forgide) — similar · Startups
- [Identitygem](/Startups/Identitygem) — similar · Startups
- [Autay](/Startups/Autay) — similar · Startups
- [Matchain](/Startups/Matchain) — similar · Startups
- [Creedint](/Startups/Creedint) — similar · Startups
- [Jumio](/Startups/Jumio) — similar · Startups
- [Idiver](/Startups/Idiver) — similar · Startups
- [Ciphermill](/Startups/Ciphermill) — similar · Startups
- [Verificationrow](/Startups/Verificationrow) — similar · Startups
- [Verificationhaze](/Startups/Verificationhaze) — similar · Startups
- [Verifiableridge](/Startups/Verifiableridge) — similar · Startups
- [Auroraverify](/Startups/Auroraverify) — similar · Startups
- [Dimit](/Startups/Dimit) — similar · Startups
- [Verook](/Startups/Verook) — similar · Startups
- [Zeroworks](/Startups/Zeroworks) — similar · Startups