☰

Ethris GmbH

Digital platform for mRNA scale-up

An mRNA therapeutics company building lab data capture, a CDMO data platform, and a digital twin for scale-up

Industry
mRNA Therapeutics
Headquarters
Planegg-Martinsried, Germany
Public information as of
January 2026

A4BEE prepared this analysis from publicly available sources. It reflects our own reading of Ethris GmbH's published strategy and is not endorsed by, or produced in cooperation with, Ethris GmbH. Company website

Strategic priorities

Ethris is a German mRNA therapeutics company developing ETH47 through Phase 2a trials for respiratory viral infections and asthma, using its proprietary SNIM RNA and SNaP LNP delivery platforms. The company has R&D headquarters in Planegg-Martinsried near Munich, a spray-drying operation in Bend, Oregon, and manufacturing partnerships with Thermo Fisher Scientific and Lonza. Its room-temperature stable mRNA formulation programme, including spray-drying technology, targets the cold-chain limitation that has constrained mRNA distribution in emerging markets.

The immediate challenge is scaling HPLC-free mRNA production from 1-litre laboratory batches to 100-litre GMP batches across a distributed CDMO network, while maintaining the reaction kinetics and product quality that Phase 1 data demonstrated. This means process knowledge that sits in Munich has to travel to Oregon and to Thermo Fisher's facilities in a form that the receiving site can act on without re-interpretation.

The digital gap mirrors the organisational one. Laboratory equipment in Munich uses RS-232 and other legacy interfaces that require manual data transcription. Manufacturing data moves between Munich, Oregon, Lonza and Thermo Fisher through uncoordinated handoffs. The spray-drying formulation work — stabilising mRNA within lipid nanoparticles for nebulisation — relies on iterative wet-lab experimentation because no predictive model of the process exists yet. ETH47's progress into Phase 2a is adding GAMP5 data integrity requirements on top of all of this.

Challenges we see

  • Operations Manufacturing

    Scaling mRNA bioreactor production from 1 litre to 100 litres

    Ethris must scale its HPLC-free mRNA production from 1-litre laboratory batches to 100-litre GMP batches across Thermo Fisher Scientific and Lonza. In vitro transcription reaction efficiency declines outside narrow temporal windows, and at 100-litre scale the cost of a failed polishing step for dsRNA by-product removal is substantially higher than at bench scale.

    At laboratory scale a scientist can intervene in time. At 100-litre GMP scale, the intervention window is shorter and the consequence of missing it is a batch worth a fraction of what it would have been worth if the yield had been maintained.

  • Digital Integration

    Getting Munich, Oregon and CDMO data into one view

    Manufacturing data moves between Munich headquarters, Lonza's Bend facility and Thermo Fisher's global network through uncoordinated handoffs. Each site generates data in its own structure, and the handoff between sites is curated manually — described internally as a relay race, where information is passed from one team to the next rather than flowing continuously.

    When a process deviation occurs at a CDMO site, Munich has to wait for the next handoff to learn about it. The time between a deviation and Munich's awareness of it is set by the relay race schedule, not by the urgency of the event.

  • Operations Manufacturing

    Reducing wet-lab experimentation for LNP spray-drying formulation

    Stabilising mRNA within lipid nanoparticles for nebulisation delivery requires a precise particle size window. The spray-drying parameters that produce that window in a GMP environment are found by iterative experimentation, and each GMP batch is expensive relative to a laboratory run. A predictive model of the spray-drying process does not yet exist.

    Without a model of how temperature and pressure affect particle size and mRNA integrity during spray-drying, each GMP batch is an experiment rather than a confirmation. The cost of that uncertainty is paid on every batch run until the operating window is defined.

  • Compliance Regulatory

    Meeting GAMP5 data integrity requirements for Phase 2a

    ETH47's progression into Phase 2a brings heightened regulatory scrutiny, including requirements for GAMP5-compliant data integrity across any cloud-based systems used in the trial. Current paper-based processes and disconnected laboratory equipment do not provide the continuous audit trail that regulators expect.

    An audit trail that depends on paper records and manual transcription has gaps — in the literal sense of missing data points and in the regulatory sense of missing evidence. Those gaps become inspection findings when a regulatory reviewer asks for the batch record.

  • Digital Cybersecurity

    Protecting SNIM RNA sequence data as equipment connects to external networks

    The SNIM RNA sequences are Ethris's core intellectual property. Connecting laboratory equipment to cloud analytics platforms and external CDMO networks is necessary for Industry 4.0 capabilities, but brings those sequences into contact with external network infrastructure that was not designed with genetic IP protection as a primary requirement.

    A perimeter-based security model — where everything inside the firewall is trusted — does not account for a CDMO network that is shared across multiple clients. Sequence data that leaves Munich's network to reach Lonza or Thermo Fisher passes through infrastructure that Ethris does not control.

Opportunities, by urgency and business impact

Each bubble is one opportunity, numbered to match the list below. Further right means it bites sooner; higher means a bigger effect on the business. A bigger bubble means a bigger implementation effort.

Source: A4BEE analysis of public sources

  1. Automated data capture from laboratory instruments

    Munich laboratory equipment — bioreactors, scales, pumps — uses RS-232 and other legacy physical interfaces that require manual transcription by technicians. Each transcription is a time cost and a potential source of human error.

    Deploy automated data capture from all laboratory instruments using OPC UA or MQTT, eliminating manual transcription and ensuring 100 percent data integrity from source to record.

    • A4BEE Lab Digitalization assessment
    • Ethris internal technical documentation

  2. Unified data platform across CDMO partners

    Manufacturing data moves between Munich, Lonza and Thermo Fisher through a relay race of uncoordinated handoffs. Process deviations at a CDMO site are not visible in Munich until the next scheduled data transfer.

    Implement a unified Industrial Data Platform that serves as the single source of truth for CMC data across all global manufacturing partners, enabling real-time batch visibility and coordinated process control.

    • Ethris CEO statement on Thermo Fisher collaboration
    • Lonza manufacturing partnership announcement

  3. Digital twin for spray-drying formulation

    Stabilising mRNA in lipid nanoparticles for nebulisation requires iterative wet-lab experimentation to find the correct spray-drying parameters. Each GMP batch run is expensive, and the experimentation cycle delays the formulation programme.

    Deploy a digital twin that simulates spray-drying behaviour — particle size, mRNA integrity, temperature tolerance — from instrumented equipment data, so the optimal operating window is found in simulation before being confirmed in a GMP batch.

    • Ethris CEO statement on LNP nebulisation challenge

  4. MTP and OPC UA standards for vendor-agnostic manufacturing

    Each CDMO partner uses proprietary hardware and software interfaces. Process recipes that work at Munich have to be substantially re-engineered at Lonza or Thermo Fisher, and the same problem applies in reverse when transferring a process back.

    Implement MTP and OPC UA standards to create vendor-agnostic equipment interfaces, so process recipes move between sites as recipes rather than as re-engineering projects.

    • Thermo Fisher/Ethris collaboration context

  5. Zero Trust architecture for genetic IP protection

    Legacy laboratory equipment connects to cloud analytics and external CDMO networks without a security model that accounts for the fact that those external networks are not under Ethris's control.

    Implement Zero Trust security architecture — identity-based access control for every data access request — so that SNIM RNA sequence data is protected regardless of which network it traverses.

    • NIS2 compliance requirements for critical infrastructure
    • Ethris Industry 4.0 connectivity roadmap

What we'd propose

  • Digital Lab

    Digital lab integration for Munich R&D headquarters

    Deploy comprehensive laboratory equipment connectivity and automated data capture across Ethris's Planegg-Martinsried site, replacing manual RS-232 transcription with OPC UA or MQTT-based real-time data streaming from all instruments.

    • Equipment connectivity layer

      OPC UA/MQTT integration for all lab devices

      Connect bioreactors, scales, pumps and analytical instruments using standardised protocols, replacing manual RS-232 data extraction with automated real-time streaming to the data platform.

    • Paperless process workflows and electronic batch records

      ALCOA+ compliant digital records from instrument up

      Implement digital SOPs and electronic batch records that populate automatically from instrument data, ensuring data integrity and audit trail completeness without manual transcription at any step.

    • Legacy equipment smart sensor retrofit

      Connect existing equipment without replacement

      Add connectivity to existing bioreactors and analytical devices without requiring equipment replacement, delivering immediate data integrity improvements and reducing the manual transcription burden for instruments that cannot be upgraded to modern interfaces.

    • Data integrity improves because data moves from instrument to record without a human in the middle.
    • Scientists spend time on research instead of transcription.
    • The Munich laboratory is audit-ready for Phase 2a regulatory review from day one of the system going live.

    We've done this before

    See how we do Digital Lab
  • Enterprise AI

    Industrial data platform for global CDMO orchestration

    Build an ontology-based unified data platform that serves as the single source of truth for CMC data across Munich, Lonza and Thermo Fisher — ingesting process data from each partner's systems and presenting a harmonised view that enables cross-site analytics and comparison.

    • Unified CDMO data lakehouse

      One data platform across all manufacturing partners

      Implement a centralised platform that ingests data from all manufacturing partners through standardised APIs and ontologies, providing real-time visibility into batch progress, quality parameters and supply chain status for Munich headquarters.

    • Semantic process harmonisation

      Cross-site analytics despite different CDMO systems

      Use ontologies to map physical production parameters from each CDMO's systems to universal business classes, enabling cross-site analytics and direct comparison of batch outcomes regardless of which partner produced them.

    • CDMO handoff acceleration

      Process data moves continuously, not on a schedule

      Replace the relay-race handoff model with continuous data flow from each CDMO site to the unified platform, so that a process deviation at Lonza Bend is visible in Munich within minutes rather than at the next scheduled data transfer.

    • Munich has real-time visibility into what is happening at Lonza and Thermo Fisher, not a retrospective report.
    • CMC data for regulatory submissions is assembled from one platform rather than reconciled from three separate data exports.
    • Process knowledge from Munich transfers to Oregon and back without requiring a complete re-interpretation at each handoff.

    We've done this before

    See how we do Enterprise AI
  • Digital Lab

    Digital twin platform for spray-drying formulation

    Deploy predictive simulation capability for the Bend, Oregon spray-drying facility, building a digital twin that learns from instrumented equipment data to predict LNP particle size and mRNA integrity from spray-drying parameters — finding the operating window in simulation before confirming it in an expensive GMP batch.

    • Spray-dryer instrument data capture

      Temperature, pressure and flow data streamed in real time

      Instrument the spray-drying equipment to capture temperature, pressure, flow rates and environmental conditions in real time, building the historical dataset needed to train the predictive model.

    • Predictive particle size and integrity model

      AI/ML model for formulation operating window

      Build models that predict LNP particle size distribution and mRNA integrity based on spray-drying process parameters, identifying the optimal operating window and the boundaries beyond which the formulation fails.

    • Virtual batch simulation

      Formulation hypotheses tested before GMP commitment

      Run virtual experiments that test formulation hypotheses against the model before committing to a GMP batch, reducing wet-lab iteration cycles and the cost of finding the operating window by experimentation.

    • The formulation operating window is found in simulation before expensive GMP batches are committed.
    • Each GMP batch run is a confirmation of the model rather than another experiment.
    • The spray-drying programme is de-risked before ETH47 reaches Phase 2b, where regulatory scrutiny of the manufacturing process increases.

    We've done this before

    See how we do Digital Lab
  • Digital CDMO

    MTP standardisation for vendor-agnostic CDMO interfaces

    Implement Module Type Package standards and OPC UA connectivity across Ethris's equipment interfaces to create a Plug and Produce modular architecture that eliminates vendor lock-in with CDMO partners and enables process recipes to transfer between sites without re-engineering.

    • MTP library development

      Standardised automation modules for all equipment

      Develop MTP-compliant automation modules that abstract equipment-specific control logic into reusable process unit descriptions, enabling the same control sequence to run on different hardware at different CDMO sites.

    • OPC UA communication backbone

      Vendor-neutral data exchange with all partners

      Implement OPC UA as the standard communication backbone between Munich protocols and each CDMO's execution systems, ensuring that data exchange is governed by a standard rather than by a vendor's proprietary interface.

    • Tech transfer acceleration framework

      Process recipes move as recipes, not re-engineering projects

      Create process recipes documented to MTP standards that can be transferred between manufacturing sites without extensive reprogramming, reducing the tech transfer timeline and the validation burden at each receiving site.

    • A process recipe developed at Munich transfers to Lonza and Thermo Fisher as a configuration exercise rather than a re-engineering project.
    • The validation burden at each receiving site is reduced because the MTP package includes the equipment abstraction needed by the regulator.
    • Ethris is not locked into any single CDMO because the interfaces are standardised.

    We've done this before

    See how we do Digital CDMO
  • Digital CDMO

    Zero Trust cybersecurity for genetic IP protection

    Implement identity-based Zero Trust security architecture that protects proprietary SNIM RNA sequences as laboratory equipment connects to cloud analytics and external CDMO networks — ensuring NIS2-compliant, vendor-agnostic secure data transmission without trust being placed in any network segment by default.

    • Identity-based access control

      Every data access request verified, regardless of network

      Replace perimeter-based security with identity verification for every data access request, so that SNIM RNA sequence data is protected regardless of which network segment it traverses between Munich and the CDMO.

    • Secure OT gateway architecture

      Protected lab-to-cloud connectivity

      Deploy secure gateways that isolate sensitive R&D equipment while enabling controlled, auditable data flow to cloud analytics platforms and CDMO partners — protecting the genetic IP without blocking the Industry 4.0 connectivity the programme needs.

    • NIS2 compliance framework

      Regulatory-ready security posture for critical infrastructure

      Implement security controls aligned with NIS2 requirements for critical infrastructure, ensuring compliance as Ethris scales manufacturing operations and the regulatory surface expands with the clinical programme.

    • SNIM RNA sequence data is protected end-to-end, regardless of which CDMO network it traverses.
    • The security architecture satisfies NIS2 requirements without blocking the cloud analytics and CDMO connectivity that the digital programme requires.
    • Every data access is auditable, which satisfies both the security team and the regulatory affairs team.

    We've done this before

    See how we do Digital CDMO

Digital maturity: today and target

Scored out of 100 across six dimensions. The target is what Ethris GmbH's own published ambition implies — not a perfect score.

Source: A4BEE analysis of public sources
Lab Equipment Connectivity 35 → 85
Laboratory instruments in Munich use RS-232 and other legacy interfaces that require manual data transcription. No automated data capture layer exists between the instruments and the systems that hold the process record.
Data Integration Across CDMOs 25 → 90
Data moves between Munich, Lonza and Thermo Fisher through a relay race of manual handoffs. No unified data platform connects the three manufacturing locations, so cross-site visibility is retrospective and mediated by scheduled data transfers.
Digital Twin Capability 20 → 75
No predictive model of the spray-drying process exists. Formulation development relies on iterative wet-lab experimentation at each parameter setting, and the cost of finding the operating window is paid on GMP batches.
Manufacturing Standards 30 → 80
Equipment interfaces are governed by each CDMO partner's proprietary standards. Process recipes do not travel between sites as reusable configurations — each tech transfer requires substantial re-engineering.
Cybersecurity Posture 40 → 85
Basic IT security exists, but OT environments — laboratory equipment and manufacturing systems — were not designed for external network connectivity. The Zero Trust architecture needed to protect genetic IP in a multi-partner CDMO environment is not yet in place.
Closed-Loop Process Control 30 → 70
Bioprocess control loops require human intervention at many steps. Automated sampling, in-line analysis and closed-loop parameter adjustment are not yet operational at Munich, and the CDMO sites are at different stages again.

Check this yourself

Our Service Portal has free self-assessments and market comparisons. These are the ones that line up with what we've read above — no sales call required.

Think we've read this right?

Talk to us

Related reading

This is an independent analysis prepared by A4BEE from publicly available information as of January 2026. It reflects A4BEE's own interpretation and opinion, is not affiliated with, endorsed by, or verified with Ethris GmbH, and may be incomplete or inaccurate. All company names and trademarks are the property of their respective owners. To request a correction or removal, contact [email protected].