
# Clinical & regulatory document management

Clinical, quality and regulatory document control.

Canonical page: https://launchinyourcloud.com/categories/clinical-regulatory-document-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


Clinical, quality and regulatory document control.

3 listings.


## eLabFTW

Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

- Listing: https://launchinyourcloud.com/directory/elabftw/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: eLabFTW application containers, database and persistent uploaded records on a customer VPS.
- Operations: 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.
- Product website: https://www.elabftw.net
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Verify the actual provider image and current upstream security fixes. Laboratory record controls are not an automatic clinical-validation, GLP or regulatory-certification claim; institutional procedures and supported dependencies remain separate.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

eLabFTW application containers, database and persistent uploaded records on a customer VPS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

- clinical-regulatory-document-management: Open-source electronic laboratory notebook for tracked experiments, procedures and attached records.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/elabftw (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger VPS (hostinger): https://www.hostinger.com/applications/elabftw
  eLabFTW application containers, database and persistent uploaded records on a customer VPS. Verify the actual provider image and current upstream security fixes. Laboratory record controls are not an automatic clinical-validation, GLP or regulatory-certification claim; institutional procedures and supported dependencies remain separate.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes NicolasCARPi, MoustaphaCamara, MarcelBolten, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/elabftw/elabftw/graphs/contributors

- Upstream project: https://github.com/elabftw/elabftw

### Sources

- Hostinger VPS: https://www.hostinger.com/applications/elabftw

- AGPL-3.0: https://github.com/elabftw/elabftw/blob/master/LICENSE

- Releases: https://github.com/elabftw/elabftw/releases

### Licensing sources

- https://github.com/elabftw/elabftw/blob/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/elabftw


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The system-administrator guide documents SAML user sign-in with one or more identity providers, separately from LDAP and trusted-header external authentication. Account-creation and local-login settings control how users are admitted. Configure the chosen IdP and team mapping for the selected release. Scope: Self-hosted eLabFTW SAML login; LDAP, local login and middleware-header paths are distinct. Source: https://doc.elabftw.net/docs/install/post-install/authentication/saml (reviewed 2026-11-20). Supporting source: Authentication and account policies — https://doc.elabftw.net/sysadmin-guide.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The version-6 installation guide uses the official elabctl management script or a downloadable Docker Compose configuration, then separate configuration/TLS/start steps. The default includes MySQL; the current guide explicitly distinguishes it from MariaDB. Configure secrets, durable data, backups and matching application/database versions. Scope: eLabFTW version-6 container installation path; provision the host and production operations separately. Source: https://github.com/elabftw/elabftw/blob/release/6.0/documentation/docs/install/installation/1-elabctl.md (reviewed 2026-11-20). Deployment artifact: https://get.elabftw.net/. Artifact reference: Official elabctl/configuration download URL is unversioned; guide branch release/6.0 is moving. Supporting source: Runtime and database prerequisites — https://doc.elabftw.net/docs/install/prerequisites.

- Minimum footprint / sizing: Sources checked — unresolved. The current prerequisites identify a 64-bit Linux container host and a MySQL-backed stack, but do not establish a quantitative whole-host CPU/RAM/storage minimum for this laboratory workload. Attachments, database growth, backups, integrations and replicas require a version- and workload-specific design. Scope: eLabFTW application, database and persistent experiment data; container/package allowances are not whole-system HA sizing. Source: https://doc.elabftw.net/docs/install/prerequisites (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: eLabFTW; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/elabftw/elabftw/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 6.0.10 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: eLabFTW upstream application; verify compatibility with the selected package. Source: https://github.com/elabftw/elabftw/releases/tag/6.0.10 (reviewed 2026-11-19).







## FormKiQ Clinical and Regulatory Document Management

Manage clinical trial documentation, regulatory submissions, and quality system records with the version control, audit trails, and retention policies life sciences frameworks require.

- Listing: https://launchinyourcloud.com/directory/formkiq-clinical-regulatory-document-management/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/clinical-regulatory-document-management/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- clinical-regulatory-document-management: Clinical, quality and regulatory document control.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Edition: FormKiQ platform; solution configuration and entitlement must be agreed separately.


### Sources

- Clinical and Regulatory Document Management solution: https://formkiq.com/solutions/clinical-regulatory-document-management/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://formkiq.com/pricing/

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/clinical-regulatory-document-management/

- https://docs.formkiq.com/docs/platform/overview


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Clinical and Regulatory Document Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/clinical-regulatory-document-management/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The overview describes controlled authoring, version comparison, approval routing and change history; validation and regulatory obligations remain deployment-specific. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Clinical and Regulatory Document Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/clinical-regulatory-document-management/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Clinical and Regulatory Document Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/clinical-regulatory-document-management/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Clinical and Regulatory Document Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/clinical-regulatory-document-management/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Clinical and Regulatory Document Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/clinical-regulatory-document-management/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## REDCap (Research Electronic Data Capture)

Institutionally licensed research data-capture and records software with AWS and Azure deployment assets.

- Listing: https://launchinyourcloud.com/directory/redcap/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself.
- Licensing model: commercial-only
- Installation: AWS CDK / CloudFormation or Azure deployment templates; separately supply licensed REDCap software
- Architecture: Licensed REDCap application, database, file storage and identity configuration in customer cloud resources.
- Operations: 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.
- Product website: https://github.com/aws-samples/redcap-on-aws
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself.

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.


### Category fit

- clinical-regulatory-document-management: Institutionally licensed research data-capture and records software with AWS and Azure deployment assets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/aws-samples/redcap-on-aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/vanderbilt-redcap/redcap-azure (checked 2026-11-19). 


### Cloud deployment evidence

- AWS CDK (aws): https://github.com/aws-samples/redcap-on-aws
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure PaaS (azure): https://github.com/vanderbilt-redcap/redcap-azure
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS CDK: https://github.com/aws-samples/redcap-on-aws

- Azure PaaS: https://github.com/vanderbilt-redcap/redcap-azure

- AWS CFN: https://github.com/Vanderbilt-REDCap/redcap-aws-cloudformation

- Consortium: https://projectredcap.org/about/consortium/

- EULA Terms: https://projectredcap.org/join/termsofuse/

- AWS Releases: https://github.com/aws-samples/redcap-on-aws/releases

- REDCap AWS sample container runtime update: https://github.com/aws-samples/redcap-on-aws/releases/tag/v1.3.2

### Licensing sources

- https://projectredcap.org/about/consortium/

- https://projectredcap.org/join/termsofuse/

### Infrastructure sources

- https://github.com/aws-samples/redcap-on-aws

- https://github.com/vanderbilt-redcap/redcap-azure


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: REDCap institutional application authentication options; release/configuration and infrastructure packaging separate. Source: https://projectredcap.org/wp-content/uploads/2025/01/REDCapTechnicalOverview.pdf (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: AWS sample v1.3.2 infrastructure automation; separately entitled REDCap application. Source: https://github.com/aws-samples/redcap-on-aws/blob/v1.3.2/README.md (reviewed 2026-11-21). Deployment artifact: https://github.com/aws-samples/redcap-on-aws/tree/v1.3.2. Artifact reference: v1.3.2.

- Minimum footprint / sizing: Documented. 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. Scope: AWS REDCap sample application-instance defaults and limited reference test. Source: https://github.com/aws-samples/redcap-on-aws/blob/v1.3.2/README.md (reviewed 2026-11-21).

- License pricing: Documented. Proprietary REDCap consortium licence for eligible institutions; the open-source infrastructure licence does not license REDCap itself. Scope: REDCap (Research Electronic Data Capture); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://projectredcap.org/about/consortium/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- REDCap AWS sample container runtime update (security-advisory): 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. Conditions: 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. Source: https://github.com/aws-samples/redcap-on-aws/releases/tag/v1.3.2; reviewed 2026-11-19.



