What Invoance is, in plain statements.
Invoance is proof infrastructure. Applications post events, document hashes and AI exchanges to an API. Invoance signs each record with a per-organization Ed25519 key, stores it append-only and exposes verification endpoints. Evidence Rooms, used from the dashboard, delivers documents to named recipients exactly as sent, with a signed log of every open and download.
| Category | Proof infrastructure. Five products are delivered as an API; Evidence Rooms is used from the dashboard. |
|---|---|
| Integration | REST and SDKs for Node.js, Python, Go, Java, Ruby, Rust, .NET, PHP. Evidence Rooms needs no code. |
| Primary output | Signed, append-only records with verification links. For a room, a signed log of every open and download, exportable as an evidence package. |
| Cryptography | SHA-256 over canonical JSON, Ed25519 signatures. Room files are hashed with SHA-256 and encrypted with AES-256-GCM in the browser. |
| Verification | Public proof pages, verify endpoints, offline SDK verifier, and an offline check of a room's evidence package. |
/v1/audit/eventsAudit Logs
Signed activity logs for each of your customers, with a viewer they can open themselves.
/v1/eventsEvent Ledger
An append-only, signed record of the business events you may need to prove later.
/v1/ai/attestationsAI Attestation
The evidence layer for AI agent actions: what an agent was asked, what it decided, and what it did.
/v1/document/anchorDocument Anchoring
Proof that an exact file existed at a given time, without handing the file over.
/v1/tracesTraces
Group events, documents and AI attestations into one sealed record of a whole process.
app.invoance.com · no API neededEvidence Rooms
Capital calls, wire instructions and closing documents, delivered exactly as sent, with signed proof of who opened what.
Capture the fact
Your application sends the event, file hash, AI exchange or workflow item when it happens. For Evidence Rooms the dashboard does this: the sender's browser hashes each file as it is added to a room, with no code on the sender's side.
Sign the record
Invoance canonicalizes and hashes the record, signs it with the organization's Ed25519 key, and appends it to the ledger. A room's file hashes are anchored the same way, and every open and download becomes a signed entry in the room's log.
Use the proof
A customer, auditor or counterparty checks the record through a verification link, an export or the offline verifier. The recipient's device checks each download from a room against the anchored hash, and the room's evidence package can be checked offline.
- One authenticated request from the code path where the action already happens.
- No data migration and no workflow replacement.
- Adopt one record type at a time.
- Idempotency keys make retries safe.
- Evidence Rooms needs no integration. It runs from the dashboard.
curl -X POST https://api.invoance.com/v1/audit/events \
-H "Authorization: Bearer $INVOANCE_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"organization_id": "org_01J8F3KQ2R7VWX9YB4ND6MCZAH",
"action": "member.role.updated",
"occurred_at": "2026-09-22T08:15:31Z",
"actor": { "type": "user", "id": "user_123" },
"targets": [{ "type": "member", "id": "user_481" }]
}'
| A room | One per fund, deal, matter or client, opened from the dashboard. Each file is hashed with SHA-256 and encrypted in the sender's browser before upload, and the hash is anchored in the document ledger. Invoance holds the encrypted files, encrypted file names, locked room keys and each file's hash, and never a key that opens a file. |
|---|---|
| A recipient | Opens their own link, asks for a 6-digit code sent to the inbox the sender named, and downloads. No account. Each file is decrypted on their device and compared with the sender's hash before it is saved. A repeat visit can use a saved passkey, and a room can require one. |
| The signed log | Room created, file added, recipient added, link opened, file downloaded, access refused, access revoked, policy changed. Each entry is signed with the organization's Ed25519 key, numbered without gaps and chained by the hash of the entry before it. |
| The evidence package | Every log entry, every file hash with its ledger anchor, the recipients and the organization's public key, with instructions for checking it offline. |
| Controls | Named recipients only, access start and end per room or per recipient, a country allow list, revoke with optional room key rotation, and a passkey requirement. A refused request is logged, and the recipient is shown no reason. |
| Free room | On Developer and Builder: one room at a time with 100 MB of encrypted storage and up to 10 recipients, at no charge, the full product otherwise. Archiving a room frees the slot. |
| Price | $59 a month, or $49 a month billed annually, as its own plan on Developer and Builder for more than the free room. Unlimited rooms, files and recipients, 3 team seats, 10 GB of encrypted storage; +50 GB storage for $10 a month. Files up to 100 MB each. Enterprise terms on request. |
| Plan inclusion | Included with Growth (10 GB storage), Compliance (50 GB storage) and Enterprise (custom storage). |
What a room shows
- Each file's SHA-256 is anchored in the document ledger before upload, so the instructions you sent are fixed at that moment.
- Each entry in the room log is signed with your organization's Ed25519 key, numbered without gaps and chained by the hash of the entry before it.
- The recipient's download is checked against your fingerprint on their device before it is saved.
- Anyone holding a copy can drop it on the file's public proof page: match or no match, no account needed.
- The evidence package holds every entry, every file hash with its ledger anchor, the recipients and the public key, with instructions for checking it offline.
What a room does not do
- Evidence Rooms do not move money, hold funds or check bank accounts. They make sure the document that arrives is the one you sent, and prove it. Your call-back and approval controls still apply.
- Our claim is that Invoance stores no keys and no readable files, not that reading is impossible. Encryption in the browser relies on the page code we serve.
- Anyone who can open a file can copy it, screenshot it or photograph the screen.
- No previews, watermarks, virus scanning or search on the server, because the server never sees a readable file. Recipients download files; nothing is shown in the browser.
- The email code is as strong as the recipient's inbox. A saved passkey, or a room that requires one, closes that gap.
- Country rules check where the request comes from, which a VPN changes.
- Lost passkeys together with a lost recovery key mean lost files. Setup asks you to store the recovery key offline for that reason.
A proof shows
- A specific record existed in a specific form.
- It was signed by a specific organization at a specific time.
- What you are looking at still matches what was signed.
- A sealed trace has had nothing added, removed or reordered.
A proof does not show
- That the underlying statement is true.
- That a decision was fair, legal or correct.
- That a document's contents are authentic.
- That you meet a legal or regulatory obligation.