ProofMail · built on Axle

Email-native delivery for independent proof artifacts.

ProofMail lets teams send, route, verify, and preserve signed proof artifacts — without making either party the source of truth.

See how it works →

Independent verification · No account required

Today, proof of delivery, disclosure, or approval lives in someone's inbox, someone's database, or someone's memory — and disappears the moment any of those fail.

“Email is where this evidence already gets exchanged. It's just never been the evidence itself.”

How it works

01

Axle generates the artifact

A signed proof artifact — claim, evidence hash, canonical payload — created independently of any inbox or database.

02

ProofMail delivers it

Routed and access-tracked as an ordinary email. No walled garden, no proprietary reader.

03

Anyone verifies it independently

No ProofMail account, no trusting the sender. The artifact carries its own proof.

ARTIFACTPROOFMAILVERIFIED

The proof doesn't depend on:

  • Sender lies about what was sent
  • Recipient claims they never received it
  • Thread is deleted from the inbox
  • Provider account is closed
  • Central database is corrupted
  • Parties disagree on the terms
  • ProofMail is unavailable

The artifact still verifies.

Use cases

LEGAL

Disclosure proof

Independent evidence that a specific document version was delivered on time.

BANKING

Approval proof

Signed record of treasury approval that lives outside the bank's internal database.

COMPLIANCE

Decision proof

Audit-ready trail of governance decisions that survives system migrations.

INSURANCE

Policy proof

Undeniable timestamp of when a policy change was communicated to the insured.

HEALTHCARE

Consent proof

Portable evidence of informed consent that outlives any single EHR vendor.

See all artifact types →
Positioning

Not secure email.

Not certified mail.

Not an inbox.

A proof artifact delivery layer.

For developers

receipt.json
{
  "version": "1.0",
  "artifact": {
    "type": "approval_v2",
    "claim_hash": "sha256:e3b0c442...",
    "evidence_hash": "sha256:7f83b165...",
    "signature": "sig_8f2a9x0..."
  },
  "delivery": {
    "channel": "proofmail",
    "recipient": "legal@corp.com",
    "delivered_at": "2026-07-18T09:14:22Z"
  },
  "verifier": "https://verify.proofmail.io"
}
// Send a signed artifact
curl -X POST https://api.proofmail.io/v1/send \
  -H "Authorization: Bearer ax_…" \
  -d '{"artifact": "0x82f…", "to": "legal@corp.com"}'

Two paths in.

Regulated buyers want a conversation. Developers want an API key. Pick your way in.