Skip to content

Open Enzyme Team

The Open Enzyme project is currently a solo effort by Brian Abent. Three collaborator roles are actively being recruited — each would address a critical question the project needs answered. Their expertise maps directly to the biological, engineering, and translational challenges of the OE platform mission, scoped at the platform level (chokepoint-first, chassis-second) rather than at the engineered-koji track specifically. The In Vivo Validation, Pharma Translation, and Innate Immune Safety roles apply to any intervention OE surfaces — koji-engineered cassettes, chassis-pending interventions (chassis-pending-interventions.md), and discovery-engine outputs alike.

Brian Abent — Platform & Engineering

Role: Founder, Platform Design, Engineering Background: CTO, non-scientist, systems thinker Current work: Building Alma.casa (AI real estate), raising seed funding

Why He's Here

Brian has gout — a uricase deficiency — and got tired of waiting for the system to solve it. His engineering background (not a biology background) drives the platform thinking: how do you make this reproducible, documentable, and accessible to non-scientists? How do you package biological solutions not as one-off experiments but as a platform others can fork, modify, and contribute to?

Critical Questions He Answers

  • How do we make engineered organism protocols accessible to people without formal biology training?
  • What's the minimum viable documentation needed for reproducibility?
  • How does this scale from personal project to community platform?
  • What's the path from home fermentation to commercial viability (if desired)?

Contribution to Open Enzyme

  • Platform architecture and philosophy (open source, GRAS organisms, accessibility)
  • Koji fermentation protocol development (personal experimentation)
  • Integration of gout research into actionable framework
  • Documentation and knowledge synthesis

Collaborator Roles (Actively Recruiting)

The project is seeking PhD-level collaborators in three complementary domains. Each role answers a question the platform cannot answer alone. No names are published here until collaborators have formally joined.

Wet-lab partner evaluation — Ginkgo Cloud Lab (2026-05-13): Brian probed Ginkgo Bioworks' Cloud Lab via their EstiMate sales bot on 2026-05-12. Two offers surfaced: (1) Cell-Free Protein Expression Validation at $39/protein — confirms a designed sequence produces folded polypeptide in cell-free lysate, ~5–10 day turnaround. This is a real fail-fast pre-gate for uricase variants (E. coli-lysate-compatible fold) but a weak test for DAF/CD55 SCR1-4 (glycoprotein, disulfide-rich). (2) A 96-construct S. cerevisiae strain-engineering campaign at ≈$2,340 total (≈$24.38/sample) — almost certainly a lead-magnet teaser, not a real quote. The cell-free pre-gate complements the community-college / grad-student path (different gates: cell-free answers "does the sequence produce a folded protein at all?"; the CC path answers "does it secrete from a fungal host in a real fermentation context?"). See ginkgo-cloud-lab-evaluation.md for full evaluation. (source: ginkgo-cloud-lab-evaluation.md)

Role 1 — Gut Microbiome & In Vivo Validation

Expertise needed: Gut microbiome dynamics, gnotobiotic (germ-free) animal models, in vivo validation of engineered microbes, 16S sequencing and metabolomics interpretation.

Why the project needs this: The gut is a chaotic ecosystem, and predicting how an engineered microbe will behave there is nearly impossible without proper animal models. Gnotobiotic validation is essential for answering the most critical biological question: will an engineered strain survive and function in the real human gut?

Critical Questions This Role Would Answer

  • Will an engineered uricase-producing organism establish a stable colonization in the murine or human gut?
  • How does it interact with existing microbiota (competition, synergy, displacement)?
  • Does the uricase enzyme remain active and functional when expressed in vivo?
  • What are the potential unintended microbial shifts that could result from introducing an engineered strain?
  • How do gnotobiotic validation experiments look, and what are the regulatory implications?

Potential Contributions

  • In vivo validation protocols for engineered strains
  • Microbiome dynamics and integration expertise
  • Gnotobiotic animal study design and interpretation
  • Guidance on regulatory considerations for live biotherapeutic products

Role 2 — Pharma Translation & Regulatory Strategy

Expertise needed: NF-κB and intestinal epithelial signaling, pharmaceutical development experience, regulatory pathway mapping (FDA, IND, clinical development), safety/efficacy frameworks.

Why the project needs this: Open Enzyme aims to build something accessible, but it operates in a space where FDA, clinical trial design, and safety standards are not irrelevant — they're just approached differently than traditional pharma. This role is the bridge between academic research and pharmaceutical-grade standards.

Critical Questions This Role Would Answer

  • What are the inflammatory signaling implications of expressing uricase in the gut?
  • Could the engineered organism trigger unexpected NF-κB activation or immune responses?
  • What's the regulatory landscape for live biotherapeutic products?
  • At what point does a citizen-science project need to transition to clinical-development standards?
  • How do we ensure engineered strains don't create new epithelial pathology?

Potential Contributions

  • Inflammatory signaling assessment of engineered strains
  • Safety and efficacy standards framework
  • Regulatory pathway mapping (FDA, IND, clinical development)
  • Guidance on what data is "clinically sufficient" vs. "academically interesting"

Role 3 — Innate Immune Safety

Expertise needed: TLR signaling (especially TLR5), innate immune responses in gut epithelium, bacterial–host interactions, PAMP and epitope analysis.

Why the project needs this: Every bacterium has pathogen-associated molecular patterns (PAMPs) — flagellin, LPS, peptidoglycans — that the innate immune system recognizes via toll-like receptors (TLRs). Even GRAS organisms can trigger these signals. This role ensures engineered strains don't create new, unexpected immunogenic epitopes or aberrant PAMP signaling.

Critical Questions This Role Would Answer

  • Will an engineered E. coli Nissle or S. cerevisiae expressing uricase trigger TLR5 or other innate immune responses?
  • Could genetic modifications create new epitopes recognized as pathogenic?
  • Is there a risk of chronic immune activation from the engineered organism?
  • How do we design strains that "blend in" immunologically with normal microbiota?
  • What safety markers should we monitor (fecal calprotectin, serum cytokines, etc.)?

Potential Contributions

  • Immunological safety assessment of engineered strains
  • PAMP and epitope analysis
  • Immune-marker monitoring protocols
  • Guidance on preventing unexpected immune activation

How the Roles Would Map to Project Needs

Project Question Role Expertise
How do we make this reproducible? Founder Engineering, documentation, platform design
Will it work in the real gut? Role 1 Gnotobiotic models, microbiome dynamics
Is it safe? Role 3 Innate immune responses, PAMP signaling
Where's the regulatory path? Role 2 Pharma translation, clinical development
How does it affect inflammation? Roles 2 + 3 NF-κB signaling + immune safety
What's the go/no-go decision point? Role 2 Clinical development readiness

Proposed Division of Labor (once filled)

Founder (current — sole team member)

  • Day-to-day: Platform architecture, documentation, protocol development, koji fermentation experiments
  • Interface: Primary point of contact for project vision, open-source strategy
  • Decisions: Platform scope, accessibility standards, what counts as "complete"

Role 1 — Gut Microbiome & In Vivo Validation

  • Would own: Designing gnotobiotic studies, microbiome sequencing analysis, in vivo validation planning
  • Interface: Germ-free animal core operations, microbiome analysis protocols
  • Decisions: What animal models to use, what microbiota questions need answering, go/no-go for in vivo studies

Role 2 — Pharma Translation & Regulatory Strategy

  • Would own: Reviewing safety and efficacy frameworks, mapping regulatory requirements, pharma-development consultation
  • Interface: FDA precedents, clinical development pathways, safety–efficacy trade-offs
  • Decisions: What safety data is necessary for clinical translation, when to involve regulators, go/no-go for human trials

Role 3 — Innate Immune Safety

  • Would own: Immunological risk assessment, PAMP analysis, immune-marker protocol design
  • Interface: TLR signaling literature, epitope prediction, immune activation pathways
  • Decisions: Acceptability of immune response levels, safety margins for genetic modifications, go/no-go for immune safety

Why This Team Structure Would Work

Non-overlapping expertise with strategic overlap:

  • Founder: Systems thinker, not a biologist — forces clarity and accessibility
  • Role 1: Microbiome specialist — owns the "will it survive in vivo?" question
  • Role 2: Translational expert — answers "what does clinical development look like?"
  • Role 3: Immune safety specialist — ensures we're not creating immunological problems

Clear decision-making: Each role owns a critical domain (safety, efficacy, microbiome, translation), making decisions transparent and preventing scope creep.

Key Insight

The strength of this intended team is complementary expertise, not overlapping expertise. The founder brings the engineering clarity that prevents research from becoming self-referential. The three collaborator roles would bring domain mastery in the specific biological questions that matter (microbiome, safety, translation) and the infrastructure to move from concept to validation to potential clinical application.

No role is a generalist. Each owns a critical question. Together, they can answer: "Can an engineered food-safe organism produce therapeutic enzymes safely, effectively, and in a manner accessible to patients?" Recruiting these collaborators is one of the project's highest priorities.

Last updated: April 2026