ObsignEvidence packages Create a case

For recipients · free public verification

Don’t trust the package.
Re-run it.

.obcase is not a file you are expected to already own. The Obsign Evidence Workstation creates it from an ordinary image, then hands it to a recipient. This page lets that recipient independently check every byte, signature, custody link, and portable computation.

Start with an image I received a package
  • 0evidence bytes
    uploaded
  • 9assurance layers
    reported
  • ON-DEVICElocal Rust/WASM
    verification
OBCASE // INDEPENDENT REVIEWSTANDBY
  1. 01Package bytesManifest + every memberCHECK
  2. 02Signing identityEd25519 + issuer policyCHECK
  3. 03Chain of custodySource + normalizationCHECK
  4. 04Portable operationRe-executed in memoryCHECK
  5. 05DeliverySigned result + pixelsCHECK
NETWORKNO EVIDENCE EGRESS

The missing first step, made explicit

You bring the image.
Obsign makes the case.

Start with a PNG, JPEG, TIFF, BMP, or WebP. The local Windows workstation preserves the source, creates an encrypted examiner identity, records custody, applies the portable operation, signs every claim, verifies the finished package, and exports one .obcase file.

Get the workstation Why creation stays on the workstation

Creator access is currently issued directly while the public Windows installer completes organization code signing and external release validation.

  1. 01
    YOUR INPUTChoose ordinary evidence

    Select a supported source image. Obsign copies its original bytes exactly before processing.

    PNG · JPEG · TIFF · BMP · WEBP
  2. 02
    LOCAL IDENTITYName the case and sign

    Create an encrypted examiner identity in the app or choose an organization-managed key.

    ED25519
  3. 03
    SELF-CHECKCreate and independently re-run

    The package is not released unless the native verifier reproduces its operation and validates every binding.

    FAIL CLOSED
  4. 04
    HANDOFFSend one portable case

    The recipient gets the evidence, receipts, report, and reproducible operation inside one .obcase.

    READY TO VERIFY
Recipient-controlledFail-closed policyMachine-readable findingsFree to verify

Received a package? Continue here.

Open the handoff. Inspect the whole claim.

No login. No upload. No “trust us” API call. The verifier runs in an isolated browser worker using the same memory-safe core as the standalone verifier.

OBCASE / PORTABLE EVIDENCE Drop the case you received or click to choose the sender’s .obcase package No file selected
Recipient policyOptional requirements
Verification policy

Your evidence stays yours. Package bytes and findings remain in this browser. Only the public page assets are fetched.

Nine layers. One unambiguous answer.

A green verdict is earned—not assumed.

A package can be intact and still come from an unauthorized issuer. It can carry a valid signature and still fail custody. Obsign reports each question separately.

01

Package integrity

The manifest and every named member must match byte-for-byte. Missing, extra, or altered evidence is refused.

02

Identity + authority

The signature must verify, then the signer is assessed against the recipient’s trust policy—not its own claims.

03

Custody + source

Preserved source bytes and the canonical working image must remain cryptographically bound to the case.

04

Re-execution

The registered portable operation runs again in your browser. A claimed result that cannot reproduce does not pass.

05

Delivered evidence

The delivered file and its decoded pixels are checked against the signed result—container and content, separately.

06

C2PA + trusted time

Content Credentials and independent time are shown as explicit layers and can be mandatory under your policy.

Designed for the receiving side

The creator does not get the last word.

Verification is free because trust only works when a newsroom, court, client, auditor, or opposing expert can inspect the evidence without buying Obsign or trusting our servers.

Read the evidence package specification

✓ What a pass proves

  • The package is internally intact.
  • The named key signed the bound claim.
  • Custody and normalization bindings hold.
  • The portable computation reproduced.
  • Your selected policy requirements passed.

— What it never pretends

  • That the photographed event happened.
  • That every valid signer is trustworthy.
  • That absence of an AI flag proves reality.
  • That software decides legal admissibility.
  • That cryptography replaces human judgment.

Evidence that can answer back

Start with evidence—or verify the handoff.

The workstation creates the package from an ordinary image. This public verifier lets every recipient challenge it independently.

Create a case Verify a received case