Vertifile landing page: a self-contained tamper-evident document file with SHA-256 content binding, Ed25519 dual-signing, Polygon anchoring, and IANA registration. The hero shows documents traveling through a Vertifile shield gate and emerging as sealed, verified .pvf files.

Enterprise Healthcare Education Finance
Pricing Developers Demo Blog Contact My Account
Verify Protect
Blind Mode: Client-Side Encryption

Documents That
Prove Themselves

Seal any document with patent-filed, IANA-registered verification technology. Built for audit and legal evidence workflows. A forged copy cannot pass verification.

Patent Pending IANA MIME Type Registered Cryptographically Sealed
02 · 5 / DEMO

See it in action

Vertifile in 20 seconds.

Watch a document become tamper-evident — sealed, signed, and anchored, so anyone can verify it without trusting us.

Muted by default · click for sound

01 / PROOF

The trust model, inverted

A signature you can check. Not a promise you have to believe.

Most "secure" documents ask you to trust a vendor, a portal, or a login. A .pvf carries its own proof. The evidence travels with the file — anyone, anywhere, can verify it offline, against a public key, forever.

.pvf

Self-contained evidence

One file holds the document, its cryptographic fingerprint, the signatures, and the verification logic. No server call required to prove it.

Dual-signed integrity

HMAC-SHA256 for content integrity, Ed25519 for sender identity. Alter a single byte and verification fails — the seal freezes red.

Permanent public record

Each document's fingerprint is anchored on the Polygon blockchain — an independent timestamp no one, including us, can rewrite.

02 / CRYPTO

How the proof works

Four independent checks. Any one fails, it's forged.

The crypto, made legible. When a .pvf is opened, the verifier recomputes the proof from scratch and compares it against what's sealed inside. No trust required — only math.

STEP 01

Content fingerprint

The verifier recomputes the document's SHA-256 hash and compares it to the one sealed at signing time. Identical means untouched.

sha256(doc) == sealed_hash
STEP 02

Identity signature

The Ed25519 signature is checked against the issuer's published public key. Proves who sealed it — and that the hash wasn't swapped.

verify(pubkey, sig) → true
STEP 03

Blockchain anchor

The fingerprint is looked up on Polygon. A confirmed anchor proves the document existed, unchanged, at that block's timestamp.

anchor(hash) ∈ polygon
STEP 04

Format integrity

The .pvf container itself — an IANA-registered format — is validated end to end, so the verification logic can't be quietly stripped out.

vnd.vertifile.pvf · ok
03 / TRUST

Trust signals · all independently checkable

Everything we claim, you can confirm without us.

Real cryptography, a registered standard, and a public key. These aren't badges — they're verifiable facts.

Verification record
Hash algorithmSHA-256
SigningHMAC-SHA256 + Ed25519
Anchor networkPolygon mainnet
Anchor contract0xC31e…a7F4
MIME typeapplication/vnd.vertifile.pvf
Verifies offlineyes
Vertifile issuer public key (Ed25519)
ed25519:8f3a 2c91 d4e7 b06f 5a18 c2d9 e74b 11a6 33fc 90be 4d27 a8c1 ef05 7b62 9d4a 0e83

Patent filed · Israel

A novel verification architecture, filed at the Israel Patent Office.

PATENT PENDING

IANA-registered format

application/vnd.vertifile.pvf is an officially recognized media type.

REGISTERED

Live on Polygon

Document fingerprints are anchored on Polygon mainnet — publicly auditable.

ON-CHAIN

Open verification

The public key is published. Verify any .pvf against it — no account, no API.

NO TRUST NEEDED
04 / PRIVACY

Blind mode · zero-knowledge

We can seal your document without ever seeing it.

In Blind mode, the fingerprint is computed on your side. Your content is encrypted end to end before it ever leaves the device. We hold the proof — never the document.

  • Content stays private — encrypted client-side
  • Still fully verifiable by anyone you share with
  • Built for HIPAA, legal, and regulated workflows
05 / PLANS

Pricing

Pick a plan. Keep the proof either way.

Same cryptography in every tier. You're paying for scale and branding — never for the right to verify.

Pro

$29/mo
  • Up to 500 sealed documents / month
  • SHA-256 + Ed25519 dual-signing
  • Polygon anchoring included
  • Blind zero-knowledge mode
Start with Pro
Most popular

Business

$79/mo
  • Unlimited sealed documents
  • Custom branding on the seal
  • API access for automation
  • Everything in Pro
Choose Business

Verifying a .pvf is always free — anyone, forever.

Ready when you are

Seal it once. Prove it forever.

Turn your next contract, diploma, or record into a file that defends itself. See it happen live, or talk to us about rolling it out.

Live demo Watch a document verify No signup — see the proof lock in

Talk to us

Book a demo

Tell us where documents flow through your org — we'll show you how to seal them.

We reply within one business day. No spam, ever.

Thanks — we're on it.

We'll be in touch shortly to set up your demo.