Castor eConsent vs WeGuide(eConsent)

Sponsors, CROs, research sites and academic teams choosing eConsent software for clinical trials and research studies.

Scope Electronic informed consent (eConsent) software that presents, explains, signs and version-controls participant consent for clinical trials and research studies, remote or on site, as sponsors, CROs, sites and academic research teams would shortlist it.

Guide updated How we compare

Compare within eConsent

Study fit, side by side

These notes describe the products in the eConsent guide.

Castor eConsent

Best for
Teams that want eConsent linked to Castor EDC and ePRO, with video consent visits
What to consider
Castor eConsent includes video consent visits, knowledge checks, versioning with re-consent and a REST API, and study teams build consent forms themselves. It publishes 20 participant interface languages and a pricing process, but no eConsent-specific scale figures.
Read product profile

WeGuide

Best for
Clinical trials and research studies that need informed consent connected to ongoing participant engagement, questionnaires and follow-up
What to consider
WeGuide connects informed consent with ongoing participant engagement throughout clinical trials and research studies. Teams can combine screening, consent, questionnaires, reminders and follow-up in one study program, rather than treating signing as the end of the workflow. Publicly described consent features include multimedia forms, comprehension checks, version control, reconsent, remote signing and multiple signatories. Confirm protocol-specific signature, validation and implementation requirements.
Less suitable for
Teams that only need a basic consent-document workflow, or require a country-by-country signature service or native enterprise EDC from the same provider; confirm the required scope.

Study-fit source

Read product profile

Compare the features

Both products use the same category definitions. Product order is editorial; products are not ranked.

Full eConsent feature comparison

Single and double checks describe documented support for an individual feature. Double checks use the extended definition for that feature. Unknown means the available evidence does not establish support.

Expand a feature definition or support note for context and its original source.

Castor eConsent vs WeGuide (eConsent): category feature evidence and sources. Products are not ranked.
Category featureCastor eConsentWeGuide
Consent experience and comprehension
Feature definitions
Supported
A digital consent presentation or completion workflow is documented.
Extended support
Digital consent includes both multimedia content and participant comprehension checks.
Extended support

Built-in video visits, knowledge-check questions, videos in forms, versioning and re-consent for amendments, remote, on-site or hybrid; LAR or assent flows not documented.

Source
About this support label

Consent forms include videos and knowledge-check questions.

Extended support

The no-code consent builder supports video, audio and comprehension quizzes, electronic signatures, multiple signatories and representatives. Versions, reconsent and consent status are tracked in the study workflow.

Source
About this support label

Both multimedia consent content and participant comprehension checks are explicitly documented.

Compliance and regulatory track record
Feature definitions
Supported
Relevant trial or security controls are stated.
Extended support
Relevant trial controls plus a public ISO/SOC certificate or audit report are documented; a certification claim or logo alone is insufficient.
Supported

Part 11 compliant eSignatures, full audit trail and MFA; ISO 27001 certified; Castor platform used in 6,100+ trials.

Source
About this support label

Trial controls and ISO certification are stated; this note does not establish a public certificate or audit report.

Supported

WeGuide states ISO certification and support for HIPAA, GDPR and 21 CFR Part 11 requirements. Its public statements do not supply a current ISO certificate or SOC audit report.

Source
About this support label

Published trial and privacy controls meet the documented-support definition. A public certificate or audit report has not been established.

Global scale and languages
Feature definitions
Supported
Multicountry use or multilingual/localized participant support is documented.
Extended support
Both multicountry use and multilingual/localized participant support are documented.
Supported

Participant interface in 20 languages, forms in any language, EU or US data storage and a hybrid paper option.

Source
About this support label

Languages and storage regions are documented; storage regions do not establish multicountry use.

Extended support

WeGuide describes multilingual consent, including the INHERIT study, and participant research across five countries in BRACE. These are vendor-published study examples, not a country-by-country e-signature acceptance list.

Source
About this support label

The source documents multilingual consent and multicountry research use, meeting the same definition applied to other platforms.

Integrations and suite fit
Feature definitions
Supported
A connection to another research system or an API is documented.
Extended support
Native EDC or eCOA integration plus an API or integration with other research systems is documented.
Extended support

Native integration with Castor EDC and ePRO, plus a RESTful API for other vendors.

Source
About this support label

Native EDC and ePRO integration is paired with a REST API for other vendors.

Extended support

Consent tasks link to screening and questionnaires in the same WeGuide program. The product page also documents connections to REDCap and other EDC or eClinical systems, with integration requirements scoped by the team.

Source
About this support label

Native consent/eCOA workflows and connections to other research systems meet the shared definition. This does not mean WeGuide supplies a native EDC.

Time to launch and self-service build
Feature definitions
Supported
A study build process, self-service builder or launch timeframe is documented.
Extended support
Study teams can configure the study themselves, with a stated build or launch timeframe.
Supported

After account set-up, study teams create studies and build consent forms themselves; no turnaround times published.

Source
About this support label

Study teams build forms themselves; turnaround times are not published.

Extended support

The no-code consent builder lets teams configure approved consent content. WeGuide states most eConsent studies can go live within days with team support. This is an eConsent setup claim; full app publishing and integration timelines require separate scoping.

Source
About this support label

A team-configurable builder and a stated consent launch timeframe are documented. No blanket promise is made for the entire study rollout.

Published pricing and terms
Feature definitions
Supported
A production pricing basis, model or contract terms beyond a sales contact are published.
Extended support
Numerical production prices or a free production option with its conditions are published.
Supported

Published pricing process with itemized fixed-scope proposals and change-control terms; no prices.

Source
Supported

WeGuide publishes a per-study quote basis. Contact the team for the study-specific scope and price; no numerical price or free production tier is published.

Source
About this support label

A public per-study quote basis meets the support definition, but not the public-price or free-production definition.

The guide update date reflects guide edits. Vendor statements are attributed in the evidence.

Keep the category in view

Compare these products with the other tools in the eConsent guide using the same feature definitions.

More eConsent comparisons featuring one of these products.