eLabFTW

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

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Docker / Compose

  2. 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
  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Hostinger VPS ↗ · 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 methodDocker / Compose
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

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.

5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Self-hosted eLabFTW SAML login; LDAP, local login and middleware-header paths are distinct · Source ↗ · Authentication and account policies ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

eLabFTW version-6 container installation path; provision the host and production operations separately · Source ↗ · Deployment artifact ↗ (Official elabctl/configuration download URL is unversioned; guide branch release/6.0 is moving) · Runtime and database prerequisites ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

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.

eLabFTW application, database and persistent experiment data; container/package allowances are not whole-system HA sizing · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

eLabFTW; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

eLabFTW upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 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.

Scope & considerations

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.

Community & 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.

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.

Compare within Document management

  • Adobe Experience Manager 6.5 Forms (Correspondence Management)Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • Alfresco Content Services + Governance ServicesCustomer-operated content and records management with retention and record-declaration workflows.
    • AWS
    Customer-operated · Open Source / Open Core
  • Apache JSPWikiApache file-based wiki for documentation and knowledge content.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • DocassembleSelf-hosted guided interviews and automated document assembly.
    • AWS
    • Hostinger
    Customer-operated · Open Source / Open Core
  • DocspellSelf-hosted document ingestion, OCR, classification and search.
    • Railway
    • Hostinger
    Customer-operated · Open Source / Open Core
  • DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
    • Azure
    Customer-operated · Commercial Only
  • Fedora RepositoryOpen-source preservation repository with an AWS Terraform deployment.
    • AWS
    Customer-operated · Open Source / Open Core

Showing 8 of 41 other listings in Document management. These products address related workflows; read their category-fit notes before comparing scope. See all of Document management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Hostinger VPS ↗ · Hostinger

      Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory