E-Signature
Scrive
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Scrive AB · www.scrive.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.
Scrive at a glance
- Vendor
- Scrive AB
- 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
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Scrive 2.5/5, the mean of 6 judges. Scrive, an e-signature and digital-identity vendor based in Stockholm, is strongest where signing meets identity: signing workflow scores 6-7 and identity verification 6-7, built on eIDs named with their countries — BankID, MitID, Smart-ID, itsme, iDIN, Verimi, Onfido — document-and-biometric checks, and a browser-based qualified-signature flow with one-shot or reusable passkey or Mobile-ID identification. 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
Scrive, an e-signature and digital-identity vendor based in Stockholm, is strongest where signing meets identity: signing workflow scores 6-7 and identity verification 6-7, built on eIDs named with their countries — BankID, MitID, Smart-ID, itsme, iDIN, Verimi, Onfido — document-and-biometric checks, and a browser-based qualified-signature flow with one-shot or reusable passkey or Mobile-ID identification. Integration and API holds at 6 with no spread, on a documented REST API, an OpenID Connect-certified identity hub and named connectors such as iManage, NetDocuments and Documaster. The lowest scores on the table are pricing transparency at 2-4: no price figures appear in the captured pricing material, and eID and SMS costs are answered "for further information please contact us". Evidence and retention sits at 4-5, with no public information found on transaction-log contents, timestamp sources or long-term validation. Sovereignty scores 3-4 — the privacy notice states all geolocations for data hosting are within the EU/EEA, but we found no public information on ownership, the contracting entity's jurisdiction or a named subprocessor list. No criterion splits the judges by more than two points.
Speaks for it
- Qualified and advanced signatures are labelled products through Scrive Certified Trust Services, with the eIDAS legal effect of QES explained
- Signers identify and sign in a single browser session with no mandatory app download, video call or third-party account
- eIDs are named with their countries — BankID, MitID, Smart-ID, itsme, iDIN, Verimi — alongside Onfido document-and-biometric checks
- Every signed document carries an evidence package including a transaction log, and exports go to SharePoint, SFTP, NetDocuments and similar systems
- Plans publish unlimited documents, with private accounts free for trying Scrive eSign
Held against it
- No price figures appear in the captured pricing material, and eID and SMS fees are answered "for further information please contact us"
- We found no public information on the transaction log's contents, timestamp sources, long-term validation or validation reports
- The subprocessor statement covers only "most" processors within the EU/EEA, with no published names or locations
- eIDs and SMS authentication are add-ons with additional fees on the Business plan, and BankID/eIDs are not available as add-on on Essential
- The privacy notice names Scrive AS as provider of the trust services while the vendor presents as Scrive AB in Stockholm
Best for
- You need qualified e-signatures under eIDAS for signers holding Nordic, Baltic and Benelux eIDs such as BankID, MitID, Smart-ID and itsme
- You need signers to complete identification and signing in one browser session, with no app download, video call or third-party account
- You need to embed signing in your own product or export signed documents to systems like iManage, NetDocuments or SharePoint via a documented REST API
- Your onboarding or HR flows need fill-and-sign web forms that trigger signing without integration work
Avoid if
- You must compute the cost per qualified signature or eID check before committing — the pages state "additional fees apply" and "for further information please contact us" with no figures
- You need signed evidence to stay retrievable in the vendor's e-archive long after the contract ends — account data retention is the duration of the agreement plus up to 30 days, and we found no public information on e-archive retention for signed documents
- Your procurement requires a named subprocessor list and confirmed ownership or contracting entity — the privacy notice says only that most subprocessors and processing locations are within the EU/EEA
- You need eID-verified signing at the entry tier — Essential lists BankID/eIDs as not available as add-on
The scores
| Criterion | Panel median |
|---|---|
| eIDAS levels & trust services | 2.5 of 5 |
| Signer identification | 3 of 5 |
| Signing workflow & signer experience | 3.5 of 5 |
| Evidence, validation & retention | 2 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 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
Advanced and qualified signatures are explicit product lines: Scrive Certified Trust Services signs with both levels, QES Global is presented as the highest assurance under eIDAS with the same legal effect as a handwritten signature and a reversed burden of proof, and the Business plan names Scrive QES. We found no public information linking a qualified trust service provider entry on the EU Trust List, on qualified seals, on ZertES, or on which plan and country delivers which level with the level printed in the signed document and audit trail. 2 3 4 5
The HR Operations Lead
The pages label qualified and advanced signatures, name the trust service behind them — Scrive Certified Trust Services from Scrive AS — and document QES Global as a browser-based qualified signature under eIDAS with its handwritten-equivalent effect and presumption of validity across the EU explained, and the Business plan shows where Scrive QES sits. I found no public information on simple signatures being labelled, an EU Trust List link, qualified seals, or the signature level printed in the signed document and audit trail. 3 4 5 2
The Revenue Operations Lead
Scrive labels advanced and qualified signatures in the product, names itself as a trust service provider since 2010 through Scrive Certified Trust Services, and explains that a qualified signature carries the same legal effect as a handwritten signature across all EU member states, supported by BankID, Smart-ID and itsme. For a buyer matching levels to documents, we found no public information naming the simple signature level, no link to an entry on the EU Trust List, no qualified seals, and no statement of which plan or country offers which level beyond qualified signing appearing in the Business plan. 2 3 4 5 6
The Integration Engineer
Advanced and qualified signatures are labelled products with Scrive AS named as provider of the Scrive Certified Trust Services, and the QES pages explain the eIDAS legal effect and presumption of validity in real detail, with regional eIDs named for the QES portfolio. I found no public information on simple-signature labelling, qualified seals, a link to the provider's EU Trust List entry, or the signature level being printed in the signed document, and plan coverage is only implied through the Business add-on structure. 3 4 5 2 6
The Data Protection Officer
Advanced and qualified signatures are labelled through Scrive Certified Trust Services, Scrive names itself a trust service provider since 2010, and QES legal effect across the EU is documented. We found no public information on qualified seals, a link to an entry on the EU Trust List, ZertES, or guidance on which documents need which level in Germany or any other market. 3 4 5 2 6
The Skeptic
Advanced and qualified signatures are labelled through Scrive Certified Trust Services and Scrive presents itself as a trust service provider since 2010, with QES under eIDAS and its EU-wide legal effect explained. I found no public information linking the provider to its EU Trust List entry, no qualified seals, and no per-country statement of which level is available where; on the cheapest plan eIDs are explicitly not available, so qualified signing is an add-on above it. 2 3 4 5 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
A dozen eIDs are named with their regions — Swedish and Norwegian BankID, MitID, Smart-ID, itsme, iDIN, Verimi — alongside Onfido document-and-biometric checks with a live-agent liveness option, and the one-shot versus reusable passkey or Mobile-ID choice for QES is explained. We found no public information on retention and deletion of identification data specifically, on the ident provider being listed as a subprocessor, or on EUDI wallet support. 3 5 6 7
The HR Operations Lead
The eID Hub pages name method after method with their countries — BankID, MitID, Smart-ID, itsme, Verimi, iDIN, OneID, Onfido — and the QES flow spells out a government-ID scan plus browser selfie liveness, with the live-agent variant distinguished and reusable identification via passkey or Mobile-ID explained; that covers the IDs my applicants actually hold. We found no public information on a named subprocessor list for the identification providers or on retention specific to ID data beyond the general account-data period. 6 7 4 5 3
The Revenue Operations Lead
This is where Scrive shows its Nordic depth: BankID, MitID, Smart-ID, itsme, iDIN, Freja, Verimi, Onfido and PIN by SMS each listed with their regions, identity verification spelled out as document scan plus selfie plus a live-agent liveness check, and the choice between a one-shot signature and a reusable passkey or Mobile-ID explained. We found no public information mapping each method to a signature level and country, no completion guidance or failure rates, and while the privacy notice states account-data retention of the agreement plus up to 30 days, we found no subprocessor listing for the identification chain. 3 4 5 6 7
The Integration Engineer
The identity pages name a long list of methods with their regions — BankID, MitID, Smart-ID, itsme, Verimi, Onfido and more — describe document-scan, selfie and live-agent liveness checks, and explain reusable identification via passkey or Mobile-ID. For embedding this end to end I would need a per-level, per-country matrix, a retention statement specific to ID data, and the identification providers named on the subprocessor list; I found no public information on those. 5 6 7 3
The Data Protection Officer
Named eIDs with their countries plus documented IDV methods — document photo, selfie, live-agent liveness — and a clear one-shot versus reusable identification story put this above the mid anchor. But we found no public information on retention or deletion of the biometric and ID document data collected in the browser flow, and no subprocessor list naming who performs identification. 6 7 4 5 3
The Skeptic
Methods are named with their countries — Swedish and Norwegian BankID, MitID, Smart-ID, itsme, iDIN, Verimi, Mobile-ID, PIN by SMS, plus Onfido document-and-biometric checks — and the qualified flow explains one-shot versus reusable identification via passkey or Mobile-ID, distinguishing the browser flow from a live-agent liveness check. What happens to the identification data afterwards is covered only by a generic account-data retention figure, and no subprocessor list places the identification providers. 3 4 5 6 7
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
Signing order, configurable signing groups with required signature counts, bulk and bundled sending, reminders, templates and no-code forms with conditional logic are all named, and signers work browser-based on any device with no app download and no third-party account. Signer languages are not listed, and accessibility rests on a browser-usability claim rather than a published conformance statement. 2 4 8 10
The HR Operations Lead
Templates, reminders, bulk send on the Enterprise plan, configurable signing groups with order, bundled sending and fill-and-sign web forms that trigger signing are all public, and signers work in the browser on any device with no app or third-party account — the ten-minute phone experience I need for new hires. We found no public information on delegation or substitute signers, signer languages, or a published accessibility conformance statement; the accessibility language present is a general claim about the browser-based flow. 2 4 8 10 9
The Revenue Operations Lead
What gets a quote back signed fastest is all here: templates, automatic signing reminders, bulk send, bundled sending, signing groups where I set how many people sign in which order, and a signer experience that needs no account, no app and no video call — one browser session on any device. Fill-and-sign web forms with publishable links and respondents adding signatories on the fly cover the self-service edge. We found no public information on delegation or substitute signers, signer languages, or a published accessibility statement, though the browser flow is described as ensuring accessibility. 2 4 8 10
The Integration Engineer
Templates, signing reminders, bulk send, signing groups with configurable order, branded no-account browser signing on any device, and no-code web forms with dynamic logic cover most of what my portal flows need, and one-shot QES in a single browser session removes signer friction. We found no public information on delegation or substitute signers, signer languages, or a published accessibility conformance statement. 2 8 10 4 9
The Data Protection Officer
Templates, automatic reminders, configurable signing groups with order, bulk and bundled sending, branded browser signing without an account or app on any device, and no-code web forms with conditional logic cover most of a sender's needs. We found no public information on delegation or substitute signers, expiry, signer languages, or a published accessibility conformance statement. 2 10 4 8
The Skeptic
Templates, reminders, custom branding, signing groups with configurable signature order, bundled sending, no-code web forms with conditional logic, and signing in a single browser session without app download or third-party account cover most of the middle ground. Bulk send sits on the Enterprise plan only, and I found no public information on delegation or substitute signers, signer languages, or a published accessibility statement. 2 4 8 10
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
An evidence package including a transaction log is attached to every signed document, account-data retention is stated as the duration of the agreement plus up to 30 days, and signed documents export to SFTP, SharePoint and named DMS connectors. The captured pages are silent on qualified timestamps, long-term validation such as PAdES-LTV, validation reports and the transaction log's contents — precisely what I would need to defend a signature in a dispute eight years on. 2 3 11
The HR Operations Lead
Every signed document gets an evidence package with a transaction log attached, it is a listed Essential feature, and signed documents export to SFTP, SharePoint and similar systems, with account-data retention given as the agreement plus up to thirty days. The captured pages do not show what the transaction log contains, and we found no public information on timestamp providers, long-term validation, a validation report, or how long signed documents are kept in the e-archive. 3 2 11
The Revenue Operations Lead
An evidence package including a transaction log is attached to every signed document, and the retention period for account data is stated as the duration of the agreement plus up to 30 days. What I cannot lean on years later is the proof itself: we found no public information on the trail's contents, the timestamp source, long-term validation, or a validation report. Export to Google Drive, SharePoint, SFTP and NetDocuments is documented for signed documents. 2 3 11
The Integration Engineer
Every signed document carries an attached evidence package with a transaction log, retention is stated as the duration of the agreement plus up to 30 days, and signed documents export automatically to SharePoint, SFTP, NetDocuments and other systems. For archiving in our DMS I need more: I found no public information on long-term validation (PAdES-LTV), qualified timestamps from a named provider, or a validation report or tool. 3 2 11
The Data Protection Officer
Every signed document carries an evidence package with a transaction log, account data retention is stated as the duration of the agreement plus up to 30 days, and offboarding is allowed before inactive-account deletion. We found no public information on what the transaction log records — signer events, IP addresses, authentication method — nor on timestamps, long-term validation, or how long the evidence itself is kept. 3 2 11
The Skeptic
An evidence package including a transaction log is attached to each signed document, documents sit in an e-archive with export to storage connectors, and account data retention is stated as the duration of the agreement plus up to 30 days. I found no public information on timestamp sources, long-term validation or validation reports, so the contents of that log and its durability in ten years are unverifiable — and thirty days after the agreement ends is thin for evidence meant to outlive the subscription. 2 3 11
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
A documented REST API with a developer guide, OpenID Connect on the eID Hub, embedded signing inside customers' own products, and a broad connector directory including iManage, NetDocuments and Documaster alongside Microsoft Office and Google Workspace. We found no public information on webhooks, a sandbox, SDKs, published rate limits, or API access per signature level. 6 10 11
The HR Operations Lead
A documented REST API with a developer guide exists, embedded signing in the customer's own product is a stated use case, and the integrations catalogue names Microsoft Office and Google Workspace plus a long list of DMS and contract-management connectors with export of signed documents to storage. I found no public information on webhooks, a sandbox, rate limits, SDKs or API versioning, and the catalogue's HR category shows no named HR system in the captured pages. 10 11 1
The Revenue Operations Lead
Signing from inside the systems where contracts are made is half-built: a documented REST API with a developer guide, an OIDC-certified eID Hub API, embedded signing described for SaaS products and marketplaces, an open-source MCP server, and named connectors for Microsoft Office, Google Workspace and DMS systems like iManage, NetDocuments and Documaster. CRM appears only as an integration category with no named connector, and we found no public information on webhooks, a sandbox, published rate limits or SDKs. 1 6 10 11
The Integration Engineer
There is a documented REST API with a developer guide, an OIDC-certified single integration covering the identity services, embedded signing described for SaaS and marketplace flows, named connectors for DMS and storage systems, and an open-source MCP server. But the captured pages give no webhooks, no sandbox, and no versioning, rate limits or SDKs — the operational details that decide whether I can build on it. 10 6 11 1
The Data Protection Officer
A documented REST API with a developer guide, embedded signing inside the customer's own product, an open AI-agent server, and a wide catalogue of named connectors for Office, Google Workspace, storage, DMS and legal systems show real integration depth. We found no public information on webhooks, a sandbox, published rate limits, SDKs or API versioning. 10 11 1
The Skeptic
A documented REST API with a developer guide, embedded signing as a stated use case, an OpenID Connect-certified identity hub, and a broad named connector directory spanning Microsoft 365, Google Workspace, storage and contract-management systems. I found no public information on webhooks, a sandbox, published rate limits, SDKs or API versioning, which holds this below the top band. 6 10 11
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
The privacy notice commits all hosting geolocations to the EU/EEA and discloses AWS for the standard platform with an EU-provider alternative for Scrive EC, and ISO 27001 EU data hosting is advertised. The subprocessor statement covers only 'most' processors with no published list, the contracting entity and ownership are not evidenced on the vendor's own captured pages, and we found no public information naming the EU data centres or the trust service chain's jurisdiction. 1 3
The HR Operations Lead
The privacy notice states that all data-hosting geolocations are within the EU/EEA and offers an EU-hosted platform alongside the AWS-hosted standard platform, with ISO 27001 EU hosting on the homepage. Beyond that, we found no public information on ownership details, named data centres, or a subprocessor list with locations — the trust service sits with Scrive AS, but the captured pages do not publish the certification scope an EU buyer needs. 3 1
The Revenue Operations Lead
The privacy notice states that all geolocations for data hosting are within the EU/EEA, that the standard platform runs on AWS with Scrive EC hosted by an EU provider, and the homepage carries an ISO 27001 EU-hosting claim. We found no confirmation of the contracting entity's jurisdiction or its ownership on the captured pages, no subprocessor list — the notice says only that "most" subprocessors are within the EU/EEA — and no named data centres or certification scope. 1 3
The Integration Engineer
The privacy notice states all data hosting geolocations are within the EU/EEA across two platforms — AWS for the standard platform and an EU provider for Scrive EC — and Scrive AS provides the trust services, with ISO 27001 EU hosting mentioned. The contracting entity's jurisdiction and ownership are not confirmed on the captured pages, the subprocessor list is not published by name, and no specific data centres or certification scopes are given. 3 1 6
The Data Protection Officer
EU/EEA hosting locations are stated with an ISO 27001 claim, but the standard platform runs on AWS and the only subprocessor statement is that most are within the EU/EEA, with no published list of who they are or where they sit. We found no public information on ownership or the contracting entity's jurisdiction on the captured pages, so the trust chain cannot be traced end to end. 3 1
The Skeptic
The privacy notice states that all data-hosting locations are within the EU/EEA, with the standard platform on AWS and a second platform hosted by an EU provider, and ISO 27001 EU hosting is advertised. I found no public information naming any subprocessor, on ownership, or confirming the contracting entity's jurisdiction; the privacy notice attributes the trust services to Scrive AS while the vendor presents as Scrive AB in Stockholm. 1 3
Pricing transparency
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
Plans are published with their feature splits and unlimited documents, but eID and BankID come as add-ons with unspecified additional fees, and the stated answer for SMS and eID pricing is to contact Scrive — so the cost of a qualified signature cannot be computed from public pages. No per-signature, identification or API fee figures appear in the captured pricing material. 1 2 6
The HR Operations Lead
Seven product pricing pages exist and the eSign Online page publishes plan tiers with unlimited documents and named add-ons. The eID/BankID and SMS fees are marked "additional fees apply" with "for further information please contact us", and the captured pages contain no price figures at all — so the per-qualified-signature cost I need before sending two hundred contracts a year is not computable from public pages. 1 2 6
The Revenue Operations Lead
The pricing page separates Essential, Business and Enterprise with unlimited documents and lists eID/BankID, SMS authentication and the forms builder as add-ons with additional fees, but we found no price figures on the captured pages and the variable eID and SMS fees go by "for further information please contact us". The cost of a qualified signature is a sales conversation rather than a computable line; only the free private account and the free trial are stated at zero cost. 1 2 3
The Integration Engineer
Dedicated pricing pages exist for eSign Online, eSign GO, eSign API, ID Check, eID Hub, eSign Forms and Forms Builder, documents are unlimited, and private accounts are free — but I found no public price figures for any plan, and eID/SMS fees are answered with "For further information please contact us", so the cost of a qualified signature is not computable from public pages. 1 2 6
The Data Protection Officer
The pricing pages name plans and priced products and state unlimited documents, but no price amount appears anywhere in the captured pages and SMS and eID costs are answered with "please contact us". A buyer cannot compute the cost of a qualified signature or of identification from what is published here. 2 1 6
The Skeptic
The public pricing page names three plans with unlimited documents and separate pricing pages exist per product — but the eID and qualified-signature add-ons are "additional fees apply", SMS and eIDs are "for further information please contact us", and no plan price, per-signature, identification or API figure appears in the captured material. The cost of a qualified signature on top of the plan is therefore not computable from public pages. 1 2 6
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Scrive
Is Scrive European?
Yes. whats-best.ai classifies Scrive as EU-Made.
Where does Scrive store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Scrive have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Scrive?
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: Scrive 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.
- Weak sourcing — Legal entity, Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- 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.
- 7 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
- 4 pricing 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
- 3 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. 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 (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.scrive.com Checked 13 Oct 2026 Details →
- 2 Pricing page www.scrive.com Checked 13 Oct 2026 Details →
- 3 Privacy policy www.scrive.com Checked 13 Oct 2026 Details →
- 4 EIDAS levels & trust services — found from sitemap www.scrive.com Checked 13 Oct 2026 Details →
- 5 EIDAS levels & trust services — found from sitemap www.scrive.com Checked 13 Oct 2026 Details →
- 6 Signer identification — found from sitemap www.scrive.com Checked 13 Oct 2026 Details →
- 7 Signer identification — found from sitemap www.scrive.com Checked 13 Oct 2026 Details →
- 8 Signing workflow & signer experience — found from sitemap www.scrive.com Checked 13 Oct 2026 Details →
- 9 Signing workflow & signer experience — found from sitemap www.scrive.com Checked 13 Oct 2026 Details →
- 10 Integrations & API — found from sitemap www.scrive.com Checked 13 Oct 2026 Details →
- 11 Integrations & API — found from sitemap www.scrive.com Checked 13 Oct 2026 Details →