REDCap (Research Electronic Data Capture)
Institutionally licensed research data-capture and records software with AWS and Azure deployment assets.
7 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
REDCap AWS sample container runtime update
The AWS sample v1.3.2 updates its PHP/Apache base image for CVE-2026-109618 and CVE-2026-109619.
Scope: aws-samples/redcap-on-aws container base php:8.4.27-apache in infrastructure release v1.3.2; not a REDCap application release.
Applies to installations built from the affected sample container. Azure and separately assembled REDCap deployments need their own runtime checks.
Action: Update and rebuild the selected AWS sample container to the corrected pinned base; apply licensed REDCap application updates separately.
Primary source · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
AWS CDK / CloudFormation or Azure deployment templates; separately supply licensed REDCap software
Runs in
Documented customer environment
Licensed REDCap application, database, file storage and identity configuration in customer cloud resources.
- AWS: Customer cloud account
- Azure: Customer cloud account
- AWS
- Azure
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
AWS CDK ↗ · Source checked 2026-11-19
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Azure PaaS ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | AWS CDK / CloudFormation or Azure deployment templates; separately supply licensed REDCap software |
|---|---|
| Infrastructure | Servers / containers Licensed REDCap application, database, file storage and identity configuration in customer cloud resources. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Commercial Only Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself. |
| License | Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Vanderbilt lists Shibboleth, OpenID and Google OAuth2 among REDCap authentication options, separately from LDAP and local-table login. Select and configure an entitled institutional release, IdP and user-rights policy. The AWS infrastructure sample does not automatically configure those application identity methods.
REDCap institutional application authentication options; release/configuration and infrastructure packaging separate · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The AWS-maintained v1.3.2 sample supplies CDK/serverless deployment with an institution-supplied REDCap archive and application configuration. Obtain the REDCap consortium licence/package, review IAM/network/database/storage and supported runtime settings, and plan upgrades; sample code does not grant REDCap software rights.
AWS sample v1.3.2 infrastructure automation; separately entitled REDCap application · Source ↗ · Deployment artifact ↗ (v1.3.2) · Reviewed 2026-11-21
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The v1.3.2 AWS sample defaults each application instance to 2 vCPU/4 GB memory and sets concurrency to ten based on a limited test, recommending workload monitoring/tuning. Database, storage, scheduled work, scaling/HA and uploaded data are separate; this is not a complete 100-user/1-TB capacity or cost estimate.
AWS REDCap sample application-instance defaults and limited reference test · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself.
REDCap (Research Electronic Data Capture); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
REDCap is not open source. Eligible nonprofit institutions can obtain a no-charge institutional licence through the consortium; licensing conditions still apply. Open infrastructure licences do not license REDCap, and deployment does not provide automatic clinical or regulatory validation. Update and rebuild the selected AWS sample container to the corrected pinned base; apply licensed REDCap application updates separately.
Category fit
- Clinical & regulatory document management
- Institutionally licensed research data-capture and records software with AWS and Azure deployment assets.
Compare within Clinical & regulatory document management
- eLabFTWOpen-source electronic laboratory notebook for tracked experiments, procedures and attached records.
- Hostinger
- FormKiQ Clinical and Regulatory Document Management Directory PublisherManage clinical trial documentation, regulatory submissions, and quality system records with the version control, audit trails, and retention policies life sciences frameworks require.
- AWS
These products address related workflows; read their category-fit notes before comparing scope. See all of Clinical & regulatory document management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- AWS CDK ↗github.com
- Azure PaaS ↗github.com
- AWS CFN ↗github.com
- Consortium ↗projectredcap.org
- EULA Terms ↗projectredcap.org
- AWS Releases ↗github.com
- REDCap AWS sample container runtime update ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- AWS CDK ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Licensed REDCap application, database, file storage and identity configuration in customer cloud resources. REDCap is not open source. Eligible nonprofit institutions can obtain a no-charge institutional licence through the consortium; licensing conditions still apply. Open infrastructure licences do not license REDCap, and deployment does not provide automatic clinical or regulatory validation.
- Azure PaaS ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Licensed REDCap application, database, file storage and identity configuration in customer cloud resources. REDCap is not open source. Eligible nonprofit institutions can obtain a no-charge institutional licence through the consortium; licensing conditions still apply. Open infrastructure licences do not license REDCap, and deployment does not provide automatic clinical or regulatory validation.
- AWS CDK ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked