Investor082’s post is a perfect example of someone pretending to understand regulatory science while misrepresenting its structure. The claim that Northwest Biotherapeutics’ MAA could not possibly be delayed by manufacturing or volume constraints is not just misleading, it shows a fundamental misunderstanding of what DCVax actually is.
This is not a monoclonal antibody. It is not a pill. It is not a generic infusion you pull off a shelf. DCVax is a personalized cell therapy. Each patient’s immune system is trained using their own cells. The therapy is not something applied after manufacturing. The therapy is the manufacturing.
Imagine trying to patent a violin by claiming the shape alone has healing value. That would never hold up. But if you develop a precise method for selecting the wood, carving the body, and tuning the structure to produce a distinct resonance, that method can be patented because the process is the instrument. That is the distinction.
That is how DCVax was patented. Not as a static substance, but as a defined method: taking a patient’s monocytes, maturing them into dendritic cells, loading them with tumor antigens, and preparing them for therapeutic use. The patent protection was granted because the method itself delivers the therapeutic effect. That method is the therapy.
This is not some abstract regulatory theory. The FDA and MHRA treat autologous cell therapies as process based interventions. That is why manufacturing validation is not a formality. It is the core of the submission. When regulators review DCVax, they are not evaluating a finished drug product on a shelf. They are evaluating the entire chain from identity and custody to antigen loading, viability thresholds, maturation profiles, sterility assurance, and cryopreservation conditions. Flaskworks and Advent are not side notes. They are part of the architecture being approved.
Investor082 claims that suggesting a volume based delay is “total quackery.” But the example they use, KITE’s initial manufacturing limits post approval, actually confirms the point.
Kite Pharma received FDA approval for Yescarta in 2017. Yescarta, like DCVax, is an autologous cell therapy, individualized and complex. At the time of approval, Kite could only produce enough product to treat roughly 100 patients in the first year. The FDA still approved it. Not because that volume was acceptable as a commercial launch, but because the process was validated. The agency was satisfied that the manufacturing system was safe, reproducible, and ready to scale with time. That is what mattered.
The FDA’s 2018 guidance on Chemistry, Manufacturing, and Controls made that point even more explicit. As stated directly:
“For autologous cell-based products, the manufacturing process is generally scaled out (i.e., increasing the number of batches manufactured) rather than scaled up… You are not expected to demonstrate commercial-scale manufacturing at the IND or early clinical stage.”
And more critically:
“The focus should be on demonstrating control and consistency of the manufacturing process, even if only at the clinical scale, to support later comparability and expansion.”
This is the regulatory posture DCVax fits precisely. The Kite example does not refute this logic. It proves it. The FDA approved Yescarta not because of how many they could treat, but because of how confidently they could treat even one. That is the exact same regulatory standard being applied to DCVax. The precedent being cited, ironically, supports our case, not theirs.
In the UK, the same logic applies. The MHRA’s Innovation Strategy, the SI 2023 No. 87 legal framework, and the real world data integration reforms are all designed for therapies like DCVax, individualized, process defined, and outside traditional mass production logic. These programs exist because approval in this space is no longer tied to commercial batch size. It is tied to process fidelity.
Flaskworks fits directly into that model. It does not sidestep GMP. It automates key components of the manufacturing process within GMP. It operates inside ISO 7 cleanrooms. It does not reduce regulatory burden. It enforces consistency. The point is not to replace oversight, but to make that oversight repeatable so DCVax can be produced at multiple sites, in multiple jurisdictions, under the same high standards that define the initial approval.
The MAA itself rests on Advent’s facility, already licensed, already inspected, already manufacturing product under the UK’s Specials framework. Flaskworks will carry that process forward into additional locations. It is not a condition for approval. It is the tool that supports expansion once approval is granted.
Investor082’s claim that Flaskworks is the reason for the delay ignores the fundamentals. Flaskworks is a post approval scale solution. It does not block the application. The MAA is already under review, based on validated systems that are live and in use today.
DCVax is not being held up because of volume. It is being evaluated based on how its therapy is made, because in autologous immunotherapy, the preparation is the product. That evaluation takes time, and it takes precision. If Investor082 does not understand that, they are either misinformed or intentionally trying to distort the discussion.
This is not a fringe idea. It is the future of oncology. It is being built step by step, patient by patient, and lab by lab, with a manufacturing backbone that regulators are watching as closely as the clinical data itself.
The claim that this is “quackery” collapses the moment you understand what is being reviewed. And once that review is complete, the results will speak for themselves.
Market Data 
Markets 
AI
