Anyone can collect a signature.Thorium can prove it.

Every event on a document goes into an audit trail where each entry is hashed with the one before it. Change, reorder or delete an entry and the chain shows it.

Signers don’t need an account. Nor does anyone checking the result.

THO-0042/Mutual NDA

All 5 entries verify

  1. 09:12:40John Guy · Document uploaded
    82.14.209.6a91c…4f2e
  2. 09:14:02John Guy · Sent for signature
    82.14.209.67d30…b8a1
  3. 09:31:55Harry Campbell · Opened by a recipient
    104.28.61.19e55f…0c94
  4. 09:41:02Harry Campbell · Recipient signed
    104.28.61.193b17…d6aa
  5. 09:41:03Thorium · Completed and sealed
    serverc20e…71f9

Each digest covers its entry and the one before.

How it works

From a PDF to a sealed copy in four steps, with nothing to set up first.

  1. 1

    Upload

    Drop in a PDF. Thorium takes a SHA-256 hash of the file and reads every object in it, compressed or not, before storing anything. Files carrying script, launch actions, embedded files or forms that post elsewhere are refused, and so are files built to balloon when opened.

  2. 2

    Place the fields

    Drag signature, initials, date, text, number, checkbox, dropdown and radio fields onto the page, and set who signs in what order. Anyone copied in gets the result without owning a field.

  3. 3

    Send

    Each recipient gets their own expiring link, scoped to them and this document. Send to one person at a time, or everyone at once.

  4. 4

    Seal

    When the last signature lands, the signed copy is sealed, timestamped by an authority that isn’t Thorium, and sent to everyone with a certificate of completion.

Four ways to sign, one record

Most signatures are someone clicking a link. The ones that hold deals up are the rest: the person across the desk, the counterparty who won’t sign in a browser, the document that can’t go out with the code in the same email.

The ordinary way.

Each recipient gets their own expiring link, scoped to them and to this one document. No account, no password, nothing to install.

What it adds to the trail

  1. 09:31:55Harry Campbell · Opened by a recipient
  2. 09:41:02Harry Campbell · Recipient signed

Some people are going to want a pen.

Usually that means the document leaves the system: printed, signed, scanned and emailed back as an attachment nobody can check. Thorium keeps it inside. The pack it prints is laid out so a photo of a signed page is evidence, and the ink joins the same chain as every click.

Harry CampbellHarry CampbellSignature — Harry CampbellTHO-0042 · page 3 of 4 · rev 0 · 75476fb2edfaSigned on paper — photograph every page to return it
Page 3 of 4 from a printed pack. The strip is a real page code.
  1. 1

    Registration marks

    Four squares the camera locks onto to straighten the photo. The top-left one is hollow, so a page held upside down is turned rather than read backwards.

  2. 2

    Page code

    Page number, page count and a fingerprint of this document at this revision, with parity bits so a smudge shows up instead of misreading.

  3. 3

    Ruled line

    Printed wherever the paper signer has a field. Their ink is cut from the photo and put back on this field.

  4. 4

    Already signed

    Harry signed electronically before the pack was printed, so the paper carries his signature too.

Coming back in

Photograph every page
The camera finds the marks, straightens the photo and reads the page code. It then knows exactly where each signature box was.
Read again on the server
What the phone saw only guides the person holding it. Every photo is re-read on the server, and that reading decides what goes on the record.
Confirm the original is held
A photo proves what was on a page, not that anyone has the page. The signature counts once a member confirms the original is in hand, and they’re named on the record.

Refused on sight

  • A page from a different document
  • A page from an earlier revision
  • A set with a page missing
  • A signature box with no ink in it
  • A photo too skewed to straighten
  • A page with a corner mark out of shot

Deeds, witnessed in the room

A deed signed by an individual has to be signed in the presence of a witness who attests it. HM Land Registry’s guidance on electronic signatures is explicit that the witness is physically present. Thorium treats each requirement as a stage the document has to pass, not a box somebody ticks.

How Thorium handles each stage of a deed
StageWhat Thorium does
Before signingEvery signatory enters a one-time code sent to their phone before they can make a mark.
WitnessingThe witness signs in the same session, on the same device, straight after the person they watched. They’re never emailed a link, and the session won’t open on anyone else’s device.
AttestationThe witness gives their home address and confirms a statement shown to them in full.
Cross-checkTime, device, network and, if shared, location are compared between the signature and the attestation. A witness “present” from another city shows as a contradiction on the certificate.
DatingA deed takes effect on delivery, so dating it is a deliberate step by the conveyancer, not something that happens when the last signature lands.
CertificateThe certificate has its own attestation section: who witnessed, their address, what they confirmed, and when.

What the witness confirms, word for word

“I confirm I was physically present and observed Harry Campbell sign this document.”

Remote and video witnessing don’t satisfy the requirement, so Thorium won’t email a witness a link and call the result a witnessed deed.

No system can prove two people were in the same room, and this one doesn’t claim to. What it can do is make a false attestation deliberate rather than casual, and visible afterwards.

Settle the wording on the document

Most of the time between drafting and signing goes on arguing about a clause by email, where nobody can tell which version anyone is looking at. Put the argument on the document instead.

THO-0042/Mutual NDA, draft 22 open

4.1This agreement starts on the date it is signed by the last party and continues until either party ends it under clause 4.2.

4.2Either party may end this agreement by giving thirty sixty days’ notice in writing to the other.

4.3Clauses 5 and 6 survive the end of this agreement for five years.

Live
Open the same document as a colleague and their comments appear as they write them.
Accepted by someone else
A proposed change has to be accepted by somebody other than whoever proposed it.
Kept apart from the evidence
Comments get edited and withdrawn, so they’re stored apart from the hash chain. The next draft marks what was carried into it. Nothing is deleted.

Decide what happens after you send it

Sending a document means handing it to someone. These set how long they have it, how often they can open it, what they agree to first, and what’s recorded if they try to take a copy. All optional, and all but the last are set per document.

COMMERCIAL IN CONFIDENCE
Try a marking. 14 are built in, or template your own.
One-time codes
A code emailed or texted to the recipient before it opens, so a forwarded link opens nothing. Or a code you give them yourself, or a passkey.
Your network only
Limit a document to your office or VPN addresses. Anyone elsewhere is refused, and the refusal is recorded.
Handling conditions
Terms they accept before the first page renders, recorded with their name and the time.
Access window
When the link opens and when it closes. Outside it the document doesn’t render, and the refusal is recorded.
Open limit
How many times each recipient can open it. Forwarding the link doesn’t buy anyone more views.
Watermark
Their name and email across every page, so any copy that leaves says who it was given to.
Copy and print
Selection, copying and right-click are blocked, and printing produces a notice instead of the document. Attempts are recorded.
Screen capture
Common capture shortcuts obscure the page and are recorded. This one is best effort: OS tools, browser extensions and phone cameras aren’t caught.
Adaptive checks
Turn it on for the workspace and a session that looks wrong, such as failed codes, a link passed between networks or a sudden handover, gets an emailed code before it can sign. The rarest cases pause for a person to look. A keyboard, language or location never counts against anyone on its own.

Always on: PDFs are only served through short-lived signed links, the signing page can’t be framed by another site, and signing and sign-in are rate limited.

When something changes while it’s out

The address was wrong. The signatory left. It’s been sitting there eleven days. None of that should mean voiding it and starting again, and none of it should happen off the record.

Correct it

Fix a wrong address, a misplaced field or the deadline without starting again. Recipients get a fresh link and the old one stops working.

Reassign or delegate

Send it to the right person yourself, or let the recipient pass it on from the signing page. Either way it’s recorded as a hand-off.

Chase it

Reminders daily, every two days or weekly. A sweep chases what’s outstanding and expires what has run out of time.

Send to many

Up to 200 recipients from one document, each with their own copy and link. The run resumes where it stopped.

Keep who you send to

Contacts and templates keep the people, fields and roles, so the second document is quicker than the first.

Withdraw it

Revoke one person, or withdraw the whole document with a reason. Copies already open close within seconds, a restored recipient gets a fresh link, and it’s all on the record.

A record that answers back

The trail is append-only. Status is worked out from what signers have actually done rather than set by hand, so the badge, the progress bar and the record can’t disagree.

38 kinds of event
From upload to seal, each with the time, who did it, their device and their IP address.
Refusals too
A wrong code, a closed window, a spent view. What was stopped is on the record as well as what went through.
Deletions show
Removing an entry leaves a gap the next one can’t bridge, so a quiet trim is as visible as an edit.
Signed checkpoints
Every trail is regularly signed with a key the database never holds and timestamped by an outside authority. Even someone with full access to the data can’t rewrite history and recompute the hashes without it showing. Anyone in the workspace can check.
Redaction isn’t tampering
IP and device details can be removed after your retention period. Those entries report as redacted, never as altered.
Security signals stay apart
How risky a session looked is a judgement, not evidence. It’s kept apart from the trail, shown only to admins, and deleted on a schedule you set.

Somebody sent you a Thorium trail or a signed PDF?

Check it without an account, and without us. The file is read in your browser and never uploaded, so the answer doesn’t depend on trusting Thorium.

Verify a document

What these signatures are, and what they aren’t

Signatures collected in Thorium are simple electronic signatures under eIDAS Article 3(10), backed by the identity checks recorded against each one and by the trail. With a sealing certificate configured, the signed copy is sealed to PAdES. Add a time-stamping authority and it reaches PAdES-B-LTA, carrying what a verifier needs inside the file so the seal can still be checked after its certificate expires.

That seal is the platform’s, not the signatory’s. Thorium doesn’t issue advanced or qualified signatures itself. Connect a provider that does and Thorium sends it only the document’s hash, and the level of the resulting signature is whatever that provider declares, not a setting here.

Your systems hear about it first

Pick which of the 36 events each endpoint receives. Every delivery is signed with that endpoint’s own secret and timestamped, so your receiver can tell a real one from a replay, and each event keeps the same id on every retry, so it’s acted on once. Rotate the secret without changing the URL.

Deliver as Thorium JSON, Discord, Slack, Zapier, Salesforce, HubSpot, Splunk or Datadog. Splunk and Datadog also get the address and device behind each event, for your security team; nothing else does.

REST API

Issue a key per integration with only the permissions it needs. Keys expire, can be tied to your network, and are rotated or revoked from Settings.

  • GET/api/v1/documents
  • POST/api/v1/documents
  • GET/api/v1/documents/{id}
  • POST/api/v1/documents/{id}/send
  • POST/api/v1/documents/{id}/execute
  • GET/api/v1/documents/{id}/file
  • GET/api/v1/documents/{id}/audit
  • DELETE/api/v1/documents/{id}
Delivery200
POST /hooks/thorium
x-thorium-id:        evt_act_7d1e93b0
x-thorium-event:     document.completed
x-thorium-timestamp: 1789378862
x-thorium-signature: sha256=4f2e…b8a1

{
  "id": "evt_act_7d1e93b0",
  "event": "document.completed",
  "at": "2026-09-14T09:41:02.000Z",
  "workspaceId": "ws_4c81",
  "document": {
    "id": "doc_8f2a41c7",
    "reference": "THO-0042",
    "name": "Mutual NDA",
    "status": "completed"
  },
  "actor": { "name": "Harry Campbell", "kind": "signer" }
}

Pricing

One plan. There’s no tier that withholds the evidence.

...per sender, per month

Unlimited documents, templates and contacts. Paper signing, deeds, one-time codes, adaptive checks, reminders, bulk sending, webhooks, the API, signed checkpoints and the full audit trail are all included. Recipients never pay and never need an account.

Create your workspaceNo card needed to start.