Data as of Sep 18, 2026 · Based on 48 AI responses from ChatGPT Search and Google AI Mode · See how Parse measures this
Your brand can be here too.
If by **“design–make–test–analyze” (DMTA/DBTL)** you mean a platform that actually closes the loop between computational protein design, physical experimentation, and learning from assay results, the landscape is fairly concentrated. Platform / company | Design | Make / build | Test | Analyze / learn | Loop status ---…
If by “design–make–test–analyze” (DMTA/DBTL) you mean a platform that actually closes the loop between computational protein design, physical experimentation, and learning from assay results, the landscape is fairly concentrated.
| Platform / company | Design | Make / build | Test | Analyze / learn | Loop status |
|---|---|---|---|---|---|
| Cradle | AI sequence generation & optimization | Usually through customer's lab; integrated automation via partners | Customer wet lab / Ginkgo | Custom models retrained on experimental data | Strong software loop; can be physically closed with Ginkgo Cradle Cradle |
| Ginkgo Bioworks / Foundry | Design software + partners such as Cradle | Automated DNA/cell engineering | High-throughput assays | Data feeds subsequent design | Full physical DBTL foundry Cradle |
| **Generate:Biomedicines / Generate Platform | Generative protein design | In-house protein production | In-house measurement | Continuous learning from experimental data | Full closed loop, primarily for therapeutics Generate:Biomedicines Generate:Biomedicines |
| Arzeda | AI/physics-based protein design | Engineering/production workflows | Application-relevant testing | Iterative design-build-test-learn | Closed-loop industrial protein engineering Arzeda |
| **Data Powered Therapeutics (DPTX) | Computational protein design | Automated expression & purification | Automated biophysical characterization | Structured data retrains models | Explicit end-to-end closed loop DPTX |
| HemeAI | Protein foundation models + active learning | Automated wet lab | Functional/biophysical validation | Experimental data → Bayesian optimization | Closed loop, focused on industrial enzymes HemeAI |
| ProteusAI | ML/structure-based design | External lab | External experimental data | ML-guided directed evolution | Software covering the DBTL cycle; not an integrated wet lab Proteus AI |
| ProGene | Generative/predictive models | Primarily external | Validation workflows | Analyze & iterate | Computational loop; physical testing is separate ProGene |
There are really three categories:
These handle the design → data → model → next design loop, but the physical make/test step generally occurs in the customer's lab or through a partner. 2. Foundry / automation platforms
Here the differentiator is not necessarily the best protein-design model; it's the ability to physically execute large numbers of designs and return standardized experimental data. Cradle + Ginkgo is an explicit example of coupling AI protein design to automated testing and feeding the results back into the model. Cradle 3. Fully integrated protein-engineering companies
These are attempting to make the entire loop one system, rather than selling only the design software. Generate, for example, explicitly describes its platform as generate → build → measure → learn, with experimentation continuously training/refining the system.
One particularly interesting entrant is DPTX, because its stated architecture is unusually literal: automated expression → purification → stability/binding/developability assays → ML-ready data → next design.
If you're asking because you're mapping the competitive landscape for a new protein-engineering platform, I can also break these down by (a) AI design capability, (b) wet-lab automation, (c) assay breadth, (d) degree of autonomy, (e) customer-vs-internal use, and (f) therapeutic vs industrial focus.
The **Design-Make-Test-Analyze (DMTA)** —or **Design-Build-Test-Learn (DBTL)** —loop for protein engineering has shifted from manual, piecemeal lab work to **fully automated, AI-driven "lab-in-the-loop" platforms** . These systems integrate generative artificial intelligence, large language models (LLMs), robotic…
The Design-Make-Test-Analyze (DMTA) —or Design-Build-Test-Learn (DBTL) —loop for protein engineering has shifted from manual, piecemeal lab work to fully automated, AI-driven "lab-in-the-loop" platforms . These systems integrate generative artificial intelligence, large language models (LLMs), robotic biofoundries, and automated analytical assays.
The primary systems, architectures, and platforms executing this closed-loop cycle span academic/open-source pipelines, biofoundry integrations, and commercial enterprise solutions:
Would you like to explore how to set up an open-source software stack for the computational (Design/Analyze) portion, or are you more interested in the hardware/robotics side of automated biofoundries?
If by **“design–make–test–analyze”** you mean a genuinely iterative protein-engineering loop—where computational design proposes variants, the platform actually gets them built/tested, and experimental results feed the next design round—the landscape is still fairly small. ### Strongest examples -…
If by “design–make–test–analyze” you mean a genuinely iterative protein-engineering loop—where computational design proposes variants, the platform actually gets them built/tested, and experimental results feed the next design round—the landscape is still fairly small.
There are really three levels of “closed loop”:
| Type | Example | What actually happens |
|---|---|---|
| AI design + user experiments | Cradle | AI designs → customer lab tests → results go back into AI |
| AI + integrated/partner automated wet lab | Cradle + Ginkgo | Design → automated build/test → data → next design |
| Vertically integrated autonomous loop | Arzeda, Generate, DPTX, ZerothBIO | Design and experimental execution are being operated as one system |
There are also academic/self-driving-lab implementations. For example, Northwestern's DREAM Cloud Lab is an NSF-supported protein-engineering facility built specifically around an AI-driven DBTL cycle, using automated cell-free protein synthesis and functional characterization. Center for Synthetic Biology A 2024 research platform similarly demonstrated four automated protein-evolution rounds in 10 days using a protein language model + biofoundry + machine-learning feedback loop.
If you're asking because you're mapping the competitive landscape, I'd put Cradle, Ginkgo, Generate, Arzeda, DPTX, and ZerothBIO in the first tier to investigate. The interesting question isn't merely who uses AI for protein design, but who owns/controls the experimental loop and automatically turns each assay into the next design decision. That's a much smaller set.
Running the **Design-Make-Test-Analyze (DMTA)** loop—often referred to as **AI-driven lab-in-the-loop** or **self-driving laboratories** for protein engineering—requires tight integration between generative machine learning models and high-throughput automated wet…
Running the Design-Make-Test-Analyze (DMTA) loop—often referred to as AI-driven lab-in-the-loop or self-driving laboratories for protein engineering—requires tight integration between generative machine learning models and high-throughput automated wet labs.
Several commercial platforms, specialized biofoundries, and open-source/academic architectures execute this continuous loop:
Would you like to explore how to connect your own software models to an external testing foundry, or are you looking for details on specific assay types (like binding affinity vs. thermal stability) supported by these platforms?
`Several biotechnology companies and automated infrastructure providers` run closed-loop **Design-Make-Test-Analyze (DMTA)** (or Design-Make-Test-Learn) workflows for protein engineering. These platforms merge generative artificial intelligence (AI) with high-throughput robotics and automated wet-lab assays to iterate…
Several biotechnology companies and automated infrastructure providers run closed-loop Design-Make-Test-Analyze (DMTA) (or Design-Make-Test-Learn) workflows for protein engineering. These platforms merge generative artificial intelligence (AI) with high-throughput robotics and automated wet-lab assays to iterate rapidly on protein design.
Would you like to explore how automated cloud labs integrate with open-source protein design models , or focus on a specific therapeutic modality like antibodies versus enzymes?
The **design–make–test–analyze (DMTA)** loop in protein engineering is a closed-loop workflow where computational models propose protein variants (**design**), DNA/protein constructs are produced (**make**), experiments measure properties (**test**), and the results are used to guide the next design cycle…
The design–make–test–analyze (DMTA) loop in protein engineering is a closed-loop workflow where computational models propose protein variants (design), DNA/protein constructs are produced (make), experiments measure properties (test), and the results are used to guide the next design cycle (analyze/learn). It is closely related to the more common DBTL (Design–Build–Test–Learn) terminology.
Platforms that run some or all of this loop include:
| Platform | What part of the loop it covers | Notes |
|---|---|---|
| EvolutionaryScale | Design | Protein language models for generating and evaluating sequences (for example ESM-family models); typically paired with downstream experimental workflows. |
| Generate Biomedicines | Design → validation workflows | Builds generative AI systems for therapeutic protein design and experimental validation. |
| Insilico Medicine | AI-driven discovery workflows | Primarily drug discovery, with AI-guided molecular design and optimization capabilities. |
| Profluent | Design | Uses generative AI for protein engineering, including novel protein generation. |
| Cradle | Design → experimental iteration support | Provides ML tools intended to help scientists design improved proteins and integrate experimental feedback. |
| DPTX | Full loop | Connects computational protein design with automated expression, purification, characterization, and feedback into models. DPTX |
| Adaptyv Bio | Make → test → data return | Provides automated protein expression/testing infrastructure designed to feed results back into AI design cycles. Adaptyv Bio |
| OpenProtein.AI | Design → ML-guided iteration | A no-code platform giving researchers access to protein AI models and engineering workflows. MIT News |
| ProteusAI | Design → analyze/learn | Supports DBTL workflows including protein discovery, structure-based design, and ML-guided directed evolution. Proteus AI |
| ProGene | Design → analyze → iterate | Provides workflow building blocks for generation, prediction, validation, and optimization. Progene |
| Bigo.bio | Design → build → test → learn | Describes a closed-loop system combining generative design, ranking, wet-lab validation, and data return. Bigo.bio |
| RunLab | Design → rank → validate → learn | Combines generative design, scoring, wet-lab validation, and feedback loops for enzymes and binders. RunLab |
A useful way to categorize them:
These generate or rank candidate sequences:
These automate the physical loop:
These connect models, experiments, and feedback:
A caveat: a fully autonomous DMTA loop (AI designs → robots build → assays test → AI learns → repeat without much human intervention) is still emerging. Many commercial platforms currently cover only parts of the loop or integrate with external CROs/robotic labs rather than operating the entire stack internally.
Bigo.bio
Running the **Design-Make-Test-Analyze (DMTA)** —or **Design-Build-Test-Learn (DBTL)** —loop for protein engineering requires tightly coupling generative AI/machine learning with high-throughput laboratory automation. This "lab-in-the-loop" ecosystem bridges digital sequence/structure generation with physical…
Running the Design-Make-Test-Analyze (DMTA) —or Design-Build-Test-Learn (DBTL) —loop for protein engineering requires tightly coupling generative AI/machine learning with high-throughput laboratory automation. This "lab-in-the-loop" ecosystem bridges digital sequence/structure generation with physical synthesis, screening, and computational feedback.
The key technology platforms, biopharma infrastructures, and autonomous foundry systems driving these closed-loop cycles include:
If you are looking to assemble your own computational side of the loop rather than a full hardware foundry:
If you are looking to build or implement a specific loop, let me know:
If by **design–make–test–analyze** you mean a genuinely iterative protein-engineering loop—where experimental results feed back into the next round of sequence design—the landscape is fairly concentrated. ### Strongest fits - **Cradle** — Probably the clearest *software platform* example. You provide experimental…
If by design–make–test–analyze you mean a genuinely iterative protein-engineering loop—where experimental results feed back into the next round of sequence design—the landscape is fairly concentrated.
| Platform | Design | Make | Test | Analyze/learn | Customer runs loop? |
|---|---|---|---|---|---|
| Cradle | ✓ AI | Customer lab | Customer lab | ✓ AI | Yes, software-led |
| Generate | ✓ | ✓ | ✓ | ✓ | Yes, vertically integrated |
| Arzeda | ✓ | ✓/partners | ✓ | ✓ | Yes, integrated |
| Codexis | ✓ | ✓ | ✓ | ✓ | Yes, enzyme-focused |
| Pando | ✓ AI | ✓ | ✓ HTP | ✓ | Yes, vertically integrated |
| TeselaGen | ✓ | ✓ workflow | ✓ workflow | ✓ | Yes, orchestration/software |
| Profluent | ✓ | ✓ | ✓ | ✓ | Yes, but primarily platform/partnership |
| ProteusAI | ✓ | — | — | ✓ | Partially—software side |
One distinction matters: “AI protein design” ≠ “closed-loop protein engineering.” Companies such as EvolutionaryScale/ESM, NVIDIA/GenSLM-type systems, etc. can generate or predict proteins, but unless experimental results are systematically returned to the design algorithm, they aren't really running the full DBTL loop.
If you're asking this for competitive landscape / company diligence, I can also give you a more exhaustive 20–30 company map of protein-engineering DBTL platforms, classified by AI design, automated wet lab, assay type, closed-loop status, therapeutic vs enzyme focus, and whether it's SaaS vs outsourced R&D.
The **Design-Make-Test-Analyze (DMTA)** loop—often referred to as a "lab-in-the-loop" or self-driving lab workflow—is increasingly automated by combining generative artificial intelligence (AI) with robotic wet-lab…
The Design-Make-Test-Analyze (DMTA) loop—often referred to as a "lab-in-the-loop" or self-driving lab workflow—is increasingly automated by combining generative artificial intelligence (AI) with robotic wet-lab infrastructure.
Platforms executing this closed-loop protein engineering span software orchestration frameworks, integrated biopharma internal engines, and robotic biofoundries:
If you are looking for platforms for a specific project, let me know:
Mila
Yes. If by **“design–make–test–analyze”** you mean a genuinely iterative loop where experimental results automatically influence the next protein designs—not merely a protein-design model—there are several notable platforms. ### The strongest examples - **Cradle** — Probably one of the clearest commercial examples.…
Yes. If by “design–make–test–analyze” you mean a genuinely iterative loop where experimental results automatically influence the next protein designs—not merely a protein-design model—there are several notable platforms.
There are really three tiers here:
| Platform type | Design | Make | Test | Analyze/learn | Closed loop? |
|---|---|---|---|---|---|
| Cradle | AI | Partner/wet lab | Yes | Yes | Yes |
| Generate | Generative AI | In-house | In-house | Yes | Yes |
| Arzeda | AI + physics | Automated | Automated | AI agents | Yes |
| Imperagen | AI + physics | In-house | In-house | Yes | Yes |
| Ginkgo + Cradle | Cradle | Ginkgo | Ginkgo | Cradle | Yes |
| RunLab | Generative/structure-aware | In-house | In-house | Yes | Yes |
| ZerothBIO | AI | Cell-free | Functional assays | Yes | Yes |
| ProteusAI | ML | Mostly user lab | User lab | ML | Partially |
The last distinction matters: ProteusAI, for example, is an open-source software platform covering several stages of DBTL, but it isn't itself an autonomous wet-lab factory.
There is also an emerging academic ecosystem of self-driving protein-engineering labs. A 2026 review describes these as systems coupling automated library design, robotic transformation/expression, assays, and ML-driven decision-making into closed optimization loops.
If you're mapping the competitive landscape, I'd put Cradle, Generate, Arzeda, Imperagen, Ginkgo/Cradle, and RunLab in the “commercial closed-loop protein engineering” bucket, with ProteusAI and academic biofoundry systems in the “software/research infrastructure” bucket.