Live demo
This is not a video and not a mock-up. The forms below belong to a demo business running on the same engine as every customer. You will read a kayak-rental waiver, answer two questions it asks, agree to sign electronically, sign, and get a copy with its certificate by email. Then you can check that certificate the way a court or an insurer would. When you have, try the two-party agreement: you sign as the renter, then countersign as the manager from your own inbox.
The same five steps a guest at a counter or a renter at home goes through — and what the business sees at each one.
Your name, your email, and the two questions the waiver needs: an emergency contact and their number. Custom fields like these are set per form.
The whole waiver, on the page, before anything is asked. What will be recorded is one tap away.
"I agree — continue" is its own press with its own time. The record can show consent came first.
Type your name. The time, your network address and a fingerprint of the exact text go into the record.
A certificate with a code is emailed to you. Paste it at /verify: anybody can, without an account.
The other side of the same document, in the portal at signsealer.com/app. Real screens, on an example account.


Every document with its signers and their state — sent, consented, signed, declined — so the morning list is a list, not a clipboard.
The emergency contact you typed is on the document and in the evidence, where the guide can find it, not in a spreadsheet nobody opens.
The sealed PDF and the evidence package: text hash, consent and signature times, addresses, the trail, the certificate, every message about it.
The agreement at /f/demo/agreement has two signers: the renter and the manager who countersigns. You play both, and the engine keeps the order it would keep for any customer.
Your name and email, what you are renting, when you will bring it back. Read the agreement, consent, sign. Same as the waiver.
The signed page says the document still needs the manager. The business's list shows one of two signed, not a finished document.
The manager's link is in your inbox, sent the way a fixed signer's always is. Open it early and it says an earlier signer has not signed yet.
Now it is the manager's turn. Read, consent, sign as the manager: the trail records the name with the role, in second position.
Both signatures, in order, on one document. The certificate goes out and verifies; the trail shows who signed first.
A guardian for a minor, a witness, somebody copied: a workflow names each role and the engine orders them the same way. Packets and multi-signer is the guide.
Both links in the agreement go to you. A public form that emailed a signing link to any address a visitor typed would be a way to send mail to strangers, so the demo never does. On a customer's account the manager is a named person, and their link goes to them.
The demo starts from a public form. A customer's PMS or point of sale starts the same document with one API call and hears back on a webhook. Four calls, in the quickstart.
About the demo account. It is a real business account called SignSealer Demo. Its documents expire after a day if unsigned and are redacted after a day if signed — the text and your details go, the fingerprint and the certificate stay, and the certificate still verifies. Your email address is used for the copy and for nothing else.