Docusign eSignature vs Skribble

Docusign eSignature

All three eIDAS levels are documented by name — simple signatures included on every plan, advanced in higher plans, qualified as an add-on to eSignature plans — and Docusign names itself as a registered qualified trust service provider in Europe whose tamper-proof certificates accompany every advanced signature. The pages fall short of the top level: we found no public information on the EU Trust List entry link, qualified electronic seals, per-level country availability, or the signature level shown in the finished document and audit trail.

Skribble

All three eIDAS levels are documented with their method and a document example each, ZertES alongside eIDAS, an organisational seal on request, and — the part I care about — the API explicitly supports all three signature standards. Skribble states it is not a trust service provider itself and relies on partners meeting ZertES and/or eIDAS requirements, with Swisscom as the named partner, but I found no public link to an entry on the EU Trust List and no public information showing the signature level in the signed document or its evidence.

Docusign eSignature

The Identify portfolio documents its methods by name — one-time passcodes, phone authentication, automatic validation of government ID documents, biometric liveness via video selfies, and CLEAR or ID.me accounts for IAL2 — plus an identity wallet that reuses a completed verification on later agreements and a proof file compiling the results, with ID checks priced from 2.35 € each. We found no public information on country coverage per method, on retention and deletion of the ID data, or on the identification provider appearing as a named subprocessor.

Skribble

Identification per level is laid out plainly: confirmed email for simple signatures, mobile number with SMS for advanced, and ID scan with selfie video, live video ident or on-site identification for qualified, working under Swiss and EU law with Swisscom named as the identification partner and SMS codes sent via tyntec. I found no public information on retention or deletion of identification data, or on the identification provider within the published subprocessor list.

Docusign eSignature

Bulk send, delegated signing, mobile-optimised web forms with conditional logic and drag-and-drop building, custom branding, eWitness, 44+ signing languages and WCAG 2.0 Level AA in the plan comparison cover most of the advanced workflow range, with shared team templates and the no-code Workflow Builder on top. We found no public information on signer roles, parallel and sequential signing order, automatic reminders, or in-person signing.

Skribble

The sending flow covers most of what I embed: signers sign in the browser with no account or app, arrive by email, link or QR code, signing order is settable, automatic reminders run on admin-chosen intervals with manual reminders for everyone, bulk signing and branding exist, and the API lets me define signers and order and track status. I found no public information on templates with field placement, conditional fields, delegation or signer accessibility.

Docusign eSignature

An audit trail is automatically generated and stored for every agreement, signatures carry tamper-evident PKI certificates, and identity checks compile into a proof file. This is the weak point for our archive requirement: we found no public information on the audit trail's contents and timestamps, long-term validation, a retention period for signed documents and their evidence, or bulk export with the evidence intact into a DMS.

Skribble

The evidence story is thin for archiving to our DMS: I found a public signature validator tool, paid validation and conversion services, and Adobe trust-list conformity in every plan, but no public information on an audit trail, completion certificate, timestamps, long-term validation, retention periods or export of documents with their evidence — and the terms state that accounts, data and documents are deleted when the customer contract ends.

Docusign eSignature

A Developer Centre with an API overview and a free developer account, forms embeddable into our own applications with our branding, API pre-population of fields, and named connectors with described scope — SharePoint send-sign-store with list data synchronised back, Dynamics 365, NetSuite, Salesforce, Outlook, Word, Teams and Power Automate — plus an App Center of 1000+ integrations give us a genuine embedding story. But we found no public information on webhooks, API versioning, published rate limits, SDKs, or whether qualified signatures can be triggered through the API rather than only the web app, and API plans are named with no prices attached.

Skribble

This is close to my checklist: a documented open REST API with an immediately testable demo key, all three signature standards reachable through it, a defined upload-signers-order-track workflow, and connectors for Microsoft 365, Google Drive, SAP and Salesforce, though API access and integrations are gated to the Pro and Scale plans. I found no public information on webhooks, API versioning, rate limits, SDKs, embedded signing or a DMS connector.

Docusign eSignature

European elements are proven: a Dublin EMEA entity for privacy matters, data centres across three EU countries, registration as a European qualified trust service provider, and ISO 27001. However the contracting controller is Docusign, Inc. of San Francisco, personal data is stored in infrastructure that may span Australia, the United States, the EU and Canada, data residency is offered only through a sales contact, and we found no public information on ownership or the subprocessor chain.

Skribble

The chain is largely proven: contracting entities are Skribble AG in Zurich and Skribble Deutschland GmbH in Karlsruhe depending on the booking URL, hosting runs in certified data centres in Germany or Switzerland chosen at setup, a DPA and ISO 27001 are published, and the privacy policy lists subprocessors with full addresses. Ownership is unknown to me, some listed processors are US companies such as Cloudflare, Clay Labs and Make.com, and I found no public information on where identification data is held.

Docusign eSignature

The three main plans are fully priced with billing period and limits — Personal 9 €/month with 5 envelopes per month, Standard 23 €/month per user with 100 envelopes per user and year, Business Pro 38 €/month per user — plus identity checks from 2.35 € per ID check, overage fees, and auto-renewal with five business days' notice and no-refund terms in the published conditions. We found no published price for the qualified signature add-on or the API plans, and identity verification on its own product page sits behind a sales contact, so the cost of a qualified-signature volume is not computable from these pages.

Skribble

Starter is published at 0 EUR per month pay per use with 2 SES for free, Pro at 6 EUR per month per user billed annually with unlimited simple and 120 FES/QES per year, and identification fees are public to the euro and franc — 15,50€ pro Identifikation for eIDAS and CHF 37 pro Identifikation for ZertES, each with a minimum of 50 — with contract durations and notice rules in the terms, all excluding VAT. Team and Scale prices are not public, the captured pages give different plan names with the pricing page listing Starter, Pro and Scale while the terms list Individual, Team and Pro, and I found no public per-signature price for the pay-per-use plan, no API pricing and no overage terms.