E-Signature
Adobe Acrobat Sign
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Adobe Inc. · www.adobe.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Adobe Acrobat Sign at a glance
- Vendor
- Adobe Inc.
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Yes, per the vendor’s own page source, captured 13 Oct 2026
- Panel verdict
- The AI panel rates Adobe Acrobat Sign 1.5/5, the mean of 6 judges. Adobe Acrobat Sign, judged on captured developer pages, reads as a developer-integration product: integration and API is its strongest criterion, clustering at 5 to 6 on documented REST and webhook APIs, OAuth scopes, SDKs for Node.js, Java,.Net and Python, an OEM/Embedded partner track, and a PDF Electronic Seal API naming trust service providers Intesi Group, Entrust, GlobalSign and TrustPro plus qualified timestamp authorities. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Adobe Acrobat Sign, judged on captured developer pages, reads as a developer-integration product: integration and API is its strongest criterion, clustering at 5 to 6 on documented REST and webhook APIs, OAuth scopes, SDKs for Node.js, Java,.Net and Python, an OEM/Embedded partner track, and a PDF Electronic Seal API naming trust service providers Intesi Group, Entrust, GlobalSign and TrustPro plus qualified timestamp authorities. It is weakest on identity verification and pricing transparency, both scoring 0: we found no public information on how signers are identified, or on any price. Signature levels score 2 to 4 because qualified services are evidenced for seals only and never labelled for signer signatures. Signing workflow spans 2 to 4 — the HR operator credits account-free signing on any device, while others found no public information on templates, signing order, reminders or bulk sending. Sovereignty sits at a flat 3: no sovereignty attributes are on record, EU customers contract with Adobe Systems Software Ireland Limited under parent Adobe Inc. of San Jose, and we found no public information on data locations or subprocessors.
Speaks for it
- Integration and API scores cluster at 5 to 6, on documented REST and webhook APIs with OAuth scopes, pagination and SDKs for Node.js, Java,.Net and Python
- The PDF Electronic Seal API names its trust service providers — Intesi Group, Entrust, GlobalSign, TrustPro — and RFC 3161 timestamp authorities including qualified ones
- Recipients sign on any desktop or device with a click, tap or swipe, with no downloads or accounts required
- Sealed documents get tamper detection and verification in Adobe Acrobat, carrying evidence and retention scores of 3 to 4
- An OEM/Embedded partner track offers private APIs for building signing into your own application or platform
Held against it
- Identity verification scored 0, with no public information on how signers are identified or authenticated
- Qualified trust services are evidenced only for the seal API, with no signature level labelled for signers on any plan or country
- The documented signing flow is send, sign, track and store, with no public information on templates, signing order, reminders, bulk sending or delegation
- We found no public information on audit trail contents, retention periods or long-term validation of signed documents and their evidence
- No sovereignty attributes are on record, and we found no public information on data locations, subprocessors, or certifications beyond a referenced security overview document
Best for
- You are a development team embedding e-signature or PDF sealing into your own application, website or platform via API
- You need to seal high-volume official documents such as invoices and statements with organization certificates and named qualified timestamps
- You want signers to complete documents quickly on any device without downloads or accounts
- You need a document pipeline that converts files to PDF, runs OCR to make text searchable, and archives the results
Avoid if
- You must prove who signed, through identification methods such as codes, eID or video ident — the only signer-facing statement in the captured pages is click, tap or swipe signing with no downloads or accounts
- You need signer signatures at a defined level — simple, advanced or qualified — tied to plans and countries; qualified trust services are evidenced for the seal API only
- Your procurement requires sovereignty attributes on record, such as data locations or a subprocessor list, before signer and document data move
The scores
| Criterion | Panel median |
|---|---|
| eIDAS levels & trust services | 1.5 of 5 |
| Signer identification | 0 of 5 |
| Signing workflow & signer experience | 1 of 5 |
| Evidence, validation & retention | 2 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 1.5 of 5 |
eIDAS levels & trust services
Show reasoningHide reasoning
How this is scored
Which signature levels the platform offers — simple, advanced, qualified, and qualified seals — through which qualified trust service provider on the EU Trust List, for which countries and legal regimes (eIDAS, ZertES), and on which plans.
0 — No signature level named; the platform calls its signature "legally binding" without saying which kind it is.
3 — Simple signatures by default with "advanced" or "qualified" mentioned as available, but no trust service provider named and no statement on which plan or country offers which level.
5 — SES, AdES and QES offered and labelled in the product, the qualified trust service provider named, and which documents need which level explained for at least Germany or the EU.
8 — Every level documented with the plans and countries it is available in, the QTSP's entry on the EU Trust List linked, QES under eIDAS (and ZertES where relevant) stated, qualified electronic seals for company documents, and the signature level printed in the signed document and audit trail.
10 — Levels are an explicit product decision: the provider is or contracts a named QTSP with its conformity assessment published, level selection per document type or template, remote QES without a separate account, EUDI wallet support stated with a date, and the legal effect per level documented for the main EU markets.
The Legal Counsel
The developer pages name trust service providers and qualified timestamp authorities — including InfoCert Qualified TSA and Namirial Qualified TSA — for the electronic seal API, which is more than a bare "legally binding" claim. But no signature level for signers, whether simple, advanced or qualified, is labelled anywhere, no link to the EU Trust List appears, and nothing states which plan or country delivers which level, so I cannot map a class of contract to a valid signature level. 1 2 6
The HR Operations Lead
The captured pages name trust service providers and qualified timestamp authorities, but only for the PDF electronic seal API, not for the signatures my new hires actually make; we found no public information on which signature levels — simple, advanced or qualified — are offered to signers, on which plans, or for which countries, only a broad claim of e-signature law compliance across the United States, Europe and other nations. 1 2 6
The Revenue Operations Lead
The captured developer pages name trust service providers and qualified timestamp authorities for the electronic seal API, but they never label a signer's signature as simple, advanced or qualified, nor say which plan or country offers which level. The only statement is a promise of help meeting e-signature laws in "the United States, Europe, Japan, Australia and virtually every other industrialized nation", which tells me nothing about whether a German deal needs a qualified signature. 1 2 6
The Integration Engineer
The electronic seal API is explicit about its providers and timestamps, naming Intesi Group, Entrust, GlobalSign and TrustPro plus qualified timestamp services under RFC 3161, which is genuinely useful for company documents. I found no public information on signer signature levels, though: no simple, advanced or qualified signature is labelled, nothing ties a level to a plan or country, and no EU Trust List entry is linked. 1 2
The Data Protection Officer
The captured pages document a cloud electronic-seal API with named trust service providers and named qualified timestamp authorities, so "qualified" appears — but for seals only, and we found no public information on which signature levels the signing product offers, through which qualified provider on the EU Trust List, in which countries or on which plans. A German or Swiss buyer cannot tell from these pages which of their documents require a level that is nowhere evidenced. 1 2 6
The Skeptic
The captured developer pages never label a signature level for the signing product — no simple, advanced or qualified tier, no plan or country mapping — and the compliance pitch rests on a generic claim of e-signature law compliance in the US, Europe, Japan and elsewhere. The only qualified trust services in evidence are timestamps and a separate PDF sealing API routed through named third parties such as Intesi Group and TrustPro, with no EU Trust List entry shown. 1 6
Signer identification
Show reasoningHide reasoning
How this is scored
How the signer is identified for each level: email and SMS codes, video ident, eID card (Online-Ausweis), bank ident or EUDI wallet — who performs it, in which countries it works, and what happens to the ID data afterwards.
0 — Email link only; no statement on how signers are authenticated.
3 — Email plus SMS or access code, with "ID verification" mentioned as an add-on but no methods, provider or countries named.
5 — Identification methods for AdES and QES listed by name (for example video ident, eID, bank ident), the identification provider named, and the countries or ID documents they accept stated.
8 — Methods documented per level and country, automated and agent-based ident distinguished, reuse of an identification for later signatures explained, retention and deletion of ID data stated, and the ident provider listed as subprocessor.
10 — Identification is transparent end to end: every method with its countries, assurance level and failure rate or completion guidance, EUDI wallet and national eID supported, ID data minimisation and retention committed, and the signer-facing privacy notice published.
The Legal Counsel
The captured pages tell me only that recipients sign with "a click, tap, or swipe" with no downloads or accounts required; beyond that we found no public information on how signers are authenticated — no code-based methods, no identification provider, no countries or ID documents, and nothing on what happens to identification data afterwards. 6
The HR Operations Lead
We found no public information on how signers are identified — no email or SMS codes, no video or bank identification, no eID or wallet support, and nothing on what happens to ID data afterwards; for qualified-signature employment contracts that silence settles the score at the bottom. 6
The Revenue Operations Lead
The only signer-facing statement is that recipients sign "with a click, tap, or swipe (no downloads or accounts required)" — exactly the frictionless experience I want for turnaround, but it says nothing about proving who signed. We found no public information on authentication methods, identification providers, countries or what happens to ID data. 6
The Integration Engineer
I found no public information on how signers are identified or authenticated — no email or SMS codes, video ident, eID or wallet method, no identification provider and no country coverage. The only authentication described anywhere in the captured pages is OAuth for API integrations, which authenticates my application, not my signers. 5 6
The Data Protection Officer
We found no public information on how signers are identified: no email, SMS or access-code authentication, no video ident, eID, bank ident or wallet, no identification provider, accepted countries or ID-data handling. The single statement about recipients is that they sign with no downloads or accounts, which tells me nothing about who verified them or where their data went. 6
The Skeptic
We found no public information on how signers are identified or authenticated for any level — no email or SMS codes, no video or bank ident, no eID, no provider, no countries, nothing on retention of ID data. The only signer-facing statement is that recipients sign on any desktop or device without downloads or accounts. 6
Signing workflow & signer experience
Show reasoningHide reasoning
How this is scored
Getting a document out and back signed: templates and form fields, signing order and roles, bulk sending, reminders and delegation, signing without an account or app, mobile signing, and accessibility for signers.
0 — Single-recipient signing of an uploaded PDF; no templates, order or reminders.
3 — Multiple signers and basic templates, but no signing order, no bulk send, and signers must create an account.
5 — Templates with field placement, sequential and parallel signing order, automatic reminders and expiry, signing without an account on mobile, and a status overview for the sender.
8 — Roles and conditional fields, bulk sending, delegation and substitute signers, team and approval workflows, branded signer experience, signer languages listed, and signer accessibility addressed.
10 — The workflow is complete and documented: web forms and self-service signing links, mixed signature levels within one process, in-person and remote signing, a published accessibility conformance statement, and team administration with shared templates and audit of sender actions.
The Legal Counsel
Sending a document out for signature, tracking its status and signing on any device without an account are described. We found no public information on templates, field placement, signing order, reminders, bulk sending or delegation, so the mechanics of a multi-party contract process are unevidenced. 6
The HR Operations Lead
Recipients can sign on any desktop or device with a click, tap or swipe without downloads or an account, and senders track document status, which serves my phone-in-ten-minutes goal; but we found no public information on templates, signing order, bulk sending or reminders — the exact features two hundred contracts a year depend on. 6
The Revenue Operations Lead
The send–sign–track loop is there and signers need no account or app, on any device, with document status tracking and secure storage — the core of fast quote turnaround. But we found no public information on templates, signing order, automatic reminders, bulk sending or delegation, which are the automations that stop deals stalling in someone's inbox. 6
The Integration Engineer
The documented flow is send a document, let recipients sign on any device without an account, track status and store the result. I found no public information on templates and field placement, signing order, reminders, bulk sending or delegation, so this reads as a bare send-and-sign loop rather than a workflow I could configure. 6
The Data Protection Officer
Sending a document out for e-signature, account-free signing on any desktop or device, status tracking and secure storage of approved documents are described; we found no public information on templates and field placement, signing order, bulk sending, reminders or delegation. That is the outbound envelope and nothing more in the captured pages. 6
The Skeptic
The documented story is sending a document out for signature, account-free signing on any device, tracking status and storing the approved document — that is the whole of it. We found no public information on templates and field placement, signing order, bulk sending, reminders, delegation or signer accessibility in the captured material. 6
Evidence, validation & retention
Show reasoningHide reasoning
How this is scored
What proves a signature years later: the audit trail and certificate of completion, qualified timestamps, long-term validation (PAdES-LTV), validation reports, and how long signed documents and evidence are kept — and whether they can leave the platform.
0 — A signed PDF and nothing else; no audit trail, no statement on storage or deletion.
3 — An audit trail or completion certificate exists, but its contents, the timestamp source and the retention period are unstated.
5 — Audit trail with signer events, IP addresses and authentication method embedded in or attached to the signed PDF, timestamps applied, documents downloadable, and the retention period stated.
8 — PAdES signatures with long-term validation, qualified timestamps from a named provider, a validation tool or report, configurable retention and automatic deletion, and bulk export of documents with their evidence.
10 — Evidence outlives the subscription: LTV and archive timestamps documented, validation verifiable with independent tools such as the EU DSS validator, export to a DMS or archive with evidence intact, and post-termination access and deletion committed in the terms.
The Legal Counsel
Timestamps follow RFC 3161 and their providers are named, including Adobe Qualified Timestamp and two qualified TSAs, with tamper detection on sealed documents. But we found no public information on the contents of an audit trail, on long-term validation such as PAdES, or on any retention period — whether the evidence still validates when a contract is disputed in eight years is unanswered. 1 2 6
The HR Operations Lead
Named RFC3161 timestamp authorities including qualified ones, tamper detection for sealed documents, and secure storage of approved documents are shown, but we found no public information on the audit trail's contents, the retention period for signed contracts, or long-term validation that would prove a fixed-term agreement years later. 1 2 6
The Revenue Operations Lead
Timestamp sources are named and credible — Adobe Qualified Timestamp, InfoCert and Namirial qualified TSAs under RFC 3161 — with tamper detection and e-seal verification in Acrobat plus an archiving use case. But we found no public information on audit trail contents, long-term validation, or how long signed documents and evidence are kept, and for a contract that must still hold up years later that silence is a problem. 1 2 3 6
The Integration Engineer
Qualified RFC 3161 timestamps from named providers, tamper detection and verification in Acrobat are real evidence primitives, and an archiving-and-retrieval use case exists for the PDF pipeline. But I found no public information on audit trail contents, retention periods, long-term validation, or exporting signed documents with their evidence intact — which is precisely what my DMS archive depends on. 1 2 3
The Data Protection Officer
RFC 3161 timestamps from named authorities — including qualified ones — plus tamper detection and seal verification in Acrobat are documented, but we found no public information on audit trail contents, IP or authentication evidence, retention periods, long-term validation, or export of documents together with their evidence. I cannot advise a records officer on what will still prove these signatures seven years from now. 1 2
The Skeptic
Timestamps come from named providers including Adobe Qualified Timestamp, InfoCert Qualified TSA and Namirial Qualified TSA, tampering after sealing is detectable, and the seal can be verified in Adobe Acrobat — that part is real, though it belongs to the sealing API. We found no public information on the audit trail's contents, long-term validation, or any retention period, and "securely store approved documents" is the entirety of the storage statement. 1 2 3 6
Integrations & API
Show reasoningHide reasoning
How this is scored
Signing from inside the systems where contracts are made: a documented API with webhooks and a sandbox, embedded signing, and connectors for Microsoft 365, CRM, HR, DMS and ERP systems.
0 — No API and no integrations; everything happens in the vendor's web app.
3 — A few named integrations or a Zapier connector, and an API mentioned without public documentation.
5 — A documented REST API with webhooks and a sandbox, plus connectors for Microsoft 365 or Google Workspace and at least one CRM or HR system named.
8 — Embedded signing in the customer's own application, API access to every signature level, versioned API with rate limits published, SDKs, and connectors for named DMS, ERP or HR systems with their scope.
10 — Integration is a product: white-label and embedded flows documented, API parity with the web app, a status page with incident history, deprecation policy, and a marketplace of integrations with stated maintainers.
The Legal Counsel
The webhook and REST APIs are documented down to OAuth scopes, admin permissions, pagination and custom headers, with SDKs for four languages and an OEM/Embedded partnership for building signing into the customer's own product. We found no public information on a sandbox, on published rate limits, or on any named connector for Microsoft 365, CRM, HR or document management systems. 5 6 2
The HR Operations Lead
A documented REST API with webhook endpoints, OAuth scopes and cursor pagination, ready-to-run SDK samples for Node.js, Java,.Net and Python, and an OEM/embedded partnership track are all evidenced; we found no public information on connectors to HR or CRM systems, a sandbox, or published rate limits, so integration with my hiring toolchain stays unproven. 2 5 6
The Revenue Operations Lead
This is the strongest area: a documented webhook endpoint API with full CRUD operations, OAuth scopes and pagination, SDKs for Node.js, Java,.Net and Python, embedded signing "into mobile apps, websites, or platforms", ready-to-run samples and an OEM/embedded partner track. But we found no public information on connectors for Microsoft 365, Google Workspace or any CRM — I cannot send a quote for signature from inside our CRM on this evidence — nor on a sandbox, published rate limits or API versioning. 2 5 6
The Integration Engineer
The webhook endpoint API is properly engineered — OAuth scopes per operation, full create-read-update-delete, pagination, custom headers, HTTPS enforcement — with SDKs for Node.js, Java,.NET and Python and an OEM/embedded partnership for native integration, which is close to my ideal shape. I found no public information on a sandbox, on connectors for Microsoft 365, CRM, HR, DMS or ERP systems, or on published rate limits and API versioning, and nothing establishes that every signature level is reachable through the API rather than only the seal. 2 5 6
The Data Protection Officer
The developer pages document REST APIs with OAuth scopes, pagination and full webhook endpoint management, SDKs for Node.js, Java,.NET and Python, embedded e-signature in the customer's own applications, an OEM/embedded partner track with private APIs, and a live demo — the substance of an integration product. We found no public information on connectors for Microsoft 365, Google Workspace or named CRM, HR and DMS systems, on published rate limits, or on API access per signature level. 2 5 6
The Skeptic
This is where the effort visibly went: a documented REST API, webhooks with OAuth2.0 spelled out endpoint by endpoint, ready-to-run samples for Node.js, Java,.NET and Python, embedded e-signature for apps and platforms, and an OEM/Embedded partner track with private APIs. We found no public information on a sandbox, published rate limits, API versioning or a single named Microsoft 365, CRM, HR or DMS connector in the captured pages. 2 5 6
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity, the trust service provider and their owners are, where documents, audit trails and ID data are stored and processed, and who the subprocessors are. Independently sourced by the sovereignty pipeline.
0 — Non-EU contracting entity, no statement on where documents and signer data are stored, and subprocessors unnamed.
3 — An EU entity contracts, but documents or signer data are processed outside the EU by default without an explained safeguard, or the subprocessor list is absent.
5 — EU contracting entity and EU data storage stated, with a DPA, but the hosting, identification or trust service chain is non-EU-controlled without a stated safeguard.
8 — EU entity, documents, audit trails and ID data stored in named EU data centres, an EU qualified trust service provider, subprocessor list with locations published, and certifications (ISO 27001, ETSI conformity) published.
10 — Sovereign end to end and evidenced: European ownership, EU entity and EU QTSP, every processing location and subprocessor European, customer-selectable data residency, and certifications with their scope published.
The Legal Counsel
EU customers contract with Adobe Systems Software Ireland Limited, an EU entity, but the captured pages state nothing about data locations: we found no public information on where documents, audit trails and identification data are stored or processed, and no subprocessor list with locations. The named trust service and timestamp providers include US and Japanese firms alongside EU ones, and a security overview document is referenced without its scope shown. 1 6
The HR Operations Lead
EU customers contract with the Irish Adobe entity, which is a start, but we found no public information on where signed documents, audit trails and signer ID data are stored or processed, which subprocessors touch them, or the ownership of the trust chain; a security overview is referenced but its contents are not shown. 6
The Revenue Operations Lead
EU customers contract with Adobe Systems Software Ireland Limited while ownership sits with Adobe Inc. of San Jose, and we found no public information on where documents, audit trails or signer data are stored or processed. No subprocessor list appears in the captures; the only related item is a security overview document that is said to exist. 6
The Integration Engineer
The vendor information shows EU customers contracting with Adobe Systems Software Ireland while the parent is Adobe Inc. of San Jose, and a security overview document is referenced. I found no public information on where documents, audit trails or identification data are stored, on the trust service chain's ownership, or on any subprocessor list with locations. 6
The Data Protection Officer
The vendor is Adobe Inc. of San Jose with EU customers contracting through Adobe Systems Software Ireland, and no sovereignty attributes are on record: we found no public information on where documents, audit trails or any identification data are stored or processed, no subprocessor list, and no published certifications on the captured pages. The timestamp and certificate chain names DigiCert, GlobalSign, Seiko and others, and I can map none of them to a processing location or a safeguard. 1 6
The Skeptic
EU customers contract with Adobe Systems Software Ireland Limited, but the parent is Adobe Inc. of San Jose, and we found no public information on where documents, audit trails and signer data are stored, on any subprocessor list with locations, or on published certifications beyond a security overview document. Every named trust service provider is a third party; the hosting and identification chain is invisible in the captured pages. 1 6
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the cost of their signing volume from public pages alone — plan prices, envelope or document limits, the per-signature price of AdES and QES, identification fees, API pricing and overage.
0 — No public prices at all; every plan is a sales conversation.
3 — Plan prices published, but envelope limits, QES and identification fees are unstated — the cost of a qualified signature is unknowable.
5 — Plans with envelope or document limits priced, but at least one commonly incurred cost (per-QES fee, video ident, API access, overage) is missing or "on request".
8 — Every plan and limit priced publicly, AdES and QES priced per signature, identification fees and overage stated, API pricing published, and contract term and notice period given.
10 — Complete cost computability: the cost of a given monthly volume per signature level derivable from public pages, volume tiers published, and every add-on and price-change term on a public page.
The Legal Counsel
We found no public pricing information on the captured pages — no plan prices, no envelope or document limits, and no per-signature, identification or API fees. The cost of any signing volume, qualified or otherwise, cannot be computed from what was captured. 6 1
The HR Operations Lead
We found no public information on prices at all — no plan pricing, no per-signature cost for advanced or qualified signatures, no identification fees and no volume terms; the cost of a qualified employment signature cannot be known before the contract goes out, which makes every plan a sales conversation. 6
The Revenue Operations Lead
None of the captured pages shows a plan price, envelope or document limit, per-signature fee for advanced or qualified signatures, identification charge or API pricing — they are developer documentation. We found no public information on pricing, so I cannot compute the cost of our signing volume and everything becomes a sales conversation. 6
The Integration Engineer
I found no public pricing on the captured pages — no plan prices, no per-signature or per-seal fees, no identification or API pricing, no overage terms. A buyer cannot compute the cost of any signing volume from what I reviewed. 6
The Data Protection Officer
We found no public information on plan prices, envelope or document limits, per-signature fees for any signature level, identification fees, API pricing or overage. No signing volume can be costed from the captured pages. 6
The Skeptic
Not one price appears in the captured material — no plan prices, no envelope limits, no per-signature or per-seal fee, no identification fee, no API pricing, no overage, no contract term. A buyer cannot compute any part of their signing cost from these pages; every number is a conversation with sales. 6
Questions about Adobe Acrobat Sign
Is Adobe Acrobat Sign European?
No. whats-best.ai classifies Adobe Acrobat Sign as Rest of world.
Where does Adobe Acrobat Sign store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Adobe Acrobat Sign have a free plan?
Yes. Adobe Acrobat Sign has a free plan, per the vendor’s page captured 13 Oct 2026.
What are the best alternatives to Adobe Acrobat Sign?
As of 15 Oct 2026, the panel rates Penneo (2.5/5), Youtrust (Yousign) (2.5/5) and MOXIS (2.5/5) highest among the other 14 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 Penneo (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Adobe Acrobat Sign alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 10 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. Know more? Tell us
- 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. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (6)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 EIDAS levels & trust services — found from sitemap developer.adobe.com Checked 13 Oct 2026 Details →
- 2 EIDAS levels & trust services — found from sitemap developer.adobe.com Checked 13 Oct 2026 Details →
- 3 Evidence, validation & retention — found from sitemap developer.adobe.com Checked 13 Oct 2026 Details →
- 4 Evidence, validation & retention — found from sitemap developer.adobe.com Checked 13 Oct 2026 Details →
- 5 Integrations & API — found from sitemap developer.adobe.com Checked 13 Oct 2026 Details →
- 6 Integrations & API — found from sitemap developer.adobe.com Checked 13 Oct 2026 Details →