Bioreactor manufacturers and the partners who run them: judge the control system

Choosing hardware and partners

1. Judge a vessel on its control system. Dissolved oxygen, pH, temperature, agitation and gas mixing under closed loop control, with off gas where possible. A vessel with fewer measured variables produces data that does not transfer to a controlled process.
2. Check how data leaves. Continuous logging in an open format, exportable without the supplier, is what lets a run be analysed and compared. A controller whose data lives only in its own software is a future problem.
3. Match microbial and mammalian requirements separately. Microbial fermentation demands oxygen transfer and heat removal that a mammalian vessel is not built for. A unit sold as suitable for both is a compromise and the compromise should be understood.
4. Treat skids and continuous operation as facility decisions. Continuous or connected processing changes buffer demand, footprint, control and how a batch is defined. It is a plant decision rather than an equipment upgrade.
5. Divide the work explicitly with a partner. Who owns the process, who develops the analytics, who holds the raw data and what transfers at the end. Ambiguity here is the commonest source of dispute at the end of a campaign.
6. Ask what the partner's constraint is. Every site has a scarce step, whether suite time, analytics or release testing. The honest ones will tell you, and it predicts your timeline better than a capacity figure.

Instrumentation is what transfers

A run produces a process description only if the variables that matter were measured. A vessel without dissolved oxygen control, or without logged agitation, produces a story rather than data.

Specify the instrumentation against the scale you intend to reach, not against the scale you are at.

Ownership decides portability

A platform partner gives speed and keeps the process; a contract manufacturer runs yours and gives portability. Both are legitimate, and the choice determines whether a second source is ever possible.

Decide it deliberately at the start, because it is not renegotiable once a campaign has run.

An automated bioreactor, and the stainless steel bioreactor question

Automation here means the control loops and the data rather than a robot: dissolved oxygen, pH, feed and temperature held against a recipe, logged at a resolution that lets a run be explained afterwards. That is worth having at any scale, and it is the part that makes two runs comparable.

Stainless against single use is a different decision and it is mostly about campaign length and changeover. Steel is cheaper per litre over many batches of one product and carries cleaning validation between products; single use removes the cleaning and adds a per batch consumable and a supply chain dependency. Below a few hundred litres, and for a facility making several products, single use usually wins on both cost and risk.

A bioreactor for sale, and reading a second hand listing

A bioreactor offered for sale is a vessel plus an unknown history, and the questions are the same every time. Which controller is it, and is that model still supported with software and spares. What probes are included, and are the fittings the same standard as the ones you can buy. Has the vessel been pressure tested, and does the glass carry a rating and a date. Does the drive turn freely and what is the motor's hours. A cheap vessel with an unsupported controller is a rebuild, so price the controller and the probes separately before you compare it with new.

A bioreactor controller, and what it has to drive

The controller is the part that decides what a vessel can do. Count the loops it closes, temperature, pH, dissolved oxygen, agitation, level or weight, and the feeds, then count the pumps and the mass flow or gas channels it drives, because a cascade that manages oxygen by moving between agitation, air and pure oxygen needs the channels to exist. After that it is data: whether the batch record exports in a form your quality system accepts, whether recipes can be written and locked, and whether a second vessel can be added later on the same unit.

A bioreactor control system on a multi-vessel bench

Running several vessels from one control system changes the specification. Each vessel needs its own loops and its own pumps, but the cabinet, the gas supply and the software can be shared, which is the economy a parallel bench is built on. The questions are how many vessels one controller supports, whether each can run an independent recipe or only a shared one, how the software presents a comparison between them, and whether a failure on one vessel takes the others down. Calibration and probe management multiply by the vessel count, which is the running cost nobody quotes.

perfusion culture, and what it asks of the vessel

Perfusion keeps cells in the vessel while medium flows through it, which holds them in a steady state at high density and takes the product out continuously. What it asks for is retention and control: a cell retention device such as an alternating tangential flow filter or a settler, pumps for medium in and harvest out, level or weight control that actually holds, and a strategy for the filter's own fouling. The trade against fed-batch is a smaller vessel and a longer campaign, with more to go wrong over weeks, and a product that spends less time in the reactor.

scale up bioreactor work, and what transfers

Volume does not scale the things that matter. What transfers between vessels is the volumetric power input, the oxygen transfer coefficient, the tip speed and the mixing time, so those are measured at small scale and held constant at large, which is why a scale up report reads as a table of those numbers rather than a ratio of litres. Geometry helps: a vessel family with the same height to diameter ratio and impeller type makes the arithmetic honest, and a change of impeller means the work starts again.

Common questions

What separates one laboratory bioreactor from another?

The control system and the data path, not the vessel. Sensors, closed loop control and exportable logging are what make a run comparable and transferable.

Can one vessel serve microbial and mammalian work?

With compromises. Microbial cultures demand far higher oxygen transfer and heat removal, and a unit sized for mammalian work will limit them. Where both are routine, two vessels usually beat one compromise.

What should be agreed before booking a slot?

Process ownership, the analytical package and who develops it, raw data access, what happens if a batch fails release, and the reslot terms. These are far easier to agree before a campaign than during one.

Browse by service class

• Compare Gene synthesis on advertised prices