
# Clinical & regulatory document management on Hostinger

Compare documented Clinical & regulatory document management deployments on Hostinger, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/hostinger/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.


## Provider guidance

- Account boundary: Hostinger account and VPS
- Provider group: vps-hosting
- Provider classification: The documented route uses a customer VPS and application administrator; the hosting provider operates its physical infrastructure. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-20).
- Network: Customer server networking, DNS and firewall rules
- Identity and access: Cloud account access, server root/SSH access and application administrators
- Installation guidance: Provision the documented Cloudron VPS template in your account, complete domain and administrator setup, then install and operate the reviewed application package.
- Guidance source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
- Guidance reviewed: 2026-11-13


### VPS hardening

The provider recommends SSH hardening, firewall configuration and patching for VPS hosts. A preinstalled application template does not transfer these operating responsibilities away from the customer.
Source: https://www.hostinger.com/tutorials/vps-security/ (reviewed 2026-11-14).

The listings below have evidence for Hostinger. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## 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).






