So we built The Fleet: modular plants, manufactured over and over and installed wherever the demand is. Standard modules that click together like LEGO®, so a plant grows by adding blocks. Book capacity in one, or take one of your own.
What SpaceX did
The Raptor is the engine that powers Starship. SpaceX made it cheaper by simplifying it: three versions, each carrying fewer parts than the one before, at higher thrust. Image: SpaceX.
What BioX-AI is doing
The Fleet is the plant that BioX-AI manufactures. Conventional plants sit at the left of this scale, custom-engineered and expensive. We are building the one on the right: fewer systems around each tank, made over and over to the same drawing.
The Fleet
In short
A plant you specify, price and receive rather than commission. Vessels up to 2,000 liters bookable today, modules that reach 50,000+ liters.
The same models in every module, reading each batch live and holding it on recipe. What improves travels as a model, including to the one on your own floor.
The Fleet learns machine behavior, not your process. Your strain, setpoints, recipe and records stay in your own space.
Scale up or scale out
Cost per kilo falls as tanks get bigger, so the industry scales up: one large plant, hundreds of millions, years of construction. The alternative has been small units and worse economics. We did not accept the trade.
Big tanks earn the economics. They also take the money and the years.
Volume per vessel drives cost per kilogram down, which is why every serious plan ends at a large plant. But a plant is a bespoke project, commissioned two to four years later, on a design committed before the first commercial batch proves anything.
Small units move fast. Repeating a one-off is expensive.
Small units install quickly and let capacity grow in steps you can finance. The penalty is unit economics: if each unit is its own project, the engineering bill is paid again every time.
Read on
Why processes stall at 1 m³.
Read → 02What a module is, and what arrives on the truck.
Read → 03The vessels you can book today, and where sites go next.
Read → 04Rent a module, buy a fleet, or license one with us.
Read → 05Who is behind The Fleet.
Read → 06Data, IP, and how fast a site can run.
Read →Tell us what you are making and what volume you need. We will come back with a configuration, a price and a date.
The challenge
Two reasons to be here
Startups need investment or offtake before they can reach scale; corporates need proven scale before committing to either. A module is small enough, and fast enough to install, that a producer reaches volume without financing a plant and a buyer sees real capacity before committing.
Plant, mammalian and insect cells, yeast, bacteria, filamentous fungi and others.
A process that works, and no realistic route to the volume your plan assumes. Your own plant means years and millions before production that matters.
Manufacturers and ingredient buyers.
Your constraint is not capital. The ingredients you depend on come from a shrinking number of geographies at prices you cannot forecast, and the alternative supply is real but not yet at the volume you want.
The wall everybody hits
Every company growing cells at volume is solving the same scale-up problems separately. Most run out of money between the pilot and the commercial plant.
Where most programs stop. Not because the biology fails, but because the next vessel means years of construction and capital few can raise.
And hundreds of thousands of dollars before a single relevant run, spent finding a contract manufacturer and adapting your line to their fermenter.
The gap between a food-grade line and a GMP suite. Build at the wrong tier and you overspend, or cannot take a regulated product at all.
The part nobody says out loud
Money raised to build buys one facility, one configuration, years from anything commercially relevant.
Four decisions change that, all structural rather than clever.
A plant is normally a project: a design house, a bespoke facility, an engineering bill paid again at the next one. We engineered one module instead and manufacture it over and over, so what you specify has a known footprint, price and lead time.
Modules are assembled and wet-tested in a shop, shipped, and bolted onto a prepared pad. You provide a slab with floor load, water, gas and electricity. What is left on site is connection and qualification, not construction.
Repeating the hardware only pays if it repeats the result. Powered by Jarvis, our Physical AI, every module runs the same models, trained on every batch the others have run, so a new one starts as good as the best one running.
Contracted capacity in a Fleet site rather than an asset on the balance sheet, or the same module on your own floor. Vessels up to 2,000 liters are bookable today, so you can run this quarter instead of waiting years.
Get to scale by spending much less and making a decision in weeks, instead of years.
Tell us what you needSolution · Plant as a product
What we are doing
A module is a few LEGO® blocks together: a complete production unit with tanks, seed train, media preparation, cleaning, utilities, instrumentation and controls, engineered once and built over and over.
One reaches 50,000+ liters, and a site is that same block clicked together as many times as demand justifies.
Engineered once, then manufactured. No project-by-project design, no engineering bill repeated at every site.
Complete in itself. You bring a slab with enough floor load and access to water, gas and electricity.
A single module scales to 50,000+ liters. Past that you add another, so capacity grows in steps you can finance.
General arrangement
The same drawing every time. Engineering is paid for once, and what leaves the shop after that is a manufactured copy of it.
Plant as a product
A plant stops being a capital project you commission and becomes something you specify, price, order and receive. The design, the procurement, the site work and the waiting happen once for the module.
Pick the configuration from a catalog of decisions rather than briefing a design house.
A price against a specification, not an estimate against a scope that moves.
Built, tested and configured, on a lead time you can plan a launch around. A project ends in commissioning surprises; a product ends in a delivery date.
Two to four years, most of it before anything grows.
A design house draws a facility around a site. Equipment is bid, fabricated and delivered on separate schedules, controls are built in place, and commissioning finds what the drawings hid. Every step is bespoke, and every plant pays for all of them again.
Manufactured off site while the slab is prepared.
The block is built and wet-tested in a shop, ships as a unit, lands on a prepared pad and connects to water, gas and power. The calendar is a manufacturing lead time rather than a build program.
What arrives
The tank alone produces nothing. A module carries the systems around it, which is what makes it plug and play.
Production tanks in the shape, material and mixing the organism needs, the seed train that fills them, and the media preparation that feeds them.
Steam or hot water, chilled water, clean compressed air and filtration, water treatment, and the piping that distributes all of it.
Instrumentation for every parameter you measure, and a model that reads the batch live, holds it on recipe and cleans between cycles.
Dewatering, drying, milling and packaging sized to the output, so what leaves is product rather than broth.
Powered by Jarvis, our Physical AI
Powered by Jarvis, our Physical AI, a repeated block of equipment becomes a repeated result: the same models in every module, trained on every batch the others have run, acting on the tank rather than reporting on it afterwards.
Every instrument feeds the model continuously, and soft sensors infer what nobody can measure directly: cell state, viability, the growth curve you are on.
Feed, gas, temperature, pH and harvest timing are set by the model against the recipe. Drift is corrected while it is still drift.
A batch anywhere in The Fleet is evidence everywhere in it. Yield learned at one site ships to the others as a software update, including to the module on your own floor.
Specify a module in a few minutes and we will come back with a price, a footprint and a schedule.
Configure your moduleThe Fleet
What The Fleet is
A module is one plant. The Fleet is all of them. One design, built over and over, each running the same tanks, powered by Jarvis, our Physical AI, and the same recipe, so it produces the same result wherever it stands. Several on one property make a Fleet site; one on yours behaves exactly like ours.
If your process needs more than The Fleet can give you on the day you sign, partner sites make their own capacity available, so you can cross the gap in their tanks and move into your module when it is ready.
The first site is in the United States, where the demand and most of the members are.
Latin America and India follow, next to low-cost feedstock, then Europe and the Middle East.
Wrong pricing model, and one infrastructure tier for everyone.
Contract manufacturers charge for time in the tank, a model built around microbes that clear a vessel in days; plant cells occupy one for weeks. They are also built for biopharma, so GMP overhead is priced into every hour whether your product needs it or not. Against a slow culture the cost per kilogram lands where no food, nutraceutical or cosmetic ingredient can pay.
Rent a module, buy a fleet, or license a site.
Rent. A subscription holds your capacity, and campaigns are billed cost plus, so you pay what the run costs rather than what the calendar costs.
Buy. The module on your own floor, specified at the tier your product needs. Capacity you are not using can go back to The Fleet and run for other members.
License. Fund and host a site and run it as part of The Fleet, on land and utilities you may already have.
Site plan
The pad, the utility spine and the aisles are drawn once. Each phase bolts another module onto them, so capacity grows in steps you can finance.
Build The Fleet now.
Tell us what you needCo-create
Who can join
The module is configured to whichever you run: plant cells, mammalian cells, insect cells, yeast, bacteria, filamentous fungi and others. Each one loads the tank differently, so the vessel, the mixing, the cooling and the instrumentation follow the organism rather than the other way round.
Hours for bacteria and yeast, days for plant and mammalian cells. Campaign length, scheduling, utilization and cost per run follow from that, and the module is sized to the organism you actually run.
Aggregating cells, stringy fungal broth and free-swimming microbes each want a different blade or no blade at all. Keeping the culture suspended without damaging it is a mixing and vessel design question, and most companies answer it alone.
A fast grower demands oxygen faster than a tank can dissolve it and throws off metabolic heat while it does. Those two transfer limits, not the biology, decide how large a single vessel can usefully get, and they are designed into the module rather than discovered later.
Shear, media cost, oxygen demand and cycle frequency set the economics whether the biomass becomes a food ingredient, a cosmetic active or a biopharma intermediate, and whether it grows in days or hours. Our customers work across every one of these.
Whatever you are growing, the constraint is the same one. Tell us what you are working on.
Tell us what you needHow it works
Subscription +
cost plus.
we own and operate it · you buy output, not an asset.
Per configuration.
you own the modules and run them on your own floor.
By arrangement.
you fund and host a site, and run it as part of The Fleet.
About
Veterans of this industry and people new to it, deliberately. A room of veterans alone would have drawn the plant the old way, and the old way is what has kept biomanufacturing from commercial volume. The veterans know what breaks on a plant floor; the newcomers come from software, robotics and product, and keep asking why a plant cannot be manufactured, shipped and switched on. The module is what happens when neither group wins the argument alone.
Tell us what you are making and what volume you need. We will come back with a configuration, a price and a date.
Questions
If yours is not here, the form goes to a person, not a queue.
Before you ask
One engineered block that grows biomass on its own: tanks, seed train, media and cleaning systems, utilities, instrumentation and controls, built and tested before it ships. Designed once and manufactured repeatedly rather than drawn up per project, which is what takes the cost and the calendar out.
Software that runs the equipment rather than reporting on it. Each module sets feed, gas, temperature, pH and harvest timing against the recipe by itself, with operators supervising. Because every module is identical, a yield gain learned at one site is a software update at the others.
A slab with enough floor load, and access to water, gas and electricity. Everything else arrives with the module.
Rent if you want output without an asset: a subscription holds the capacity, we operate the module, and you pay what each run costs. Buy if volume is certain and you would rather own the steel. Some members do both, proving the process in The Fleet and then taking modules of their own.
Campaigns are billed cost plus, meaning media, labor, utilities and consumables plus a defined margin to the site that runs them. Modules are quoted against the configuration you specify. Send us one and you get a price, a footprint and a schedule.
The ones the configurator carries today: plant cells, mammalian cells, insect cells, yeast, bacteria and filamentous fungi, and others on request. Each loads the tank differently, so the module is configured to the organism rather than the reverse.
Your choice. A module can arrive with DSP integrated or without it, running as an upstream block that hands broth to whatever you already have. Integrated means the standard DSP train, dewatering, drying, milling and packaging sized to the output, so what leaves the module is dry biomass rather than broth. Anything beyond that, extraction, fractionation or purification to a specific spec, comes as an add-on rather than part of the module itself, because the module stays standardized. We quote it separately for you.
Much faster than a plant, because nothing is designed from scratch and the heavy work happens off site while the pad is prepared. Utilities, connection and qualification are still real work, and there is risk in any date.
That is where most of the demand and most of the members are, and where a site and its utilities can be secured fastest. Latin America and India follow, then Europe and the Middle East. Members with volume in a region get a say in when it gets a site.
Because two different things come off a batch, and only one is yours. Machine behavior, how fast the jacket pulls heat out, how oxygen transfer falls as broth thickens, how a pH loop settles, is a property of the equipment, and it is what the control models train on. Your process, the strain, the media, the setpoints, the titre, never enters the shared model.
Your runs stay in your own space, visible only to you and the crew running your campaign. Training happens on de-identified machine signals, and what moves between modules is the trained model, not the data behind it.
It is in the contract as well as the architecture: you own your process data and any improvement specific to it, we own the general control models. A module can also run with learning switched off.
Nothing. Two companies in the same category can run in the same building without touching each other's work: campaigns are separated by module and by schedule, and confidentiality is contractual. What is shared is the equipment design and how Jarvis, our Physical AI, performs, never the product.
Two ways. License a site: you fund and host it, we license the module design, Jarvis, our Physical AI, and the operating standard, and capacity is sold through The Fleet. Or invest in a licensed site: back a site somebody else hosts, which is exposure to capacity in use rather than to one product working.
Still have a question? Ask it directly, and we will answer honestly, including when the answer is that we do not know yet.
Tell us what you needTell us who you are and what you need. We reply to every enquiry, usually within two working days.
All fields marked * are required. The form will not send until every one is complete.