Munich’s mbiomics closes €30M to develop live bacterial product


The Munich techbio company is developing a live bacterial product designed to enhance immune checkpoint inhibitor response in advanced melanoma, with a Phase 1B study planned for 2027


mbiomics GmbH, a Munich-based techbio company developing microbiome-based therapeutics, has completed the third and final closing of its Series A funding round, bringing the total raised to €30 million.

The latest €12 million tranche was provided by existing investors MIG Fonds and Bayern Kapital, and marks the conclusion of a round that began in March 2023.

The capital will fund two near-term priorities: strengthening the IND-enabling pharmacological data package for the company’s lead candidate MBX-116, and accelerating the GMP-grade manufacturing development required to produce it at the clinical scale needed for human trials. The goal is a Phase 1B study in second-line advanced melanoma, planned to begin in 2027.

“While the clinical potential of the gut microbiome is well understood, transforming microbiome-based therapeutics into a scalable product has remained a significant engineering challenge,” said Dr. Johannes B. Woehrstein, CEO and co-founder of mbiomics.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

“At mbiomics, we are solving this challenge by building the full technology stack for the design, analysis, screening, and manufacturing of complex microbial consortia.”

Founded in Munich in 2020 by Woehrstein, Dr. Markus Rinecker, and Dr. Laura Figulla, mbiomics sits at the intersection of microbiology, AI-driven drug design, and precision medicine.

Its core product class is Live Biotherapeutic Products (LBPs), oral therapeutics composed of defined combinations of live bacterial strains, delivered in a pharmaceutical-grade format.

The distinction from earlier-generation microbiome interventions matters: faecal microbiota transplants (FMTs) have demonstrated clinical efficacy across multiple conditions but are inherently variable, non-standardised, and difficult to manufacture at scale. mbiomics’ platform is designed to replace FMT’s empirical variability with a rationally designed, reproducible product.

The platform combines AI and machine-learning-driven consortia design, proprietary high-resolution analytical technology, and large-consortium co-cultivation and screening capabilities.

The AI layer is used not just to identify candidate bacterial strains but to design the specific combination, the consortia, most likely to produce a defined therapeutic effect in a defined patient population.

This approach to rational consortia design, rather than single-strain probiotics or empirical transplants, is where mbiomics positions itself as a step-change from what came before it.

mbiomics’ lead clinical target, MBX-116 as a co-therapy alongside immune checkpoint inhibitors in second-line advanced melanoma, is grounded in a well-established but still-developing body of clinical evidence.

The gut microbiome modulates the immune system through multiple mechanisms: microbial metabolites, including short-chain fatty acids and tryptophan-derived compounds, regulate immune cell activation, dendritic cell activity, and the development of regulatory T cells, collectively shaping whether the immune system mounts a strong enough anti-tumour response.

Clinically, the relationship between microbiome composition and checkpoint inhibitor response has been documented in several studies. A landmark trial by Routy et al. found that FMT from ICI-responsive donors significantly improved outcomes in patients with refractory melanoma, with objective response rates reaching 65% in some cohorts.

Conversely, patients who had received broad-spectrum antibiotics within 30 days of starting checkpoint inhibitor therapy, which disrupts the gut microbiome, consistently showed worse outcomes across multiple tumour types.

Specific bacterial taxa, including Akkermansia muciniphila and Faecalibacterium prausnitzii, have been repeatedly identified as enriched in ICI responders and mechanistically linked to enhanced effector T cell activity.

The €30 million total is relatively modest by the standards of late-preclinical biotech rounds, but mbiomics is an IND-stage company: it is still completing the pharmacological data package required to file an Investigational New Drug application with regulators.

The Phase 1B trial target of 2027 gives the company approximately 18 months from now to reach IND submission and trial initiation, an achievable timeline for a company at this stage if GMP manufacturing comes together on schedule.

Beyond oncology, mbiomics has described a broader pipeline of microbiome-based therapeutics targeting indications including autoimmune and neurodegenerative diseases, indications where the gut–brain axis and gut–immune axis connections have generated increasing research interest but where no therapeutic-grade LBP has yet reached late-stage clinical development.

If the company pursues those indications independently or in partnership will likely be shaped by the results of the melanoma trial.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.

A lot of vibe “coders” are really just prompt typers

And they’ve never touched a line of code

An AI robot using a computer with a prompt field on the screen. Credit: Lucas Gouveia / How-To Geek

Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.

The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.

Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.

Anyone can vibe code a prototype

But you really need to know what you’re doing to build for the long haul

For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.

Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.

Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.

I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.

It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.

Vibe coders often jump from app to app without thinking of longevity

The app was a weekend project, after all

A relaxed man lounging on an orange beanbag watches as a friendly yellow robot works on a laptop for him, while multiple red exclamation-mark warning icons float around them. Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock

I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?

My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.

If a vibe coder’s only goal is to build apps in short amounts of time so they can brag about how fast they built the app, they likely aren’t going to take the time to fix little things like that.

I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.


Anyone can be a vibe coder, but not all vibe coders are developers

“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.

By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.

I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.



Source link