Proof infrastructure for records that get questioned.
Invoance builds an API that signs, stores and verifies events, documents, AI outputs and audit logs. When a customer, auditor or regulator asks what happened, they check the record themselves, without trusting the company that kept it.
Audit logs, event ledger, AI attestation, document anchoring and traces.
Node, Python, Go, Java, Ruby, Rust, .NET and PHP, plus plain REST.
Every record an organization sends is signed with its own Ed25519 key.
A customer, auditor or regulator checks a record from a link.
Audit Logs
Signed activity logs for each of your customers, with a viewer they can open themselves.
POST /v1/audit/eventsEvent Ledger
An append-only, signed record of the business events you may need to prove later.
POST /v1/eventsAI Attestation
A signed record of what a model was asked, what it answered, and which model it was.
POST /v1/ai/attestationsDocument Anchoring
Proof that an exact file existed at a given time, without handing the file over.
POST /v1/document/anchorTraces
Group events, documents and AI attestations into one sealed record of a whole process.
POST /v1/tracesA database row is not evidence.
Every company keeps records of what it did: approvals, invoices, AI answers, access changes. When someone outside the company asks for proof, those records are only as believable as the company's word, because whoever runs the database can change it. Invoance closes that gap. Records are signed when they are written, kept in a ledger that refuses deletes, and checked by anyone against a published public key.
| Question | Application logs | Database rows | Invoance record |
|---|---|---|---|
| Can be edited after the fact | Yes, by anyone with write access | Yes, by an admin | No. Deletes are blocked, and any change breaks the signature |
| Carries a signature | No | No | Ed25519, per organization |
| A third party can check it | Only by trusting your export | Only by trusting your export | Yes, with a link or offline |
| Shows nothing was removed | No | No | Gap-free sequence numbers and sealed traces |
| Checkable without the vendor | No | No | Yes, against the published public key |
A customer disputes an action
You send a verification link for the signed event instead of a screenshot of your admin panel.
An auditor samples your controls
You export the sealed trace. They verify it without access to your systems.
An AI answer is challenged
You show the attested input, output and model version from the time it was generated.
A buyer asks for audit logs
You give them a portal where every event is numbered and signed.
Verifiable without us
Signatures check against the organization's published public key with any Ed25519 library. A record you hold stays checkable even if we are offline.
How verification worksClaims we can back
The security page describes the controls that exist today, in plain terms, along with the limits of what a proof can tell you.
SecurityStatus in the open
Availability and incident history are published for anyone to see, not reported on request.
System statusYour records stay yours
We do not sell your data, share it with other customers or use it to train models.
Privacy notice
| Legal name | Invoance, Inc. |
|---|---|
| Incorporation | A Delaware corporation |
| Contact | Contact form |
| Security questions | Security overview |
| Partners | Partner program |
| Legal | Legal notice |
Talk to us.
Questions about an integration, a security review or a partnership come straight to the team that builds Invoance.