Tamper-evident hash
The finished PDF is hashed with SHA-256 the moment it is sealed, and the digest is stored with the envelope. Change one byte of the file and it no longer matches the record.
Turn a PDF into a signable envelope in minutes. Send secure links and get back a signed, audit-trailed document.
Built for teams like
- Northwind Labs
- aster studio
- Harbor & Vale
- Kestrel
- Meridian Health
- PortsideLogistics
- Foundry Row
- Vantage Realty
Five deliberate steps
Nothing here is a metaphor. This is the path a document actually takes through closeit.fast — from the file you drag onto the dashboard to the sealed PDF that lands back in your inbox.
Upload
Drop in a PDF, PNG or JPG up to 20 MB. Every page renders in the browser at the size it will print.
Tag
Drag signature, initials, date, text and checkbox fields onto the page. Each one belongs to a single recipient and is colour-coded to them.
Send
Every recipient gets their own single-use link by email, in the order you set. No account, no download, nothing to install.
Sign
Signers consent, then draw with a finger or trackpad, or type their name in a script face. A phone behaves exactly like a 27-inch display.
Track
Watch each recipient move from pending to viewed to signed, live. When the last field is filled, closeit.fast seals the PDF and appends the certificate.
Average upload to sent: under two minutes.
Send your first envelopeLook inside
Four screens do the whole job. Swipe the panel, drag it, or pick one — these are the interfaces you and your signers actually touch.
The editor
Drag a field from the palette, drop it on the page, assign it to a recipient. Coordinates are stored relative to the page, so a field lands in the same place on every screen size.
Screen 1 of 4: The editor
Papers people sign
Six of the documents that move through closeit.fast every day. Open any one to see the shape of it — how many pages, how many fields, and who signs before it is done.
Proof, permanently attached
Anyone can email a PDF and hope. The difference between a signature and a claim about a signature is the record standing behind it.
Audit trail
env_9c4f2a7b18de · 2026-08-24- Sent for signature13:41:03 UTC
Dana Reyes
203.0.113.24 · Chrome 128 · macOS
- Opened the envelope13:44:12 UTC
Dana Reyes · signer order 1
203.0.113.24 · Chrome 128 · macOS
- Consented and signed13:46:58 UTC
Dana Reyes · dana@northwind.co
203.0.113.24 · 3 of 3 fields completed
- Opened the envelope13:58:41 UTC
Marcus Lai · signer order 2
198.51.100.7 · Safari 18 · iPhone
- Consented and signed14:04:09 UTC
Marcus Lai · marcus@asterstudio.com
198.51.100.7 · 4 of 4 fields completed
- Sealed and certified14:22:07 UTC
closeit.fast · certificate of completion
Appended as page 5 of 5 · SHA-256 written
SHA-256 of the sealed PDF
7c1f9a2e4b83d05a6e19…b3e7401d
closeit.fast is built around what the ESIGN Act and UETA actually ask for: that the signer intended to sign, that they consented to do business electronically, that the signature is logically associated with the record, and that the record can be reproduced later by everyone entitled to it.
So every envelope ends the same way. Every view, signature, IP address, browser and timestamp is recorded as it happens. Field values are flattened into the page they were placed on. A certificate of completion is appended, and the whole file is hashed with SHA-256 next to the envelope where it cannot be quietly edited.
You do not have to take our word for any of it. Download the PDF, hash it yourself, and compare.
- ESIGN & UETA aligned
- SHA-256 sealed
- Private storage
Complete audit trail
Created, sent, viewed, consented, signed, declined, completed. Each entry is written as the event happens, with the actor, IP address, browser and a UTC timestamp.
Single-use links
Recipients are identified by a unique token rather than a shared password. Void the envelope and every outstanding link stops working on the next request.
Nothing is public
Documents are encrypted with AES-256-GCM before they are stored, and the key is kept apart from the file. Reading one means passing an authenticated route.
Half the price, all of the proof
One plan with everything in it, and two ways to pay for it. No per-signature fees, no envelope caps, and no feature held back for a tier you have to call someone about.
Yearly
Save 50%The same plan at the lowest monthly rate.
Was $12 per month.$6/monthPer user, per month, billed $72 a year.
Start free, upgrade later- Every feature, no envelope limits
- 6 months cheaper than paying monthly
Monthly
Most flexibleThe same plan, paid month to month.
$12/monthPer user, per month. Switch to yearly whenever.
Start free, upgrade later- Every feature, no envelope limits
- Cancel any month, no exit fee
In both plans
- Unlimited envelopes
- Unlimited recipients
- Signature and initials fields
- Text, date and checkbox fields
- Sequential or parallel signing
- Viewer, copy-only recipients
- Certificate of completion
- Tamper-evident audit trail
- SHA-256 sealed final PDF
- Custom subject and message
- Reminders and resend
- Void an envelope any time
Free to start: one envelope a month, forever, with the same audit trail and certificate of completion the paid plan ships. Recipients never need an account, and you can cancel any time — completed documents and their audit trails stay downloadable.
Answered plainly
The six things people ask before they send their first envelope.
In the United States the ESIGN Act and UETA give an electronic signature the same standing as a pen-and-ink one, provided the signer intended to sign, agreed to sign electronically, the signature is associated with the record, and the record can be reproduced later. closeit.fast captures all four: an explicit consent step before any field opens, the signature bound to the exact field and page it was placed on, and a certificate of completion stored with the finished PDF. The same reasoning holds under eIDAS for simple electronic signatures in the EU and UK.
PDF, PNG and JPG, up to 20MB per document. Word, Pages and Google Docs files need to be exported to PDF first — every word processor does this from File, then Export or Download as PDF. Images are wrapped into a single-page PDF before signing, so a scanned form and a native PDF produce exactly the same kind of sealed, certified artefact at the end.
They are asked for a reason, the envelope moves into a declined state, and every outstanding link on that envelope stops working immediately. Nothing is lost: the audit trail keeps who declined, at what moment, from which IP address, and exactly what they wrote. You fix the clause they objected to, upload the revised document and send a fresh envelope — the declined one stays on file as part of the history.
No, and they never will. Each recipient gets a unique single-use link that opens the document straight in their browser — phone, tablet or laptop, no app, no download, no password and no paywall in the middle of signing. Only the person sending documents needs an account, which is also why our per-seat pricing is per sender rather than per signature.
closeit.fast writes an entry the moment each event occurs: envelope created, document uploaded, sent for signature, viewed, consented to electronic signing, signed, declined, completed. Every entry records the actor, their IP address, their user agent and a UTC timestamp, and entries are append-only — there is no edit path, for you or for us. When the final signature lands, the whole trail is rendered into the certificate of completion, appended to the PDF, and the resulting file is hashed with SHA-256.
Finished documents and their certificates stay in your account for as long as it is open, and you can download the sealed PDF at any point. Delete an envelope and the underlying file is removed from storage; the audit record of that deletion remains, because a record you can quietly erase is not a record. Documents are encrypted with AES-256-GCM before they are stored, with the key held apart from the file, and are only ever served through an authenticated route — a stored file on its own cannot be read.