Varde
On-chain proof that a document, image, or capture came from a human or machine.
Tagline
Proof of origin for digital content
The provenance ledger for content origin.
Privacy-preserving proof, not another detector.
We never see content. Only proof.
The provenance ledger for content origin, not another detector.
The page repeatedly emphasizes hashing, freezing, Varde-ID, and on-chain records; the product is strongest as an origin proof system, not as a generic AI classifier.
Alternative to metadata-dependent verification that disappears when files move.
Varde explicitly checks C2PA, watermarks, clones, and model SDK signatures, but its on-chain proof survives after the original file has been copied, screenshotted, or reposted.
A privacy-preserving authenticity layer for platforms that cannot read user content.
The core promise is that Varde never sees words or pixels, only proofs; that’s a sharp differentiator for enterprises and regulated platforms that need verification without content exposure.
Primary user
Trust and safety lead at a marketplace, media platform, or creator platform that needs provenance checks on user-submitted content
ICP #1
Trust and Safety Lead at a UGC marketplace with 10M+ monthly uploads
Pain
They need to stop AI-generated spam, fake identity evidence, and manipulated images without reading every submission or creating privacy liability.
Why this solves
Varde gives them a public, tamper-resistant proof trail and automated signals like AI, human, camera, or indeterminate, so moderation can be based on provenance instead of manual inspection.
ICP #2
Managing editor at a digital newsroom publishing reader submissions and freelance work
Pain
They are constantly asking whether photos, quotes, and drafts are original, edited, or synthetic, and current checks are brittle and slow.
Why this solves
Varde can freeze a draft or image provenance record at creation time and later verify it with a Varde-ID, giving editors a repeatable authenticity check without seeing the underlying content.
ICP #3
AI platform product manager shipping a generative image or writing tool
Pain
They want their output to be recognizable as machine-made and defensible in downstream disputes, but standard metadata gets stripped and screenshots break traceability.
Why this solves
Varde’s SDK signs model outputs at the moment of creation and anchors proof on-chain, giving the product a durable provenance layer even when files are copied or reuploaded.
Strengths
- +The product promise is unusually crisp: content stays private, proof becomes public and permanent.
- +The page explains the system with concrete mechanics: keystroke dynamics, hashing, C2PA, perceptual hashes, and Base mainnet.
- +The visual examples make the concept tangible by showing HUMAN, AI, CAMERA, and UNVERIFIED verdicts.
Weaknesses
- −It reads like a manifesto, not a product page; there is almost no immediate explanation of who should buy this or why now.
- −The trust claim is too broad and slightly cultish, which may alienate enterprise buyers who need boring, auditable language.
- −There is no pricing, no obvious CTA beyond "Verify Something," and no packaging for different buyer types.
- −The page over-indexes on technical mystique and under-explains workflow integration, API use cases, and operational deployment.
- −The distinction between biometric proof, image SDK, and public verification is impressive but buried under dense copy.
Fix these
- Add a direct enterprise use-case section for marketplaces, newsrooms, and AI labs with concrete workflows and outcomes.
- Reframe the headline around provenance and privacy in plain language, then keep the poetic copy as a secondary layer.
- Publish integration docs and sample API endpoints for upload, verify, and SDK signing so buyers can understand implementation effort.
- Add trust signals that enterprise buyers expect: security overview, audit details, retention controls, and compliance notes.
- Create separate landing paths for text provenance, image provenance, and public verification instead of one all-in-one page.
Drop-in replacement copy
Headline
Proof of origin, on-chain
Verify text and images without exposing the content
Freeze origin at creation time
Varde captures the signals that matter when a document or image is made, then freezes a tamper-resistant proof record. The proof stays public even when the file gets copied, compressed, or reposted.
Verify without reading the content
Content stays on the user’s machine. Varde only stores the proof trail, so trust and safety, editorial, and compliance teams can validate origin without taking on unnecessary data exposure.
Text, image, and model workflows
For text, Varde measures typing rhythm and micro-corrections. For images, it checks SDK signatures, C2PA, watermark signals, and perceptual hashes before writing the verdict to Base.
Public Varde-ID certificates
Every frozen record gets a Varde-ID and verification URL. Anyone can later confirm whether the content was marked HUMAN, AI, CAMERA, or indeterminate.
FAQ
Is Varde a detector?
No. It is a provenance system. Detectors guess after the fact; Varde creates a proof of origin at creation time and makes it verify later.
Do you read the content?
No. The design is privacy-preserving. We capture proof signals and metadata needed for verification, not the underlying text or pixels.
What happens when metadata is stripped?
That is exactly why the proof is anchored outside the file. Even if a file is copied or screenshots are taken, the Varde-ID record still exists.
Who is this for?
Trust and safety teams, newsrooms, enterprise risk teams, and AI products that need durable proof of origin without exposing user content.
How do people verify a record?
They open the public verification link or Varde-ID and see the origin verdict, timestamp, and proof record anchored on Base.
Varde freezes proof of origin for text and images. Human typing rhythm. Model signatures. C2PA. Watermarks. Perceptual hashes. Then it anchors the verdict on Base and gives every file a public Varde-ID. We never see your content. Only the proof.
Files move. Metadata dies. Screenshots survive. Varde is built for provenance that survives copying. Capture the origin once, freeze it on-chain, and let anyone verify HUMAN, AI, CAMERA, or indeterminate later. That’s the whole product.
Most content tools try to detect AI after the fact. That’s too late. Varde is different: prove origin at creation time, then make the proof public and permanent. Private content stays private. The record does not. Much better trade.
For text, Varde measures pause patterns, dwell, flight, and micro-corrections. Not to read the content. To prove how it was made. That lets platforms separate human drafts from machine output without storing the underlying text.
If you run a marketplace, newsroom, or creator platform, you already know the pattern: fake screenshots synthetic submissions edited images plausible deniability Varde gives you origin proof instead of vibes.
Metadata is fragile. Copy the file, strip the header, repost the image, and the trail is gone. Varde anchors the proof outside the file itself, so the verification link still works after the asset has been copied, compressed, or screenshotted.
Type in the editor. Freeze. Get a Varde-ID and a verification link. Now anyone can check whether that record was marked HUMAN, AI, CAMERA, or indeterminate — without seeing the actual document.
Upload an image or sign it from your model SDK. Varde checks C2PA, watermark signals, perceptual-hash neighbors, and model-origin signatures. Then it writes a public proof record to Base. No black box moderation theater.
The teams who care about provenance don’t want another classifier. They want an audit trail they can show legal, policy, and ops. That’s why Varde is built as a verification layer, not a guess machine.
Enterprises keep saying the same thing: we need to verify content without reading it. Varde does exactly that. Content stays on the user’s machine. The proof goes public. The tension disappears.
Angle: provenance ledger
Most companies do not have an AI-content problem. They have a provenance problem. They do not know where a draft came from. They do not know whether an image was camera-captured, generated, or edited. They do not know whether a submission was produced by a human or a model. That is why we built Varde. Varde creates a proof of origin for text and images without exposing the underlying content. We capture signals at creation time, freeze the record, and anchor it on Base. Then anyone can verify the result later through a public Varde-ID. The important part is not the chain. It is the separation of content and proof. Private content stays private. The provenance record becomes durable, auditable, and shareable. If you run trust and safety, editorial operations, or content infrastructure, this is the layer you have been missing.
Angle: privacy-preserving verification
A lot of verification tools fail for one simple reason: They need to see the content. That is a bad fit for regulated platforms, enterprise workflows, and any system that cannot afford to inspect user data just to validate it. Varde was designed around a different assumption. We never see the document or image itself. We only capture enough evidence to prove origin, classify the result, and write a public verification record. For text, that means timing and rhythm signals from the editor. For images, that means SDK signatures, C2PA validation, watermark detection, and perceptual-hash checks. The outcome is simple: HUMAN AI CAMERA indeterminate This is not about replacing moderation. It is about giving moderation a stronger primitive. Origin before opinion.
Angle: workflow integration
The best trust systems disappear into workflow. They do not ask editors to do extra work. They do not ask creators to change habits. They do not add another dashboard nobody opens. Varde is meant to sit at the point of creation. A writer types. A model outputs. A camera captures. A team freezes the record. From there, the proof can be checked later by anyone with the Varde-ID. That means the same system works for a newsroom, a marketplace, or an AI product shipping provenance by default. If you are thinking about deployment, this is the question to ask: Where does trust get created in your workflow? That is where provenance should live.
No visuals for this kit yet.
Tagline
Proof of origin for text and images
Description
Varde creates public, tamper-resistant provenance for digital content. Capture human, AI, or camera origin without exposing the underlying file, then verify it later with a Varde-ID on Base.
Maker's first comment
We built Varde because content verification kept collapsing into two bad options: either you inspect the content directly, or you trust fragile metadata that disappears the moment a file is copied, compressed, or screenshotted. We wanted a third option: capture proof at creation time, keep the content private, and make the proof public and permanent. That led us to a text editor that measures typing rhythm, an image flow that checks SDK signatures, C2PA, watermark signals, and perceptual hashes, and an on-chain record on Base that anyone can verify later. This is the version we wish existed when people started asking, ‘Can you prove where this came from?’ Would love feedback from teams who run trust and safety, editorial workflows, or AI products that need durable provenance.
Pinned maker comment
Would love feedback on the enterprise packaging, the wording of HUMAN / AI / CAMERA / indeterminate, and which workflow should be the default entry point: text, image, or public verification.
Meta
Stop moderating blind. Verify origin.
Hypothesis: trust and safety teams will convert better when the promise is provenance, not detection. Varde creates a proof of origin for text and images without exposing the content. Freeze the record, anchor it on Base, and verify HUMAN, AI, CAMERA, or indeterminate later.
Google Search
Content provenance API for platforms
Hypothesis: buyers searching for AI detection are actually looking for origin proof and auditability. Varde gives marketplaces, newsrooms, and AI products a privacy-preserving provenance layer for text and images. Content stays private. Verification stays public.
Reddit Promoted
We built a proof layer, not a detector.
Hypothesis: indie founders and platform operators care more about verifiable origin than classification accuracy. Varde captures proof at creation time for text and images, then anchors it on-chain so the record survives reposts, screenshots, and file stripping.
Subreddits
r/SideProject
Show the product as a weird but useful provenance layer for text and images, with a short demo and one clear use case.
Rules: Read the sidebar; self-promo is tolerated only if useful and transparent. Lead with the problem and mechanics, not hype.
r/indiehackers
Build-in-public post on why detectors fail and why proof-at-creation is the better wedge.
Rules: No spammy promotion; share the lesson, the product, and what you learned building it.
r/microsaas
Position it as a niche infra product for trust teams and AI tools, with clear buyer and workflow.
Rules: Keep it practical and founder-focused. Show what it does and who buys it.
r/EntrepreneurRideAlong
Founder story about going after an unsexy compliance/trust problem with a sharp technical angle.
Rules: The community likes journey posts. Be specific about the problem, not promotional.
r/startups
Discuss provenance as infrastructure for the post-AI internet, with examples from marketplaces and newsrooms.
Rules: Avoid pure marketing. Tie it to startup strategy, distribution, or product-market fit.
Communities
Join discussions on synthetic media, UGC verification, and moderation tooling. Offer a demo and ask for brutal feedback on workflow fit.
Post the build story, then DM people building marketplaces, creator tools, or AI infra. Ask which buyer pain is sharpest.
Launch with a crisp demo, maker comment, and one sentence on why this is not another detector. Reply fast to every comment.
Cold outreach template
Hey {firstName} — saw {context} and thought of Varde. It gives you proof of origin for text/images without reading the content, so your team can verify HUMAN, AI, or CAMERA later. If provenance is on your roadmap, I’d love to show you the 2-minute flow.
Product Hunt timing
Launch Tuesday morning UTC after shipping docs and a short demo video; that gives you a full day to respond to comments and lets HN/LinkedIn momentum carry into Product Hunt traffic.
Indie Hackers post ideas
- 01We built a proof-of-origin layer because AI detection is the wrong problem
- 02How we verify text and images without seeing the content
- 03From keystrokes to on-chain proof: building Varde for trust teams
Competitor alternatives
Current tone of voice
Mythic, declarative, and cryptographic, with lines like “trust what you see” and “we never see your content — only the proof. The proof is forever.”
Your kit is ready. Sign up free to unlock, takes 10 seconds.
7 more X posts · 2 LinkedIn · Product Hunt copy · ad hooks · 100-user playbook · landing critique