SignWell
Straightforward e-signature service with a free tier, REST API and CLI.
Jobs Sign Edit — adding signer and text fields as form preparation, not editing existing PDF text
Since 2019
Operated by Docsketch, LLC
Where your files are processed
Reported to upload your files
The vendor states that files are uploaded to their servers. We have not independently tested this.
Hosted service: the privacy policy says content uploaded to the service is collected and stored by SignWell, hosted on Amazon Web Services, with signers completing documents in the browser. Sending tracked requests and receiving them are different: recipients do not need an account, and the vendor advertises a separate no-account signing tool, so the account requirement applies to the sender.
What it does
A hosted e-signature service for sending documents out for signature and tracking completion. You upload or template a document, place signature and text fields, set signing order, reminders and conditional rules, and recipients sign in the browser without needing an account. It also offers a REST API, a command-line tool, an MCP connector and white-label embeds so signing can sit inside another product.
Best for: Small and mid-sized teams that want simple, low-cost e-signature plus a developer API, without enterprise contracts.
Worth knowing: The free tier is one sender and three documents a month, and documents live on US infrastructure with no self-hosting or EU residency option. It is purely a signing tool, so anything involving editing, redaction or conversion is out of scope. The free plan's one sender and three documents a month is a web allowance, not an API one: the developer account and the payment-backed API allowance have different conditions, so unlimited paid web requests do not mean unlimited free API requests. The documented REST API and CLI are real capabilities, and the REST API is distinct from the web allowance. US-only infrastructure and the absence of EU residency are recorded against the vendor's own pages rather than inferred from AWS hosting.
Details, and where each comes from
Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.
- Versions covered
- Web · API
- Website
- signwell.com
- Requires an account
- Yes
- Free tier
- Yes
- Watermark on the free tier
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Yes
- Data residency
- United States
- Open source
- No
- Self-hostable
- No
- Licence
- Proprietary
- Redaction
- No redaction feature
- Programmatic access
- HTTP API · Command line
- Last availability check
- Responded in 182 ms 16 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.
What the redaction verdict rests on
From the vendor's own documentation, read 22 September 2026. Not tested by us.
What that does not establish: The vendor’s own site was read on 22 September 2026 and contains no mention of redaction, sanitisation, blackout or whiteout. Absence from a vendor’s own material is not proof that a feature does not exist — it may be undocumented, or on a page the reading did not reach — but for a NEGATIVE claim it is the strongest evidence available, and it is weaker than a positive quote. Recorded as such rather than presented as certainty.
What the vendor says
Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded — not that we tested the behaviour, unless the note says we did.
-
“Legally binding eSignatures trusted by more than 65,000 businesses.”
Checked by us — the source only partly supports this Read 21 September 2026
Partial, and the reason is that the record has drifted rather than that the vendor has contradicted it. The page no longer says 65,000. Its hero paragraph now reads: "Legally binding eSignatures trusted by more than 80,000 businesses." Two things follow, and the distinction matters. As an assertion, the claim is still satisfied — 80,000 is more than 65,000 — so the source has not said otherwise and a refutation would overstate it. As a quotation, it is stale: the index is showing a reader a number the vendor stopped using, and showing a lower one than the vendor now claims. The page's own meta description is vaguer still, saying the platform is "used by tens of thousands of businesses worldwide". This is the second stale quotation this campaign has found, after Nitro PDF Pro, and the first where a social-proof figure has moved — which is exactly the drift the stored source hashes exist to make detectable.
Standing: Re-read and matched once per-response tokens were masked
Check it yourself: the source, the SHA-256, and how we checked
- From
- the raw HTTP response
- SHA-256
- be35e051b28ea8b6fbd8ede80fb5e539c38086889dbf39be2a53b2e3e710b2d6
How we checked: The figure is not in the rendered homepage and not at all in the raw response for "65,000", so the claim was checked against the raw HTML of https://www.signwell.com/, 169299 bytes saved and hashed, by searching for the sentence around it. sourceHash is the SHA-256 of that raw response.
-
“No account required for recipients.”
Checked by us — the source says this Read 22 September 2026
Confirmed verbatim: the sentence appears unaltered in the page's feature copy. The sentence it follows adds the part a reader is actually deciding on — the tool is "mobile-optimized so your clients, contractors, and teammates can sign anywhere" — so the no-account promise is about the signing experience rather than about the sender. For a recipient, not having to create an account to sign a document is a real friction difference and one of the few claims in this tier that a person could check in two minutes by sending themselves a document, which we did not do. Recorded as the vendor's description; no account was created and no control was run.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 8832502d87e9c918d0405c3a33d8c66cb0f8534bcf680ac92eb665b6c5a244f9
How we checked: Re-verified verbatim on 2026-09-22: https://www.signwell.com/ re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-www-signwell-com-281873aa.txt.
Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked — it is not a judgement about anyone.
Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.