What is Dalea?

A unified research orchestration platform for life science.

Dalea is a research orchestration platform for life science. It unifies the four software stacks every modern lab needs — an electronic lab notebook, a structured data warehouse, an inventory and sample tracker, and an AI assistant — into a single collaborative workspace with one identity, one permission model, and one audit trail.

The platform is built on the assumption that every result must be reproducible. Each protocol has explicit reagents, hazards and timing. Each measurement is anchored to the animal, plate well, or sample it came from. Each schema change carries an audit reason. Data is exportable in open formats and the platform is EU Data Act compliant and EU-hosted.

Why this exists

European BioPharma alone spends roughly €23 B per year on research that cannot be replicated. Critical experimental context — buffer recipes, assay timings, animal weights — lives in lab notebooks that nobody else can read, in spreadsheets on personal computers, or in tools whose vendors went out of business.

Dalea fixes this by giving every result a structured home from day one, then lets your team work in it like a notebook.

What you can do in a Dalea workspace

The single mental model

Everything in Dalea sits in one of these layers:

UserOrganizationWorkspaceProjectDocumentEnvironmentInventoryTemplate
Workspace

The data boundary. Documents, data and inventory all live in a workspace.

Example
IND-128 Discovery Team
Workspaces never share data with each other directly. Sharing happens by exporting through templates or marketplace packages.
The Dalea hierarchy. Click any node to see what lives there.

A workspace is the unit of collaboration and the data boundary. You can belong to many. Inside a workspace, work is organised into projects (a study, a campaign), which group documents, files and structured data. Tables, environments and inventory all live at the workspace level so they can be referenced from any document.

A concrete example

A typical pre-clinical IND-enabling team might run one Dalea workspace per programme:

  • Workspace "IND-128 Discovery Team"
  • Projects inside it: Lead optimisation, Mouse PK, Tox screen, IND submission
  • Environments: a shared In-vivo PK schema reused across studies
  • Inventory: freezer L-204, plus carousel-fed compound stock
  • Templates: an IACUC submission form locked to your institutional language

The same researcher may also belong to a "Method dev" workspace and a "Manuscripts" workspace — switching is one click in the sidebar.

What's next