Electronic signature software, from upload to sealed PDF.
Signclad covers the whole path: preparing a document, getting it signed on whatever device the recipient has, and handing you back a file that holds up. Here is each part of it.
Electronic signature software has one job that matters: take the document you already have, put it in front of the right people, and give you back something you can still rely on in two years. Everything else is arrangement.
Signclad is built for teams of roughly one to fifty people who send contracts, onboarding packets, and agreements a few times a week, and for the developers who put signing inside their own product. Both get the same API, the same sealed PDFs, and the same audit trail, on every plan including the free one. There is no enterprise-only evidence tier and no feature that exists in a sales deck and nowhere else.
The six areas below are the whole product. Read them in order if you are evaluating, or go straight to the one that matches whatever you are currently stuck on.
-
Send and sign
Upload a PDF, DOCX, image, or HTML file and place signature, initials, date, text, checkbox, dropdown, and attachment fields exactly where they belong. Every field lives in PDF points on a specific page, so what you see in the editor is where the mark lands in the sealed file, at any zoom on any screen. Recipients open a link and finish in one sitting — no account, no app, no plugin, and the signer surface is translated into fifteen languages including right-to-left Arabic.
-
Templates and bulk send
A template holds the file, the named roles, the fields, and the settings, so saying who is signing takes seconds instead of minutes. Publish one as a public link anyone can open to start their own copy, generate hundreds of documents from a CSV that is validated by row and column before anything goes out, or replace the underlying file and let Signclad re-anchor every field and report exactly what moved, scaled, or was orphaned before you commit.
-
Workflows
Most re-sends are avoidable: the wrong person signed first, a section that did not apply got filled in anyway, the licence never got attached. Signing order decides who is invited when, conditional fields hide what does not apply, checkbox groups enforce a minimum and a maximum, and attachment requests stop a document coming back incomplete. Reminders, expiry dates, passcodes, and CC recipients are here too, set on the document rather than explained in a covering email.
-
Audit and compliance
The evidence model written out in full rather than summarised into a badge: a manifest of the exact revision each signer accepted, frozen and hashed the moment the document is sent; a hash-chained event log where changing one row breaks every hash after it; four independently generated and separately hashed artifacts; and a public verification page a counterparty or a court can use without an account. It also states plainly what Signclad does not claim.
-
API and developers
One REST API, versioned by date, idempotent on every write, and the same one the app and the embedded builders call — there is no private tier. Body-signed webhooks carry health states, a full delivery log, and one-click replay. List and search are cursor-paginated and filterable. Sandbox keys never bill, test mode is unlimited, and the OpenAPI document the reference and the MCP tool schemas are generated from is the contract.
-
Integrations
What connects today — the REST API, webhooks, embedded signing and builders, and the MCP server in developer preview — and what is planned, labelled as planned. Nothing appears on that page because a competitor lists it, and there is no private endpoint that only our own connectors can call. Until a connector ships, the same job is done with one authenticated POST and a webhook subscription.
If you are comparing tools, the two pages that will tell you most are audit and compliance, which shows what you actually get back when the last signature lands, and pricing, which is charged per sender rather than per envelope. If you are integrating rather than evaluating, start at getting started and keep the API reference open beside it.
Send your first document today.
The free plan covers three documents a month, with the same sealed PDFs and audit trails as every paid plan. No card required.