ProjectEnvelope is a neutral sharing and proof layer.

Use it to package project material, stamp important files with a Company Mark, share clean protected links, and let recipients verify later that they are looking at the same file or page.

Plain English

What it is

ProjectEnvelope is for sharing important work without exposing the original studio, newsroom, client, or internal system. It gives each item a neutral link and, when needed, a Company Mark stamp that proves the exact file fingerprint was recorded by that company.

The file can be a PDF, image, video, document, spreadsheet, HTML page, ZIP, CAD file, BIM export, dataset, or normal shared file. ProjectEnvelope does not need to understand the format. It verifies the bytes.

Create project

Start with a project record: title, summary, client reference, status, tags, timeline, thumbnail, and private notes.

Add material

Attach files, images, documents, CAD exports, notes, articles, brochures, pasted HTML, generated HTML, or other shared files.

Stamp proof

Use your Company Mark to stamp important material so the exact same file or page can be checked later.

Share link

Publish a neutral ProjectEnvelope link with optional passcode, expiry, availability window, max opens, and recipient notes.

Verify later

Anyone can check the same file against ProjectEnvelope and see whether it matches an active Company Mark stamp.

How it is used

Hosted app and external workflows

Inside ProjectEnvelope

Create a project, add material, draft notes or HTML with AI when useful, stamp the important items, then publish neutral links for clients, readers, auditors, or reviewers.

Outside ProjectEnvelope

The same Company Mark proof can extend to browser extensions, CLI tools, CMS plugins, Word, Acrobat, CAD, media, and publishing workflows so files can be stamped before they are uploaded, sent, or published.

Who it is for

Teams that need source integrity

Studios and agencies

Share pitch material, proofs, brochures, images, project packs, and client review pages through neutral links.

Newsrooms and publishers

Stamp final images, PDFs, articles, videos, and evidence packs before publication.

Legal and compliance teams

Stamp bundles, disclosures, reports, statements, and issued documents so later copies can be checked.

Architecture and engineering teams

Stamp issued drawings, CAD files, BIM exports, planning packs, tender documents, and client approval files.

Investigators and researchers

Stamp source captures, datasets, archives, notes, and evidence exports without needing to upload the original file.

Trust boundary

What verification means

What it proves

The file fingerprint matches a stamp made by a named Company Mark at a recorded time.

What it does not prove

ProjectEnvelope does not decide whether the contents are true, complete, legal, or editorially accurate.

Why changes matter

If one word, pixel, metadata field, or byte changes, the fingerprint changes and the old stamp will not verify that modified file.