# Legalesign — E-Signature

Legalesign by Legalesign Ltd holds a panel rating of 2.5/5 from 6 AI judges (category median 2.5/5), as of 2026-11-03. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: Legalesign Ltd (https://legalesign.com)
- Category: [E-Signature](https://whats-best.ai/software/e-signature.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/e-signature/legalesign
- Alternatives: https://whats-best.ai/software/e-signature/legalesign/alternatives ([markdown](https://whats-best.ai/software/e-signature/legalesign/alternatives.md))
- Data as of: 2026-11-04 · evaluated 2026-11-03 · oldest source captured 2026-11-03

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Legalesign Ltd
- Headquarters: Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 3 Nov 2026

## The panel's verdict

Legalesign is an e-signature platform from Legalesign Limited, registered in Scotland, United Kingdom. Its strongest area is signing workflow, scored a uniform 7 for templates with per-participant fields, sequential and simultaneous routing, signer, approver and witness roles, bulk send from a CSV, and account-free signing links. Integration and API follows at 7-8 on REST and GraphQL behind an OpenAPI 3 specification, five Apache-licensed SDKs, webhooks verifiable by public key or HMAC, and a sandbox throttled to 100 API calls per hour. Evidence and retention spans 6-8: long-term validation with external timestamps and an audit log inside the signed PDF draw credit, while the timestamp provider remains unnamed. Identity verification is weak because qualified signing presumes the signer holds a Digidentity credential and open links let anyone sign. Sovereignty is the other weak area: the vendor markets a UK-based platform with ISO 27001, and we found no public information on data residency, a data processing agreement or subprocessors. Pricing transparency scored 1-2 on a 14-day trial with all features and no credit card required.

**Speaks for it:**
- Signing workflow scored a uniform 7, covering templates with per-participant fields, sequential and simultaneous routing, signer, approver and witness roles, and bulk send from a CSV
- Integration and API scored 7-8 for REST and GraphQL behind an OpenAPI 3 specification, five Apache-licensed SDKs, webhooks verifiable by public key or HMAC, and embeddable signing components
- Evidence and retention scored 6-8 for long-term validation, Adobe Reader's Certified mark, an audit log appended inside the signed PDF, and retention configurable up to 99 years per team or per document
- Qualified electronic signatures via Digidentity are documented alongside PAdES and eIDAS advanced signatures, including the rule that signers after a qualified signature are restricted to qualified signing
- Crown Commercial supplier status and published ISO 27001 certification are confirmed on the vendor's pages

**Held against it:**
- Identity verification scored 2-3, as the only pathway described is qualified signing for holders of an existing Digidentity credential, and we found no public information on identification methods, countries or ID documents
- Sovereignty scored 1-2: the contracting entity is a UK one, and we found no public information on where documents, audit trails and signer data are stored, on a data processing agreement, or on subprocessors
- The timestamp behind long-term validation is attributed only to an unnamed external trusted source
- We found no public information on which plans include qualified signing, the countries it covers, or a linked EU Trust List entry for Digidentity
- We found no public information on API access to qualified signatures, production rate limits, or the scope of the named connectors

**Best for:**
- You need to embed document preparation and signing inside your own application, with REST and GraphQL APIs, verifiable webhooks and embeddable components
- Your team sends high volumes of templated agreements — bulk send personalised from a CSV with automatic reminders and recipient roles covers this
- You must keep signed contracts verifiable for years, with long-term validation inside the PDF and retention set per document type up to 99 years
- You are a UK-based buyer for whom a Scotland-registered vendor with Crown Commercial supplier status and ISO 27001 certification fits procurement

**Avoid if:**
- You need signers identified within the platform — the pages describe identification only as holding an existing Digidentity credential, and open links let anyone sign with email confirmation optional
- You must document EU data residency, a published data processing agreement or a subprocessor list for compliance — the contracting entity is a UK one and we found no public information on these
- Your signers complete complex forms on iPhones — the vendor notes these may not work well in embedded mobile contexts and recommends jumping to a browser window

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v2). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Legal Counsel | The HR Operations Lead | The Revenue Operations Lead | The Integration Engineer | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| eIDAS levels & trust services | 2.5/5 | 2.5/5 | 2/5 | 3/5 | 2.5/5 | 3/5 |
| Signer identification | 1/5 | 1/5 | 1/5 | 1.5/5 | 1.5/5 | 1/5 |
| Signing workflow & signer experience | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Evidence, validation & retention | 3.5/5 | 3.5/5 | 3/5 | 4/5 | 3.5/5 | 3.5/5 |
| Integrations & API | 3.5/5 | 4/5 | 3.5/5 | 4/5 | 3.5/5 | 4/5 |
| European sovereignty | 1/5 | 1/5 | 0.5/5 | 1/5 | 1/5 | 1/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **3/5** | **3.5/5** | **2/5** | **2.5/5** |

### The judges

- **The Legal Counsel** (v1.0): Decides which contracts may be signed electronically and at which level. Wants SES, AdES and QES named per plan and country, the qualified trust service provider linked to the EU Trust List, and an audit trail with timestamps that still validates when the contract is disputed in eight years.
- **The HR Operations Lead** (v1.0): Sends two hundred employment contracts a year, many of them fixed-term and so under written form. Wants QES that a new hire can complete on a phone in ten minutes, identification that accepts the IDs applicants actually hold, bulk sending from templates, and a price per qualified signature known before the contract is signed.
- **The Revenue Operations Lead** (v1.0): Measures how long a quote takes to come back signed and where it stalls. Wants signing from inside the CRM, templates sales cannot break, reminders and signing order that run themselves, and a signer experience that needs no account, no app and no explanation.
- **The Integration Engineer** (v1.0): Embeds signing into the company's own portal and archives the result in the DMS. Wants a versioned API with webhooks and a sandbox, every signature level reachable through the API rather than only in the web app, and signed documents exported with their evidence intact.
- **The Data Protection Officer** (v1.0): Knows every signer who holds an ID card up to a camera hands biometric and identity data to a provider they never chose. Asks who performs the identification, where documents and ID data are stored, how long the audit trail keeps IP addresses, and who the subprocessors in the trust service chain are.
- **The Skeptic** (v1.0): Knows "legally binding" usually means a simple signature. Reads for the level the default plan actually signs at, the QTSP the provider does not operate itself, the per-QES and ident fees on top of the plan, the envelope limit, and "eIDAS-compliant" from a provider that names no trust service at all.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Crown commercial supplier: yes [S11]
- ISO 27001: yes [S11]
- ISO 27001: yes [S1]
- Trademark: legalesign [S2]
- UK platform: yes [S11]

**Integrations**
- API: yes · yes · yes · yes [S1]
- Document viewer component: yes [S3]
- Final pdf webhook event: finalPdfCreated · document · yes [S13]
- Graphql: yes [S3]
- Mcp: yes [S1]
- Openapi spec: yes [S3]
- Pdf download endpoint: GET · https://eu-api.legalesign.com/api/v1/pdf/${documentId}/ [S12]
- Postman: yes [S7]
- Power automate example: MS Power Automate generated webhook URLs supported; signed PDFs saved to Sharepoint in demo [S12]
- Rest API: yes [S3]
- Sdk java: Apache-2.0 · yes [S3]
- Sdk php: Apache-2.0 · yes [S3]
- Sdk python: Apache-2.0 · yes [S3]
- Sdk ruby: Apache-2.0 · yes [S3]
- Sdk typescript: Apache-2.0 · yes [S3]
- Webhook admin permission required: yes [S12]
- Webhook events document: created · rejected · finalPdfCreated [S12]
- Webhook events recipient: completed · rejected · emailOpened · visiting · bounced · autoReminderEmail · emailNotification [S12]
- Webhook graphql crud: createWebhook · updateWebhook · deleteWebhook · yes [S12]
- Webhook hmac verification: X-HMAC-SHA256 · yes [S12]
- Webhook logging: yes [S12]
- Webhook manual trigger: yes [S12]
- Webhook method: POST · JSON [S12]
- Webhook recipient roles: signer · approver · witness [S12]
- Webhook repeat events: visiting · bounced · emailNotification · autoReminderEmail [S12]
- Webhook required fields document: tag1 · recipients · groupResourceUri · statusText · name · tag · resourceUri · uuid · tag2 · group · status [S12]
- Webhook schema count: document · recipient [S12]
- Webhook schema expansion: yes [S12]
- Webhook signature verification: X-Signed-SHA256 · yes [S12]
- Webhook tags: 3 [S12]
- Webhook types: realtime_events · all_events_every_6_minutes_legacy · upon_event_legacy [S12]
- Webhooks definition: Webhooks are your URLs where Legalesign will send real-time status updates. [S12]
- Websocket alternative: yes [S12]
- Zapier: yes [S7]

**Legal**
- Address: St John's Innovation Centre, Cowley Road, Cambridge, CB4 0WS [S11]
- Copyright entity: Legalesign Limited [S5]
- Docs URL: https://docs.legalesign.com [S3]
- Entity: Legalesign Limited · Scotland, United Kingdom · SC425013 · 1 George Square, Glasgow, G2 1AL, UK [S2]
- Footer address: St John's Innovation Centre, Cowley Road, Cambridge, CB4 0WS [S2]
- Location: Cambridge, United Kingdom [S3]
- Privacy policy URL: https://legalesign.com/opn/privacy/ [S2]
- Service terms URL: https://legalesign.com/opn/terms/ [S2]

**Pricing**
- Free trial: 14 · no [S11]
- Free trial access: yes · all features [S1]
- No credit card: no [S11]
- Sandbox throttle: 100 [S7]
- Trial: 14 · no [S2]

**Product**
- Ades eidas: yes [S11]
- Age requirement: 18 [S2]
- AI mcp: yes [S7]
- API: yes [S11]
- API key creation: create API key in Developer Portal [S6]
- API key required: API use requires logging into the Developer Portal and creating an API key [S7]
- API sandbox banner: API Test banner shown on signing page in sandbox mode [S6]
- API sandbox throttle: sandbox · 100 [S6]
- Approver role: Approver reviews/approves without a signature field; can be sole participant or part of a larger flow [S9]
- Audit log: yes [S11]
- Batch sending: yes [S11]
- Bulk send: yes [S1]
- Bulk send sender fields: Sender fields work with Bulk Send, personalised per recipient from a CSV [S8]
- Certification validated by adobe reader: yes [S11]
- Certified pdf display: Certified PDF shows a blue horizontal bar at top of document in PDF Reader [S11]
- Core roles: Signer · Approver · Witness [S9]
- Data retention document types: sent & signed documents · email attachments · PDF/Word uploads · text templates [S10]
- Data retention max years: 99 [S10]
- Data retention scope: yes · yes [S10]
- Deletion logging: yes · yes · yes [S10]
- Description: online software service for contract management [S2]
- Digidentity signature types: yes · yes · Digidentity [S5]
- Doc export: Docs articles exportable as PDF or plain text [S9]
- Docs export: PDF · plain text [S5]
- Document lifecycle: Documents have lifecycle: completed, declined, expired [S8]
- Documents sent: 10M+ [S1]
- Editor component: yes [S3]
- Embeddable components: yes [S1]
- Esignatures: yes [S1]
- Ewitnessing: yes [S1]
- Export article: Docs articles can be exported as PDF or plain text [S8]
- Field data deletion: yes · yes [S10]
- Field participant assignment: Every field is assigned to a participant: signer, approver, or sender [S8]
- Final pdf download after signing: yes · yes [S13]
- Forms: yes [S1]
- Iframe device constraints: yes · yes · yes [S13]
- Iframe embedded signing: yes [S13]
- Inbox: Inbox centralised signing queue [S11]
- Legalesign link: yes · yes · yes [S13]
- Let previous recipient decide: Let previous Recipient decide: previous recipient supplies unknown recipient details during workflow [S9]
- Linked recipients: Linked Recipients coordinate behavior within the same document flow [S9]
- Ltv: yes [S11]
- Ltv audit log embedded: yes [S11]
- Ltv external timestamp: external trusted source [S11]
- Ltv verification independence: yes [S11]
- Modules: Web App · API · Forms · Link · Bulk Send [S2]
- Modules: Web App · API · Forms · Link · Bulk Send [S11]
- Participants roles recipients model: Participants are template-level slots reused on every send; each Participant has a Role; a Participant becomes a Recipient when a document is sent [S9]
- Pdf certification: PDF certification freezes the document in time and identifies the responsible party [S11]
- Plugin setup: Ready-to-go plugins exist (e.g. Salesforce, Voyager Infinity); contact support to enable [S7]
- Positioning: AI-ready eSignature Platform, API-first [S1]
- Post qes field styling: basic PDF form fields instead of Legalesign styled format [S4]
- Qes digidentity support: Legalesign supports signing documents with Qualified Electronic Signatures (QES) via Digidentity [S5]
- Qes signing flow: Signer offered QES option after selecting signature fields if valid QES exists [S4]
- Qes signing order restriction: yes · yes [S4]
- Qes video tutorial: video · yes [S5]
- Reassign reject: Recipients may be allowed to reassign a document or reject it, depending on signing experience settings [S9]
- Same day signing: 70 [S1]
- Sandbox banner: yes [S7]
- Self service links: yes [S1]
- Sender field rendering: Sender field values are printed directly onto the PDF [S8]
- Sender fields: Sender fields are filled in by the sender at send time before dispatch [S8]
- Sender role: Sender prepares and dispatches the document; sender fields allow filling values at send time [S9]
- Sequential workflows: Sequential: recipients act one after another in order [S9]
- Signer component recommended: yes · yes · yes [S13]
- Signer role: Signer signs the document [S9]
- Simultaneous workflows: Simultaneous: recipients can act independently at the same time [S9]
- SSO passkeys: yes · yes · yes [S11]
- Status page: yes [S11]
- Template document separation: Template changes after sending do not affect in-progress documents [S8]
- Template prep workflow: Workflow: upload PDF, open Template Preparation page, place fields, configure properties (labels, ordering, validation), ready to send [S8]
- Template reuse: Templates live in the Library, are reusable, and hold PDF, fields, and participant structure [S8]
- Template signature field requirement: Templates require at least one signature field per signer before sending; approver-only templates exempt [S8]
- Tracking: yes [S11]
- Upload rights: material uploaded in relation to the Service is excepted from non-confidential treatment [S2]
- Web app: complete web application for prepare, send, sign, witness, track [S1]
- Webhooks legacy: Docs cover Legacy Webhooks [S7]
- Witness role: Witness is linked to a Signer and confirms signing took place appropriately [S9]
- Workflow automation: yes [S1]
- Workflow types: Single-Recipient · Multi-Recipient · Sequential · Simultaneous [S9]

**Support**
- Production mode: Support ticket · move out of sandbox · add multiple teams · identify dev teams to exclude from future billing [S6]
- Production mode: Support handles sandbox-to-production move, multiple teams, and excluding dev teams from billing [S7]
- Rating: ranked #1 for Enterprise Support [S1]
- Resources: Pricing · Contact Us · App Documentation · API Documentation · Status [S2]
- Ticket channel: support.legalesign.com · ticket [S5]

## Questions

### Is Legalesign European?

Not determined: the vendor’s pages as captured do not say where Legalesign is based.

### Where does Legalesign store data?

Not stated on the vendor’s pages as of 3 Nov 2026.

### Does Legalesign have a free plan?

Not stated on the vendor’s pages as of 3 Nov 2026.

### What are the best alternatives to Legalesign?

As of 3 Nov 2026, the panel rates [sproof sign (3.5/5)](https://whats-best.ai/software/e-signature/sproof-sign), [MOXIS (3.5/5)](https://whats-best.ai/software/e-signature/moxis) and [Signicat Sign (3/5)](https://whats-best.ai/software/e-signature/signicat-sign) highest among the other 22 E-Signature products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [sproof sign](https://whats-best.ai/software/e-signature/sproof-sign) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Legalesign alternatives](https://whats-best.ai/software/e-signature/legalesign/alternatives).

## What this page leaves out

- 14 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 4 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown.

## Sources

- [S1] Vendor page: https://legalesign.com (checked 2026-11-03)
- [S2] Terms of service — found from the homepage: https://legalesign.com/opn/website-terms/ (checked 2026-11-03)
- [S3] Code repository (open-source licence) — found from the homepage: https://github.com/legalesign (checked 2026-11-03)
- [S4] EIDAS levels & trust services — found from sitemap: https://docs.legalesign.com/web-app/how-to/how-to-use-qualified-electronic-signatures (checked 2026-11-03)
- [S5] EIDAS levels & trust services — found from sitemap: https://docs.legalesign.com/web-app/how-to/how-to-use-qualified-electronic-signature-with-digidentity (checked 2026-11-03)
- [S6] Signer identification — found from sitemap: https://docs.legalesign.com/rest-api/how-to/api-verification (checked 2026-11-03)
- [S7] Signer identification — found from sitemap: https://legalesign.com/articles/esignature-api/API-verification/ (checked 2026-11-03)
- [S8] Signing workflow & signer experience — found from sitemap: https://docs.legalesign.com/web-app/explanation/templates-and-fields (checked 2026-11-03)
- [S9] Signing workflow & signer experience — found from sitemap: https://docs.legalesign.com/web-app/explanation/participant-roles-and-workflow-types (checked 2026-11-03)
- [S10] Evidence, validation & retention — found from sitemap: https://docs.legalesign.com/web-app/how-to/gdpr-how-to-set-data-retention (checked 2026-11-03)
- [S11] Evidence, validation & retention — found from sitemap: https://legalesign.com/electronic-signature/features/pdf-certification-with-ltv/ (checked 2026-11-03)
- [S12] Integrations & API — found from sitemap: https://docs.legalesign.com/rest-api/how-to/webhooks (checked 2026-11-03)
- [S13] Integrations & API — found from sitemap: https://docs.legalesign.com/rest-api/how-to/iframe (checked 2026-11-03)

---

Cite as: whats-best.ai, "Legalesign — E-Signature", AI panel analysis, as of 2026-11-04. https://whats-best.ai/software/e-signature/legalesign

Corrections: https://whats-best.ai/correct/1414?target=page